• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 41 subscribers
  • Views 189 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3235MODASF: One binary for CC3235MODASF and CC3235MODAS

Cedric Gerber
Expert 2240 points
Part Number: CC3235MODASF
Other Parts Discussed in Thread: CC3235MODAS, CC3235S, UNIFLASH

Hi,

Due to the chip shortage, we are thinking about switching one of our product from CC3235MODASF to CC3235MODAS. With some optimization we can do without the 1MB internal flash. 

To avoid having to maintain two differents firmwares, I would like to use the same binary on both variants. From my understanding we should be able to link both variants as the CC3235MODAS and ignore the internal flash on CC3235MODASF.

Is it enough to modify the linker cmd file to use the ram instead of flash as in the CC3235MODAS examples?

Or is there some other things which would prevents this? (Bootloader for example)

Best regards,

Cédric

  • 0
    Guru 73425 points

    Hi Cédric,

    You can use this trick described by Michael. It is for CC3220, but for CC3235 should work as well.

    Jan

  • 0 in reply to Jan D
    Expert 2240 points

    Hi Jan,

    Cool that's exactly what I was looking for. Thanks!

    I'll test tomorrow and report here. I suppose the potentially tricky part will be to do the OTA from the mcuflashimg.bin to  mcuimg.bin.

     

    Best regards,

    Cédric

  • 0 in reply to Cedric Gerber
    Expert 2240 points

    It's working : )

    I've modified the ccs project variant to "CC3235S" (not sure it's actually needed), and modified the linker file as in the cc3235s examples.

    I've created a new uniflash project based on the cc3235s and have been able to load it with uart on the "sf". 

    One thing to note is that the .bin file is quite bigger, 237KB instead of 165KB. Not sure why.

    I am now trying to make the ota from SF to S variant. 

    What I suppose to be the best way:

    - Delete /sys/mcuflashimg.bin with tag SL_FS_WRITE_BUNDLE_FILE.

    - Write /sys/mcuimg.bin  with tag SL_FS_WRITE_BUNDLE_FILE

    - Check new firmware and if successful commit with sl_FsCtl( (SlFsCtl_e)SL_FS_CTL_BUNDLE_COMMIT, ...)

    However I do not see how I can delete a file with tag SL_FS_WRITE_BUNDLE_FILE. Any idea?

  • +1 in reply to Cedric Gerber
    Guru 73425 points

    Hi,

    Good to hear that you was able to use trick described my Michael. Bigger size of image for CC3235S device is expected, because it contains memory for initialized variables. But if you want to dig deeper, you can use memory allocation tool at CCS and compare results of build for S and SF device.

    I am sorry I am not able help you with your OTA task. Without testing this at my side, I am not able provide right answer. Technically should be enough to prepare one TAR file for S device which should work at SF as well. It will not be needed to deal with mcuflashimg.bin file. But I am not able say what exact tweaking inside OTA code will be required. It will be better to open new thread for this task.

    Jan

  • 0 in reply to Jan D
    Expert 2240 points

    Hi Jan,

    Ok, I will open a new thread for the ota questions.

    Thanks for your help! 

    Cédric