Hi,

We are trying to boot the IWR6843AOP EVM board through SPI, with an external, Linux-based, non-TI-based processor.

Our code is based heavily on the mmw_sflash_example (located in mmwave_dfp_02_02_02_01) and the ti sdk (located in mmwave_sdk_03_05_00_04).

The hardware was adjusted accordingly, and the flash was disconnected.

According to the IWR6843_Bootloader file, we start with reading the MSSPOWERUPDONE from the device and then loading the file using the ti-based interface.

The file loading protocol works smoothly. including getting all ACKs and no error messages.

After sending the file, the TI board triggers the host-IRQ, as expected. and we read the async event for boot-error.

In the received AWR_AE_MSS_BOOTERRORSTATUS_SB message, we get MSS_POWERUP_STATUS 4 - which indicates (according to mmWave-Radar-Interface-Control) RPRC_IMG1_AUTH_FAILURE.

We have tried to send an image with the CRC generated by gen_bin32.pl and without it. We got the same error in both cases.

Do we need to change the format of the file? Do we need to change any other configuration?

Our source code is a simple GPIO led toggle. It includes both code for the mss (which just toggles the led) and for the dss (which is an empty main function). 

Attaching both the logic data and the TI binary. ## edited - apparently, I can't attach these files to the forum, can send specific pictures/files upon request.

P.S.

After reading the AWR_AE_MSS_BOOTERRORSTATUS_SB the host IRQ is triggered again, but when sending sync from the host the device (ti) doesn't respond