• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 381 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.

CCS/CC2640R2F: Excessive current consumption Flashing with Elprotronic GangPro vs CCS

Philip Tifone
Prodigy 30 points
Part Number: CC2640R2F
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hello,
We are using the CC2640r2f chip in a design.In the past we have used the CC2640-Launchpad to program the IC using cJTAG.

We have upgraded to the Elprotronic GangPro-CC in order to flash multiple targets at once.

We are finding that the current consumption of a board flashed using the GangPro-CC is higher than one with the launchpad. The thinking is that perhaps we have something miss-configured within CCS during the generation of the .hex output file that would cause something to be miss loaded by the GangPro-CC. We have reached out to the Elprogronics, but were unable to arrive at a source for this additional current consumption.

We are using CCS 8.3.
SDK: 1.5.xx

Summary of flags set: --memwidth=8 --romwidth=8 --intel

I have included screen shots of the Hex utilities settings pages.
Is there anything else that sticks out as not being configured?

Thank you

  • 0
    TI__Guru**** 162325 points

    Philip,

    If you flash the .hex file using UniFlash do you see the same current consumption as CCS or the Elprotronic tool?   With UniFlash you could even compare flashing the .out and the .hex.

    Regards,

    John

  • 0 in reply to JohnS
    Prodigy 30 points

    Hello,

    Thank you for you suggestion.

    Working from home means that I do not have immediate access to the gangpro, but I did use the UniFlash to flash the .out & .hex files to the boards so thank you for the lead on that valuable tool.

    In the experiment I was able to determine that CCS, the .out & .hex file all consumed the same current. With that said, I did watch the board consume 6x the nominal current when flashed with the .hex file before re-flashing. I am uncertain if this is relevant to the situation, but it was the same current that we were seeing repeatedly with the GangPro-CC.

    I would like to keep this open until we have a change to dig into this further perhaps we will find the root cause of this discrepancy.

    Thank you for the support thus far.

    -Philip

  • 0 in reply to Philip Tifone
    TI__Guru**** 162325 points

    Philip,

    I asked one of our guys what to use for the hex settings.  He mentioned that the default memwidth is 32 and that would be what he would use.  Does the gang programmer want 8bit?

    There is a chapter in the help that has more info:

    That said I am not sure why this would lead to increased power consumption.

    I am hoping that you can get consistent results with UniFlash programming the .hex and .out and that way it points to something specific when using the gang programmer.

    Regards,

    John