robdobsn / BusRaider

Play vintage computer games on real hardware, single-step debug Z80 programs and test new hardware with the BusRaider for RC2014. https://robdobson.com/2018/08/trs80-galaxy-invasion-on-rc2014/ and https://robdobson.com/2019/06/what-can-you-do-with-a-busraider-part1/
https://robdobson.com
MIT License
20 stars 3 forks source link

Request for a working launch.json file #11

Open skullandbones opened 10 months ago

skullandbones commented 10 months ago

Hi Rob,

Your documentation on your wiki page https://github.com/robdobsn/BusRaider/wiki/Debugging-a-Program does not work for me.

I am using DeZog 3.3.2 in vs code 1.83.0 on my Raspberry Pi 4 running Linux Raspberry Pi OS bookworm (64-bit).

I have just built my BusRaider v2.3 kit: ESP32 SW: 2.2.061 (HW V2.2) - came pre-programmed Pi Zero W SW: V2.2.062 - I built the latest and I programmed my micro SD card

I realise that the ESP32 and Pi Zero firmware images are not the same version number but hopefully that is not the issue.

An additional observation is that the WiFi link to the ESP32 is unreliable and works for about 60 seconds after power-up then the web UI on Chrome stops working. If I refresh the web page then get a connection failure message. wireshark shows no responses coming from the ESP32.

I have managed to run a ZX Spectrum diag ROM image from Retroleum and this works albeit a bit slowly. This confirms at least the 64K RAM in the 1MB RC2014 RAM card is working. I used linear mode.

I wanted to do single-step debugging but I am having trouble with your documentation for setting up DeZog.

I have looked at the ESP32 SW and noted that the port is 11000 and not 10000 as per your documentation on your wiki

Please can you provide some hints on what the launch.json file should be to get single-step debugging to work.

Thanks,

Regards, Dean