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.

LAUNCHXL-CC3235S: Inquiry about the way how to store the firmware into External flash

Part Number: LAUNCHXL-CC3235S
Other Parts Discussed in Thread: CC3235S

Hi Experts,

Our customer is trying to evaluating CC3235S with LAUNCHXL-CC3235S. they are referring the sample code which is “simplelink_cc32xx_sdk_5_20_00_06\examples\nortos\CC3235S_LAUNCHXL\demos\trigger_mode” as follows. Customer built this project and tried do burn this firmware into sFlash, however, they were not able to burned it in LAUNCHXL-CC3235S by CCS. This means, when customer executed Power cycle( removed USB plug and reconnect it ) after stopping debugging, CC3235S did not work. Probably, the firmware was not stored.  They confirmed that the binary file of this firmware was generated. As far as I checked LAUNCHXL-CC3235S schematic ( https://www.ti.com/lit/zip/swrc348 ),  sFlash was implemented. Also, I requested customer to try burn-in it during SOP[2:0]=010, : Flash and functional development mode with 4-pin JTAG), However, this issue still occurs

Can we have your Expert’s advice/comments on this, please?

I noticed the latest sample code has image.sysconfg. should customer configure any setting ?

 

Customer’s environment is as follows

SDK: simplelink_cc32xx_sdk_5_20_00_06

CCS version: 10.4

Sysconfig : 1.8.0

UniFlash : 6.3

Best regards,

Miyazaki