• State Answer Suggested
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 42 subscribers
  • Views 591 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.

cc3200 ethernet bootloader

user4179451
Prodigy 10 points
Other Parts Discussed in Thread: CC3200

Hello

Where can I find description of ethernet bootlaoder for CC3200. We consider to switch to this chip in a product that will be manufactured in series of 100000, and need to be confident that we are able to update the product over internet.

Bets regards

Jan-Petter Bakke

  • 0
    Intellectual 535 points

    I was going to post this question myself... we are going to need to be able to roll out code updates via the Internet as well... is there any documentation about how to do this?

    Thanks,

    Mark

  • 0 in reply to Mark Goodrich
    Prodigy 20 points

    Hi, 


         I also am working on a device which would require updates via the internet so this is a question I have been researching as well. .  And also.. The project I'm working on although primarily intended for use in a WiFi implementation may at times be deployed in environments where the WiFi is not an option leaving a wired ethernet connection the only solution. I would prefer take advantage of the integrated capabilities of the CC3200 but also have the option to reroute on the same device when needed.


        Dave

  • 0
    Intellectual 780 points

    You can refer to the OTA (Over The Air) update process and see if it fits in with your requirements.  I decided on a completely customized approach.  The main thing to keep in mind is the CC3200 loads using the serial flash.  The serial flash can be viewed similar to a conventional hard drive in that it maintains files within folders.  Typically the /sys/ folder would contain data/code files relevant to any firmware update process.  You can refer to documentation for naming standards.

    I decided to use a completely custom TFTP process to manage my firmware updates.  So there is no restriction to use the OTA process as outlined.