LAUNCHXL-CC1352R1: DMM

Hi Yash,

I will ask a TI 15.4 expert to get back to you on the sensor/collector part of your question, in the mean while, which SDK version are you using?

Regarding OAD, we don't have any DMM examples featuring OAD as of today, but I would expect this to be possible. As for the steps to do this, I would assume the guide to be sufficient. The error message suggest you already have theses variables declared at some point in your application, I would try to identify where and why as a starting point.

Hello M-W,

Thanks for replying.
I'm using SImpleLink SDK 2.30.00.45.

And regarding OAD, Thanks for your suggestion I was able to solve that error. But a new error occurs error saying - "unresolved symbol __cfg, first referenced in whole program".
And I think i figured out the reason for that. The link i was following asked to delete the "ccfg_app_ble.c" file (under Startup folder). But as soon as i delete it and build the program again i encounter the aforementioned error.

I tried keeping that file, and it builds successfully but it behaves in a strange manner. the first time i see what i am supposed to see on the DMM terminal and after configuration it starts sending data to the Collector. But when i press the reset button, the terminal displays the UI which was mentioned in the project_zero example, and the senor stops sending data.
So my question is, how can i make the DMM and OAD work together? Is this behaviour because of the "ccfg_app_ble.c" file I didn't delete or is it something else?

Thanks and Regards,
Yash.

Hi,

Following are the updates since my last message.

Firstly, the project_zero code was running after reset because the BIM was loading the image after Reset. After i flashed the erase_storage_offchip file, that didn't happen again.So I guess that problem is now solved.

Secondly, while going through the BLE user guide and the Simplelink Academy tutorial I saw the following statements-

"As of BLE5-Stack 1.00.00 BIM is always linked to page 31 of internal flash, and will always link the CCFG section with it. Thus the OAD application will not need its own CCFG. "
and
“The BIM is responsible for linking and defining the CCFG structure, instead of the application as in the non OAD case. This ensures that the device always will always execute the BIM after boot.”

So it is sort of a given that we can’t keep both ccfg_app_ble.c file (under the Startup Folder in the project) and use the BIM at the same time. Now to use BIM, I will have to delete the ccfg_app_ble.c file (as BIM links the CCFG file itself)

Is the above understanding correct? If yes, then coming back to my question again, what changes will I have to make to remove this error,

P.S- Just a reminder, the very first question I asked still persists- "The Sensor/collector address part".

Thanks,

Yash.

Hi Yash,

As of today, we have not yet provided "OAD enabled" DMM examples, and I would assume the current examples to be designed as a "OAD applications". I'm not able to give you exact pointers on what you have to do to solve this error, but searching your project for the symbol could be a start.

Hello M-W,

Okay, Thank you for your response.

Regards,
Yash

Hello Hector,
Thank you for responding and sorry for my late reply.

I'm confused,
As you said "The device has been deleted on the collector side and it has no record of this device being part of the network previously ", shouldn't the short address allocated also be deleted and the shouldn't the collector assume the device as a new device and assign the address 0x01 again?

Assuming my understanding is wrong and the collector won't use the same address again, Is there any workaround for this? any way to stop it from reassigning new address and making it remember the last device address (basically reusing the short address)?

Thanks and Regards,
Yash.