Comments for https://wellys.com/posts/avr_c_gdb_bloomsetup/

Hi Lief, hope you're well.

Just FYI, since version 0.10.0, Bloom can program the target via GDB. For debugWire targets, this means you no longer have to worry about the DWEN fuse or rely on other software and ISP for programming, as Bloom will write to the target's program memory via the debugWire interface.

In other words, since version 0.10.0, you can simply begin a debug session in GDB, then make changes to your code and rebuild the ELF (GDB will notice the ELF has changed and will reload it for you), then run the load command in your GDB session, to instruct GDB to program the target with the latest ELF, via Bloom. Bloom will then program and reset the target, leaving it ready for you to continue your debug session with your newly applied changes. No need to close Bloom, cycle target power, etc. Oh but keep in mind, if you do choose to use this new function, be sure to disable the disableDebugWirePreDisconnect target param in your Bloom config (otherwise you'll still need to cycle target power after each disconnect).

Oh and BTW, I've just noticed that you've been using the target extended-remote localhost:1442 command to begin a remote session with Bloom. Bloom doesn't support the extended GDB protocol - it only supports the standard protocol (target remote localhost:1442). As I understand, most of the additional functionality provided by the extended protocol cannot be applied to debugging AVRs, which is why I've not bothered to support it. If you switch to the standard protocol, you should experience no difference (except for better stability, possibly), as the standard protocol is a subset of the extended protocol, so everything that's worked for you with the extended protocol will be part of the standard protocol.

Let me know if you have any questions.

Thanks!

Nav