As I am using a csr1024 I hope I am in the correct sub forum.
We have succesfully implemented CSRmesh on csr1010. No we are using a csr1024 mainly because of the 4 hardware link layers inside.
We have created our own PCB with this chip and can confirm that it works seeing as I am the first one to post in the csr102* family section.
My question however is regarding the programming of the UUID and Authorization_code for association the device.
For the csr1010 this is documented as using uEnergyProdTest.exe (I have translated the addresses and written them using a different tool.
<CSR_uEnergy_Tools path>\uEnergyProdTest.exe –k
CSRmeshbridge_CSR101x_A05.keyr –m1 0x02 0x3210 0x7654 0xBA98
0xFEDC 0xCDEF 0x89AB 0x4567 0x0123 0xCDEF 0x89AB 0x4567 0x0123
The csr1024 has a different layout regarding memory layout where we have User Stores, Application Stores and Configuration Stores.
Can you provide any insight in where I am expected to program the UUID and Authorization_code in the csr1024?
Perhaps I am overlooking this information in the documentation.
Kind regards,
Thomas van Kleef
After some digging, I have resolved the issue myself and I am now able to use CSRmesh on the 1024.
The offsets @ mesh_common\components\nvm_manager\nvm_acces.c were helpfull.
For programming the UUID and AC i will use the offset locations I have found them to be stored (the offsets will vary with changes to the code) and will use a custom tool for programming these offsets.
Kind regards,
Thomas van Kleef
Dear Thomas van Kleef,
Can I check with you if the CSRMesh messages have interoperability between CSR1010 and CSR102x?
Regards,
Karthik
Just a tad too soon. I am a week from confirming that (sending message from csr1010 to csr1024) myself. I shall post my findings here. What I can confirm is that at least the CSRmesh stack works on both device families. The only change is the SDK which is used 3.x for csr102*, 2.x for csr101*. Communicating with the devices works from the controller (android and ios).
Based on my results until now I assume the following: csr101x and csr102x are different chips, where the most significant change is that the latter contains multiple Hardware Link Layers which enable multiple users to be connected to the device. This is also the reason for the connection manager in software which handles multiple client connections. In order to use this chip a different SDK has been developed (3.x) which contains software for supporting the hardware link layers..
Until now everything hints that I will be able to send a message from the csr1010 to the 1024. I am 99.9999% sure it will. However I shall post a confirmation here when I actually implemented this myself. :)
Kind Regards,
Thomas van Kleef
Thanks for information!!
Karthikeyan.t
"Can I check with you if the CSRMesh messages have interoperability between CSR1010 and CSR102x?"
I can confirm this now. Right now I am sending data from a csr1010 chip to a csr1024 which receives this data. Even when connected to the csr1024 I am able to receive this data both on the csr1024 and the connected controller (Android).
Kind regards,
Thomas
Thanks!