Nav

Moving this into 'in consideration'. Work will begin once evidence of demand emerges.

This is pretty much done. The new `--target-list-machine` command will list all targets supported by the Bloom binary: ``` $ bloom --target-list-machine [ { "configurationValue": "at90can128", "family": "AVR8", "name": "AT90CAN128"...

Changed the command to `--capabilities-machine`, so that I can extend with other capabilities when necessary. Also added the `insight` boolean flag to indicate whether the build includes the Insight GUI....

Requirements for this were discussed a few weeks back, on the AVR Freaks forum: https://www.avrfreaks.net/s/topic/a5C3l000000BovEEAS/t390852 Not sure if I'm going to implement all of those suggested input formats right away....

I've decided to move this out of v1.0.0. There's quite a lot of changes planned for that release, and this is a lot of work, so I'd rather not delay...

Hi, As is the case on most AVR targets, the debugging protocol for UPDI targets is proprietary. Microchip's EDBG debug tools implement the proprietary protocol in firmware, and expose a...

The problem with reverse engineering is that you almost always end up with more questions than when you started. And when all you have is findings from reverse engineering, it's...

I'm starting with some RISC-V targets from the QingKe V4 series from [WCH](https://www.wch.cn/), and the WCH-LinkE debug tool. First set of targets that I want to support: | Target |...

Quick update on this: I've spent a number of months revising Bloom's TDF format, so that it can better accommodate targets from other families. This includes refactoring all TDF processing...

Quick update on this: I have completed the TDF work and refactored Bloom's codebase (excluding the Insight GUI) to accommodate the new TDF format, and RISC-V targets. I have also...