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: Run the same firmware on CC1352R and CC1352P

Part Number: CC1352R
Other Parts Discussed in Thread: SYSCONFIG, , CC1352P

Hi,

We are now using both R- and P-model of the CC1352 and I run the same FW on both devices except that I use a different sysconfig file during build and some #define statements to distinguish between both versions.

I would like to be able to make these check during runtime and have only one FW that can run on both MCU's.

This would make distributing FW easier. e.g. OAD which now does not differentiate between R and P.

Can this be done? / What needs to be done?

Thanks,

Marijn

  • Hi Marijn,

    The PA field in the USER_ID register in FCFG1 can be used to to differentiate between the R and P models. 
    Please take a look at Table 11-64 in the Technical Reference Manual.

    Regards,
    Nikolaj

  • Hi Nikolai,

    Great, Thanks, I found it.

    Now can I just program the P version then with the sysconfig used by the R version so I can setup the different IO's in runtime?

    BTW I'm not using the P's 20dB amplifier so there is no other differences?

    Thanks,

    Marijn

  • Hi Marijn,

    I want to make sure I understand your question correctly and what you want to achieve.

    Do you just want to use the P device as a direct drop in replacement for the R device? Why are you using the P device if you are not using the 20dB amplifier?

    Why do you need to differentiate between the two variants (R and P) during runtime?

    so I can setup the different IO's in runtime

    Do you need to setup the IO's differently for the R and P devices?

    Thanks,
    Nikolaj
     

  • Hi Nikolaj,

    Sorry, I get your confusion.

    Yes we want to use the P-device as a drop-in replacement only because of component shortage. Availability of the R is even worse then the P. So thats why there is no need for the 20dB.

    We need to setup a few IO's differently because we actually use the pins that are taken up by the 20dB output.

    That in itself is not an issue because we can just skip them from sysconfig and configure them in code.

    So what I want to know actually is what I need to do to run the 'R' firmware on the 'P' device (apart from the change in IO setup).

  • Does that mean you are using DIO3 and DIO4 on CC1352R?

    It's not possible to reconfigure any of these pins to DIOs if that is your question (from the CC1352P datasheet):

    The 32 kHz osc xtal is also on different pins for CC1352R and CC1352P. 

    How have you planned the HW differences between the R and P?  

  • Hi TER,

    Yes we are doing a hardware redesign for the P version that has no DIO3 and DIO4 in use and indeed also with the 32kHz osc on the different pins.

    So R and P both have different boards but are trying to get them on the same firmware.

  • Ok, meaning that you want to use DIO3 and DIO4 on the R based board and hence need DIO setup dependent on the target device? 

    I believe it's some device dependent checks in the GPIO(++) and pin driver to ensure that you are not using a DIO that is not available. If you base your SW on CC1352R this shouldn't be an issue. Since you have separate HW I believe you should be ok with just setting the DIOs (no other changes should be required)  

  • Correct, DIO3 & DIO4 are used in R but not in P based board.

    Great to hear that it should work. This will save a lot of time not having to manage different FW packages.

  • A note: Here I have assumed that both boards uses external load caps for the 48 MHz xtal.