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.

CC1352P7: Device revision '0x3' unknown for selected target. Assuming latest known revision: Rev. 1.0.

Part Number: CC1352P7
Other Parts Discussed in Thread: SYSCONFIG,

I have a new custom board that uses a CC1352P7 chip, and I'm struggling to create a working project for this chip. I have an exiting project for a similar board using a CC1312 chip, using the Simplelink SDK v5.20, and my first attempt to create a project was to clone that and use the target migration tool in Sysconfig v1.8.2 and provide the appropriate linker script. Trying to build and flash that project returned the title error, and the debug session appeared to hang without actually entering code regions.

My next step was to take an example project for the target chip and clone that, but Resource Explorer no longer appears to support the SDK v5.20, presumably given the changed name going to v5.40. I took the 'hello' project from the SDK v5.40 example set and found that I was able to flash the device and step through code, but I was still getting the title error.

The next step after that was porting the code from the CC1312 project into a clone of the hello project for CC1352P7, but now I'm also seeing 'Loader: One or more sections of your program falls into a memory region that is not writable.  These regions will not actually be written to the target.  Check your linker configuration and/or memory map.' in addition to the title error. Why would the 'cc13x2x7_cc26x2x7_tirtos.cmd' linker file be placing program information in non-writable locations?

All 'flashing' operations are through cJTAG.

What is causing the title error, and what can be done to resolve it?