Open m0rb opened 1 year ago
FWIW - dfu-util works just fine after flashing the IronOS-dfu bootloader bin with a SWD debug cable.
Match vendor ID from file: 1209
Match product ID from file: db42
Multiple alternate interfaces for DfuSe file
Opening DFU capable USB device...
Device ID 28e9:0189
Device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Interface #0 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
File contains 1 DFU images
Parsing DFU image 1
Target name: ST...
Image for alternate setting 0, (1 elements, total size = 44544)
Setting Alternate Interface #0 ...
Parsing element 1, address = 0x08008000, size = 44536
Erase [=========================] 100% 44536 bytes
Erase done.
Download [=========================] 100% 44536 bytes
Download done.
Done parsing DfuSe file
I don't know whether or not to open another issue, but it seems that flashing boot screens / animations requries the use of an external programmer and SWD debug cable -- IronOS-dfu and dfu-util will act as if they're programming. Can take another bin dump and see which range is updated, if at all.
Hi Ralim!
just got a new iron and wanted to test out #16
unfortunately I'm unable to upload or download anything while in runtime mode;
same error message inversely trying to flash runtime.dfu
Not really sure where to start digging here, but can provide more details, logs, and tracing if need be.