I'm combining two rows together

[georgerosar]

Combing micropython and teensy core together along with freeRTOS and other stuff.

Why do you think my qemu is doing this?

Reading symbols from build-SHAREDLIB/micropython.elf...
Remote debugging using localhost:51234
IntervalTimer::~IntervalTimer (this=0x0 <IntervalTimer::~IntervalTimer()>,
    __in_chrg=<optimized out>)
    at /Users/iridescent/iridescent/iridescentCoconutSynth2/iridescentmicropython/ports/libmicropython/IRIDESCENT/cores-master/teensy4/IntervalTimer.h:52
52            this->end(); 

That's what It starts out doing. I don't understand gdb very well, but I believe it's telling me the program is ending immediately.

[georgerosar]

My kernel is 32MB I need some new hardware.

[georgerosar]

Also the encryption doesn't work if teensy4.1's flash ram size is larger than it's supposed to be

[defragster]

Two Rows of?
Were there any less inclusive parts building that worked?
Does it build and work without the use of IntervalTimer?
Flash RAM "larger than it's supposed to be" ?
A locked or lockable 1062 Teensy? If unlocked does it work with .Hex instead of .eHex?

[PaulStoffregen]

Why do you think my qemu is doing this?

Would it be too obvious to answer "why" that Teensy's core library was meant to be run on real NXP IMXRT hardware rather than an emulator?

[georgerosar]

Two Rows of?
Were there any less inclusive parts building that worked?
Does it build and work without the use of IntervalTimer?
Flash RAM "larger than it's supposed to be" ?
A locked or lockable 1062 Teensy? If unlocked does it work with .Hex instead of .eHex?

Sorry I mean combining two ROMs. It works in .hex easily. I'm running the kernel in qemu like this:

#!/bin/sh
/usr/local/bin/qemu-system-arm -cpu cortex-m7 -machine mps2-an500 -nographic -monitor null -serial telnet:localhost:4321,server,nowait -semihosting -kernel ./build-SHAREDLIB/micropython.elf -gdb tcp::51234 -S