AM2432: burning appimage failed

Hi Ming,

Thanks for your advice, and I've suggest customer try to change to release version. Below is customer's response:

We have two boards:

    A:TI  LP-AM243 (CPU:XAM2434ASFGGAALX)

    B:FR CPU(CPU:AM2432BSFFHIALX)

    use the following  two CCS projects:

    1. sbl_uart_uniflash_am243x-lp_r5fss0-0_nortos_ti-arm-clang

    2. sbl_ospi_am243x-lp_r5fss0-0_nortos_ti-arm-clang

    Active Release,change Board  or  Device to AM2432_ALX in AM2434_ALX.ccxml and then Clean Project,Build Project.

    In the project Release directory, we chose sbl_ospi.Release.hs_fs.tiimage and sbl_uart_uniflash.Release.hs_fs.tiimage .

    Then ,download to flash use the following CFG :

    # First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files

    --flash-writer=sbl_uart_uniflash.Release.hs_fs.tiimage

    # Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

    # Program the OSPI PHY tuning attack vector

    --operation=flash-phy-tuning-data

    # When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0

    --file=sbl_ospi.Release.hs_fs.tiimage  --operation=flash --flash-offset=0x0

    # When sending application image, make sure to flash at offset 0x80000 (default) or to whatever offset your bootloader is configured for

    --file=hello_world_am243x-lp_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x80000

    Board A and B all download successful.Power-on again.

    A successfully start, and shows:

    B failed, and it shows:

    DMSC Firmware Version 8.5.3--v08.05.03 (Chill Capybar

    DMSC Firmware revision 0x8

    DMSC ABI revision 3.1

    Some tests have failed!!

    We try to changed some of the configuration, but it still didn't work.

    Please ask the TI engineer to help us check whether there is anything neglected in the above steps.

BR

Sirui

Hi Sirui,

It is hard to tell the reasons of the failure on a custom board. One thing they can try is to flash the SBL_NULL HS-FS version to the FR board, so that we can tell the issue is with the SBL or the appImage. 

Best regards,

Ming

Hi Ming,

According to our SDK document, our device has digital verification by default:

However customer read ROM info and find Cust MPK empty, which caused their app failed.

Need to confirm whether Cust MPK is pre-burned in our device, or customer need OTP Keywriter to self-burn.

BR

Sirui

Hi Ming,

Thanks for the quick response! By my understanding the device(with security) we provide to customer is all HS-FS version, and customer need write key to convert to HS-SE version. Is that right?

And can you tell where customer can download OTP writer? It's not availble in SDK.

BR

Sirui