• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 51 subscribers
  • Views 350 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.

CC2564C: A few questions about what the device is capable of (firmware updates over air)

Jacob Wyrick
Expert 8665 points
Part Number: CC2564C
Other Parts Discussed in Thread: CC3301

Hi team,

I am also looking at the CC2564C Bluetooth module for Bluetooth capability.  An application we might like to pursue is to do firmware updates to our charger over Bluetooth. 

  • Is this the right device?
  • Is such an application possible with this device?
  • If so, for the fastest update rate possible, would we use BR, EDR or LE?
  • What would the fastest attainable update rate be for a firmware update?  4Mbps based on the UART?
  • What bootloader would you recommend for updating in this fashion?

Thanks,

Jacob

  • 0
    TI__Mastermind 46555 points

    Hey Jacob,

    That device does indeed have Bluetooth capabilities. However, I would also encourage you to take a look at our newer CC3301 device which has BLE 2M PHY.

    I don't see a reason this wouldn't be a possible application unless there are certain system level requirements that can't be met. EDR would still give you the fastest theoretical data rate, but with the CC3301 device you also have Wi-fi capabilities that would ultimately give you the fastest speeds. As far as the realistic update rate, its hard to tell since there are quite a bit of factors that play a part (e.g even the packet format with different payload sizes). However, I can say the bottleneck will not be the UART communication. I found this article online that goes into more details on this, I expect it will be a valuable read.

    I'm not really sure what are referring to when asking about the recommended bootloader. In any case, this will likely be something dictated by the host (the targeted system getting the update).

  • 0 in reply to Dylan Hubbard
    TI__Expert 8665 points

    Thanks Dylan!

    One other question. In regards to the type of bootloader, the thought is that if we wanted to do firmware updates to our system over Bluetooth, the data coming from the Bluetooth device to our microcontroller would have to be ported over some form of UART, correct?  We would then need an associated bootloader for handling the update from this UART.  Do I have this correct?

  • 0 in reply to Jacob Wyrick
    TI__Mastermind 46555 points

    Hey Jacob,

    So you are on the right track, but I think there is some confusion here. So the data would come over the UART interface from the BT controller, but how that data is handled will still be dictated by the Host device. Its likely that it will be stored in some flash and the Host controller will need to boot from the new FW image - this process would required a bootloader, yes - but that would be unrelated to our device. On top of that, technically they could pull that FW from the flash via any interface and not just UART.

    Let me know if that clears it up. I'm a HW specialist so I can only relay high level info on this, if needed I can pull in one of our SW experts.