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.

CC2531: CC2531

Part Number: CC2531

I've been tinkering with some CC25xx chips, using SDCC and a download utility (cc-tool) running on Linux. The download utility talks to a SmartRF04EB interface, so uses that protocol rather than what's documented for the CC25xx series chips.

Where can I find a full description of the SmartRF04EB protocol, so that I can extend the download utility to act as an interactive debugger? This information must have been available to IAR to enable them to do the job.

MarkMLl

  • Please refer to the following: http://www.ti.com/lit/swru039 

    Regards,
    Ryan

  • Thanks for that, which is at least concise :-)

    Referring to Fig 13 in Section 8, and assuming that the firmware running on the Silicon Labs device presents an identification of 11a0:eb20 to a host PC, what are the debugging commands that are sent from the host to the SmartRF04 board?

    The cc-tool program I'm enhancing can program Flash etc., and using existing facilities I've plumbed in interactive commands to inspect and in some cases modify memory. I don't, however, have information on the commands to set breakpoints, inspect the PC, single-step etc., and those commands that I already have don't look quite like the ones expected by the CC25xx chip itself.

    MarkMLl

  • Hi Mark,

    The debugging commands sent over USB is part of a TI proprietary driver which could not be shared here on the forums. I could (and will) check if this is something that could be considered to be made public but I would not count on it due to the expectation that releasing something often comes with.

  • Thanks very much for the response. Any light you could throw on this would be very much appreciated, and I'd like to think that "the powers that be" understand that increasing the accessibility of the development tools ultimately results in increased sales of the target hardware.

    In my case I have some low-cost modules with CC2531 chips which I'm evaluating for various short-range applications, I find available open-source compilers etc. and a minimal loader adequate but being able to exploit the chips' debugging capability really would be "icing on the cake".

    I'll mark this as resolved for the moment, and would appreciate it if you'd contact me if you come up with anything.

    MarkMLl