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.

CC1352R: Where's the documentation for the ROM on the CC1352R?

Part Number: CC1352R
Other Parts Discussed in Thread: SEGGER

I'm specifically looking for the memory map of the ROM on the CC1352R.  I'm trying to bring up an example from the CC1352 SDK using GCC and the libraries in ROM, and the code keeps dying in what I assume is ROM.  I say assume because I cannot find any documentation on where exactly the ROM is located on the CC1352 and what is located where within in ROM.  The Technical Reference Manual has some vague references to ROM, but does not say what is located where.  Same with the CC1352 datasheet.

For example, let's say I was trying to figure out where something was going wrong in the ROM bootloader.  There is NO information in the TRM or datasheet that says where the bootloader is located in ROM.  If I pause the debugger and all I have is a current instruction memory location, how can find out where in the bootloader that instruction is to figure out what is going wrong?

Likewise, where can I find the documentation that has the address range of driverlib? What drivers are located where?

It's a massive pain trying to debug firmware when you can't figure out where something went wrong.

My apologies for the ranty-nature of this question.  I've been pounding against problem after problem trying to get my CC1352 to do...anything, and the documentation has proven to be less than enlightening.

  • First to the basics: Could you confirm that you are using a rev E of CC1352R? See https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/767774 for details. 

    If you have a rev E, which example are you trying to run from which SDK and I can try to recreate the issue on our side. 

  • Any update on this? 

  • I'm waiting to get confirmation that it's an E rev.  I'm working remotely and don't have physical access to the hardware. 

    Also, I was misreading my symptoms.  I'm trying to run the rfEasyLinkTX example under /sdk/examples/nortos/CC1352R1_LAUNCHXL/easylink and breakpoints in rfEaslyLinkTx_nortos.c simply don't get hit.  The call stack always winds up in the 0x10000xxxx address range when I pause the program execution.  I can step through the assembly and come out to actual source code.  I've attached a screenshot of the call stack.  I'm using GCC for the toolchain and Visual Studio with VisualGDB for the IDE. 

    Whenever I pause the program while running, the instruction register is always pointing at 0x1000060a.

  • When will you get an confirmation on which version you are using? 

  • Confirmed using the E version of the micro and I'm using SDK 3.2.0.68

  • I'm not sure what I did to get the sample to work, but I added Segger's RTT and added some debug statements in the main loop in "rfEaslyLinkTx_nortox.c", and as far as I can tell, the example is working.  No idea what I did to fix it (or if there ever actually was a problem).

  • Then I will close this one and if you have further questions you can post an update in this thread.