This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1310: Erase failing through UART over USB on linux

Part Number: CC1310

Hello,

I'm trying to use the ti154stack_linux_x64_4_40_00_03 cc13xx-sbl to flash a custom board with a cc1310 on linux. I have it set up to where I can successfully flash and verify the image, but if I try to erase the image it fails at 50% giving "Flash erase failed error status 2" 

As far as the connection from the computer to the board, it is just going through a USB cable to an FTDI FT231X, then to the UART on the CC1310.

So, while this isn't necessarily an issue for devices that haven't been programed yet, I'm slightly concerned about reprogramming this way. I can just use windows via Flash Programmer 2, as that is correctly erasing, but I was wondering what would be keeping it from getting correctly erased on the linux sbl.

  • Hi Bryce,

    Sorry for the delay, I will take a look at what the actual difference between these two flash programming mechanisms are and get back to you tomorrow. 

    Regards,

    Sid

  • Hi Bryce,

    Is this a CcDnld_Status error? In that case, 2 represents CcDnld_Status_State_Error Device State Error (cc13xxdnld.h).

    Do you restart your device during your flash process?

    Cheers,

    Marie H

  • Hi Marie,

    Here's a screenshot of the terminal window from when I'm working with it, it doesn't say anything about a CcDnld_Status error, just a flash erase fail. I went ahead and included it also succeeding on programing and verifying. The only time it restarts during the flash process is before to get it into bootloader mode, and after verification to bring it back out of bootloader.

  • Actually, I found my issue after reading back through the erase process in the files for the sbl. The sbl base assumes that the chip is the F128 version; I have the F64 on the things that are doing this. So it was just a mismatch on expected flash size and actual. I have added the ability to specify flash size and now it works for these devices.

    Thanks,

    Bryce