Added hexload code#96
Added hexload code#96breakintoprogram merged 1 commit intobreakintoprogram:mainfrom envenomator:hexload
Conversation
|
Thanks. I'll test this and get it into the RC. |
|
Hi @envenomator I'm testing this at the moment. Could you provide a series of steps so that I can test it? |
|
Hi; I'll send you an assembled 'hexload' binary to run in mos later today, currently in the office without access to my git and private workstation.
|
|
@envenomator cool thanks. |
|
Forgot to mention; the same MOS tool, started with the 'uart1' option, connects to the GPIO serial pins and receives Intel Hex content from that. But then, you need to connect GPIO + gnd pins to an external serial converter. With the 'uart1' option, there is the option to also specify the local baudrate. With the 'vdp' option, the default is 115.200, as that is compiled into VDP and the maximum transfer I can reliably achieve over the ez80<->esp32 serial interface. You can specify a filename as last option for both 'uart1/vdp' and the content from the incoming Hex will also be dumped to the local uSD card as a binary file |
|
Hi Dean, |
Hi Dean,
I've cleaned up my original patch for VDP/hexload to match the new VDP code for 1.04RC.
In order to do so, I have enabled the DEBUG serial interface by default for use in loading intel Hex files over it, though the DEBUG/SERIALKB variables are still optionally using it.
The actual hexload binary is a MOS loadable command, that I will update for this version in my repo a.s.a.p.