• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 553 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.

CC2640R2F-Q1: CC2640x Advisory 08,

paddu2017
Expert 2885 points
Part Number: CC2640R2F-Q1
Other Parts Discussed in Thread: CC1310

Hi,

The new errata sheet(swrz085) mentions about Advisory 08,
and the workaround mentions about keeping the flash ON during IDLE mode.
does this workaround increases the power consumption? and how much would be the increase?

Best Regards
paddu

  • 0
    TI__Guru**** 317180 points
    Yes, this will increase the power consumption. Some tests I did on the CC1310 (same flash block and power system as CC2640R2) indicated about 500 uA.

    It will therefore be a tradeoff with the risk of losing some packets and somewhat increased power consumption. You should also evaluate the probability for the CM3 starts when you send/ receive a packet in your application. If this happens infrequently and you can accept any lost packets you don't have to use extra current.
  • 0 in reply to TER
    Expert 2885 points
    Hi TER,

    Thank you very much for the quick reply.

    500uA would be a huge increase.
    I am sorry for asking additional questions,
    could you please let us know below details.

    1.Does it mean there will be an increase of 500uA even in standby mode?

    2.The errata mentions that there will be "deviation error in the modulated signal or erroneous signal reception"
    does it mean that the RF frequency will be out of Bluetooth Specifications(illegal RF)?
    or there will be just some packet loss?

    3.If possible could you please let us know the rate of occurrence,
    does it occur every time if CM3 starts during send/receive packet?

    Best Regards
    paddu
  • 0 in reply to paddu2017
    TI__Guru**** 317180 points
    1) The current increase is only in the active modes.

    2) I haven't done any measurements on BLE with this. What I saw when I measured with 50 kbps on CC1310 was that the deviation increased by 50% for a short part of one bit periode.

    3) It happens everytime the CM3 starts from standby and the radio is active when the constraint is not set. The constraint ensures that the flash is on as long as the RF core is on.
  • 0 in reply to TER
    Expert 2885 points

    Hi TER,

    Thank you so much for the information.

    I am sorry for the confusion, the question was not about standby mode,
    it was about the Idle mode, as this Advisory is related to Idle mode.

    1.In idle mode the current consumption is 650uA as shown below.
    Does this Advisory mean +500uA increase to this Idle current consumption(60uA+500uA)?
    or does 650uA already includes this flash current?

    2.With regards to the question 2, is it possible to let us know if this errata causes
    RF to be out of Bluetooth Specifications(illegal RF)? or there will be just some packet loss?

    Best Regards
    Paddu

  • 0 in reply to paddu2017
    TI__Guru**** 317180 points
    As written in the last reply, the extra current is when the radio core is on and as far as I know, not measured how this impact the BLE spec.
  • 0 in reply to TER
    Expert 2885 points
    Hi TER,

    Thank you.

    Is it possible for someone from BLE team to answer the second question?

    Best Regards
    paddu
  • 0 in reply to paddu2017
    TI__Guru** 106705 points
    Hi Paddu,

    The 650 uA current does not include the flash being on. For BLE use cases however, IDLE is typically used only when the radio is operating and you do not use the Cortex-M3. Unless your application code uses IDLE outside of this you will only get a 0.5 mA current increase for the period the radio is running.

    It is of course debatable if this errata really affects BLE at all though. BLE is designed to handle packet loss gracefully, so in the event this issue is triggered in your application it is not likely to give you any noticeable performance impact.

    Best regards,
    Fredrik