CC2652R: Enable PTM & BSL backdoor in simple_peripheral_oad_onchip

Hi Jo,

I have assigned an expert to help with your query.

Regards,

Jan

Hi Jo,

Boot Serial Loader (BSL) and PTM are supported on simple_peripheral examples. When it comes to simple_peripheral_oad_onchip, the challenge might be the flash available. From your description it does not seem to be the case.

I would recommend to implement these two features one by one. That way you can be sure one is working before implementing the other.

If you wish to get more help, it would be nice if you could specify the SDK version used, the observations you are doing (i.e. explain what "not working" means to you), etc.

Make sure to leverage all our documentation:

• https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_5_10_00_48/docs/ble5stack/ble_user_guide/html/ble-stack-5.x-guide/ble5-oad-index-cc13x2_26x2.html
• https://dev.ti.com/tirex/content/simplelink_academy_cc13x2_26x2sdk_5_10_00_00/modules/ble5stack/ble_enhanced_oad/ble_enhanced_oad.html
• https://www.ti.com/lit/swra466
• https://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_5_10_00_48/docs/ble5stack/ble_user_guide/html/ble-stack-5.x/creating-a-custom-bluetooth-low-energy-application-cc13x2_26x2.html#production-test-mode-ptm

Best regards,

Hi Clement,

I tested with both SDKv4.40 & v5.10. I was using bim_onchip & simple_peripheral_oad_onchip projects. here's my flow for BSL mode testing:

1. change both project sttings to "Release"

2. in simple_peripherals syscfg, change backdoor pin to DIO11, active low.

3. build two projects and get .hex files, then program them by Uniflash like below:

4. pull low DIO11 and power cycled to enter BSL and send two 0x55 characters. I didn't see the device's acknowledge. (0xCC or 0x33) meaning it's not in BSL.

5. pull high DIO11 and reset device to run app freely, however there's no simple_peripheral app message showing on UART. meaning it's not running correctly. 

As for PTM, I'm expecting the device with oad + PTM can interact with Btool like other example projects with PTM checked. It did not take PTM Cmds, does it need any SW or HW invocation to get in PTM?

In short, the "BSL & PTM not working" means the device didn't take BSL and PTM Cmds. 

I probably did it wrong so I will spend more time on the references you provided first, and if you have some tips for bringing the device up, I will be very appreciated.

Regards,

Jo

Hi Jo,

Keep me updated :)

I would recommend to start by verifying you have properly set up the target (see this subset of the documentation).

Best regards,

hi Clement,

By comparing normal simple_peripheral and one with oad, I found the latter's syscfg does not generate ti_device_config.c which means the backdoor as well as BSL thing was not configurable through syscfg. How can I manually add related settings in this project? And I think PTM is the same situation.

Thanks, 

Jo 

Hi Jo,

I confirm, the file ti_devices_config.c - used to set-up the CCFG parameters - is not generated for OAD examples. This is because the CCFG region is set by the BIM - this is why the CCFG cannot be altered through OAD.

As a consequence, in order to enable the Bootloader Backdoor you will be required to modify the BIM. The BIM project is stored in <SDK>\nortos\<DEVICE>\bim\. Once you have imported the project in CCS, the CCFG configuration is in Application/ccfg_app.c - review the comments before editing the file. Leverage the code generate by SysConfig for non-OAD project. Once done, rebuild the CFG for the configuration you want.

With that being said:

1. It is important you first fix the out-of-the-box example. If this does not work, it is going to be difficult to assess if the rest behaves properly.
2. PTM is NOT related to CCFG configuration. As a consequence, the solution suggested before will not have any impact. If the BLE example does not work properly, it is very unlikely PTM does.

I hope this will help,

Regards,

Hi Clement,

I searched PTM_MODE in both simple_peripheral projects, and as you can see the oad one does not even include NPI folder and related files. That's why I said it's similar to the CCFG case, it is not supported in syscfg at all.

Now I need a quick and simple way to add PTM into OAD project for my customer, please advise.

regards,

Jo

Hi Jo,

Could you tell me if you have managed to run the out-of-the-box project? Could you tell me if you have managed to enable the Backdoor Bootloader? Again, we have to address the issues one by one if not we will never get anything working.

When it comes to PTM, you should first assess if the available flash will be sufficient to fit OAD and PTM - it should be ok. Then, please refer to this thread.

Regards,

Hi Clement,

Thanks for prompt reply. Yes! I can run out-of-box (project Zero). I'm a bit confused from here, do you want me to add CCFG settings in BIM or project Zero? I want to know how to for both, but the BSL thing can wait because my customer won't expose interface for end customer to do firmware update, and BIM seems not necessarily to be updated. instead, the end customer will program the device over the air. Sorry for not clarifying on that, my urgent request is PTM and OAD. From the discussion for integrating PTM it looks quite a lot of work. Do you happen to have one project with OAD + PTM enabled?

And if the size of internal flash is an issue I need to let them know asap. From project Zero the occupied flash size is 0x240dc, 0x31ff4 left, I think it's on the margin. 

Regards,