Other Parts Discussed in Thread: IWR6843AOP, UNIFLASH
Tool/software:
Hello,
We are working with the IWR6843AOP and have built our application (e.g., out_of_box) in Code Composer Studio, which produces a raw “post-build” .bin file.
When attempting to flash this raw .bin via the UART bootloader (SWRA627), it is not accepted at the FILE_CLOSE step (integrity error).
However, when the same raw .bin is imported into UniFlash, flashing succeeds, which indicates that UniFlash transforms the file by adding the required structures (header “MSTR”, multi-core RPRC, tables, internal CRC64, final CRC32), effectively generating a Meta Image.
To ensure a reliable production workflow, we would like to request:
- A Meta Image .bin file (“ready-to-flash”) for the IWR6843AOP corresponding to our build, or
- The official end-to-end procedure/scripting to generate the final Meta Image from our CCS build artifacts, identical to the one expected by UniFlash. Ideally, with example commands and options (device type, core IDs, MSS/DSS mapping, etc.) for mmwave_sdk_03_06_00_00 LTS, including the correct file_types to use at the OPEN_FILE stage.
What currently works:
- PING (0x20) OK : response 00 04 CC 00 CC.
- ERASE (0x28) OK (~30s).
- Re-PING (0x20) OK after erase.
- OPEN_FILE (0x21) OK.
- WRITE_FILE to SFLASH (0x24) OK (sent in 240-byte blocks).
- PING (0x20) just before close → OK.
- FILE_CLOSE (0x22) : ERROR (NACK).
The failure occurs only at FILE_CLOSE when using the raw .bin. With UniFlash, using the same .bin, flashing completes successfully.
Could you please provide the recommended solution (ready Meta Image or official procedure) for generating the final .bin expected by the bootloader?
Thank you very much for your support.
