• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 39 subscribers
  • Views 256 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CC3235MODSF: Bootloader question.

John DeWitt
Prodigy 190 points
Part Number: CC3235MODSF
Other Parts Discussed in Thread: UNIFLASH

Hello,

I am debugging a CC3235MODSF using IAR and a XDS110 Launchpad board to talk to our custom board. I've started having an interesting issue where once I stop the debugger, the FW on the custom board reverts to an older version. For example I am debugging version 0xA, I do my work and stop the debugger to make whatever changes I have determined need to be made. However, if I reconnect to the custom board using IARs Project->Attach to running target feature, I can see the FW version has reverted to 0x8. Sadly this version was not in the best shape, so I can no longer make http or mqtt connections and our main processor doesn't get the information it needs to function properly without those connections.

Is this something I should expect to happen? I wasn't able to locate a bootloader reference (probably exists, but I wasn't able to find it). I used the sl_FsGetFileList API and I can see the is a mcuflashimage.bin file (or something close to that). I was reluctant to just blindly erase it not knowing what would happen. 

Can someone explain if this is expected behavior, and if so how I can clean things up so it stops happening?

Thanks,

John

  • 0
    TI__Guru 64725 points

    Hi,

    Can you be more specific what you mean by FW version? It is not the Servicepack version, right?

    Basically, the mcuflashimg binary is your application code running on the internal processor. It gets loaded from SFLASH at boot time and executed unless you download another version as you do when debugging. But the debug version is loaded to the internal SRAM and executed and hence erased when power cycled (and the mcuflashimg is loaded from SFLASH again). If you want to make the debug version persistent you need to program it to the SFLASH).

    Regards,

    Shlomi

  • 0 in reply to Shlomi Itzhak
    Prodigy 190 points

    Hi,

    By FW version I mean the version we keep for our application, so not the service pack. 

    That's interesting that the debugger loads to SRAM rather than SFLASH, I was not aware of that. How do I program the image to SFLASH? Using the Uniflash tool or the command line tools? I find I have better luck with the command line tools.

    Thanks,

    John

  • +1 in reply to John DeWitt
    TI__Guru 64725 points

    Hi John,

    Yes, Uniflash (CLI or GUI) is the right way to go.

    Regards,

    Shlomi