ccrause

This is strange, 0x900 is 1 byte past the end of RAM (0x8FF), and reading two bytes past the end of RAM is allowed by this code: https://github.com/buserror/simavr/blob/51de22447b70aff741c5bd7c1759db8d343e5682/simavr/sim/sim_gdb.c#L371 Perhaps enable...

I checked the backtrace over debugwire at start (tiny45): ``` (gdb) file blink.elf Reading symbols from blink.elf...done. (gdb) target remote :2345 Remote debugging using :2345 0x00000000 in _START () (gdb)...

So after comparing different scenarios it seems as if gdb will do the following when the stack pointer is pointing to end of RAM, such as when the program hasn't...

Can you explain what your intention is by "stripping out the UI code"? Do you mean you just want to start a gdbserver session and not use interactive debug commands?

`Can't find unit system` typically means there is either a problem with the fpc.cfg file not pointing to the correct RTL unit folder, or the RTL units for the LX106...

No feedback.

My snapshots are basically what I generate while testing and debugging the build process of the esp SDKs so should perhaps be seen as test versions. I don't mind changing...

There is a merge request with changes to espsdk4fpc to work with esp-idf v4.3.2 and esp8266-rtos-sdk v3.4. Alfred, not sure if the current combined esp32 and esp8266 archives in espsdk4fpc...

Hi Alfred. No worries, I have been wondering how you managed to invest so much time and effort into figuring out all the install details of the many different cross...

I tested v2.2.0i, but that resulted in an error: cannot open linker script file esp32.rom.ld - the reason seems to be that the wrong -WP version is passed for esp32....