Debugging 8051 firmware gives exceptions

[gec1-dev]

Hi, I'm trying to debug a 8051 firmware in Ghidra (regular Ghidra or pyGhidra) in Windows. For test purposes I compiled a small assembler file. I imported it into a new Ghidra project using as 8051:BE:16:default (2.0).
When I start "Emulate Program in new Trace", execute a couple of instruction and then try to browse memory during program execution I get a lot of exceptions like this:

Address are in different spaces EXTMEM != CODE
java.lang.IllegalArgumentException: Address are in different spaces EXTMEM != CODE
	at ghidra.program.model.address.AbstractAddressSpace.subtract(AbstractAddressSpace.java:285)
	at ghidra.program.model.address.GenericAddressSpace.subtract(GenericAddressSpace.java:21)
	at ghidra.program.model.address.GenericAddress.subtract(GenericAddress.java:117)
(...)

or

Offset must be between 0x0 and 0xff, got 0xfff instead!
ghidra.program.model.address.AddressOutOfBoundsException: Offset must be between 0x0 and 0xff, got 0xfff instead!
	at ghidra.program.model.address.AbstractAddressSpace.makeValidOffset(AbstractAddressSpace.java:610)
(...)

Sometimes the exceptions get into infinite loop and I have to kill Ghidra.

Of course I need to browse different memory areas - Internal, external, bits, SFRs. Am I doing something wrong?

Thanks,

G.

This is how my program looks like in debugger a couple of instructions into the code.

This is my memory map. I used the default memory map provided by Ghidra - only added external memory.

The error looks like this:

I attach the binary - which is a tiny program I padded with zeros to fill the whole 64KB. I compiled it from assembler .s file.

..\sdcc\bin\sdas8051.exe  -los .\test8051.s
..\sdcc\bin\sdld.exe -i test8051.ihx test8051.rel
pip install intelhex
hex2bin.py --pad=00 --size=65536 .\test8051.ihx .\test8051.bin

test8051.zip

[nsadeveloper789]

From the stack trace, it looks like we have a bug in (at least) the Memory viewer. You can try disabling/closing it and seeing what happens (just for curiosity). Otherwise, go ahead and file an actual issue and let us know what version of Ghidra this happened in. When we get a chance, we can try replicating it on our end. Thanks for the artifacts, because that usually makes it much easier.

[gec1-dev]

Raised:
Issue #8982