Other Parts Discussed in Thread: Z-STACK, , TIMAC, SIMPLELINK-CC13X2-26X2-SDK
Does anyone have experience in porting ZBOSS ( public version v1.0 ) for CC2652 ???
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.
Does anyone have experience in porting ZBOSS ( public version v1.0 ) for CC2652 ???
Hi Georgi,
I am not familiar with this solution, but according to the Wiki it is clear that only CC25XX devices are supported. You should consider ZBOSS 3.0 or Z-Stack from the SIMPLELINK-CC13X2-26X2-SDK for CC2652P Zigbee development.
Regards,
Ryan
Hi
ZBOSS 3.0 is not free and I not use TI Z-Stack ( only driverlib )...
I try to port Arduino for CC2652 https://github.com/Wiz-IO
last log:
.....
[TRACE] lib\ZBOSS\src\nwk\nwk_join.c( 223 ) ::: No dev for join
[TRACE] lib\ZBOSS\src\nwk\nwk_join.c( 276 ) ::: <<assoc_join 195
[TRACE] lib\ZBOSS\src\nwk\nwk_join.c( 929 ) ::: <<join_req 0
[TRACE] lib\ZBOSS\src\zdo\zdo_app.c( 432 ) ::: >>nlme_join_conf 2
[TRACE] lib\ZBOSS\src\zdo\zdo_app.c( 485 ) ::: assoc j failed st 195
[TRACE] lib\ZBOSS\src\zdo\zdo_app.c( 490 ) ::: <<nlme_join_conf
[ZB] zb_zdo_startup_complete()
[TRACE] lib\ZBOSS\src\port\cc2652.c( 105 ) ::: Device start FAILED status 195
Great project, unfortunately I am not able to further assist with this resource.
Regards,
Ryan
how to calculate exactly TIMER_A ( 16 bit mode) the Prescaler and LoadSet for 15360 uSec ( baecon )
now works but is not accurate...
BTW: I thing, ZBOSS is ready but need more tests
loadMatchVal = 15360u // uSec
/* Upper byte is used by prescaler */
uint8_t prescaleValue = 0xFF & (loadMatchVal >> 16);
/* Discard upper byte (24 bits max) */
loadMatchVal &= 0xFFFF;
Timer and GPTimer are two different TI Drivers with various parameters. In your case, from the GPTimerCC26XX.h example, I would use 64 as the loadMatchVal since this is one divided by .01536 (minus one). Another option to evaluate is the Clock module.
Regards,
Ryan
are you have time to reverse TI SDK ?????
GPTimer (16 bit mode ... onli TIMER_A )...
is there is formula - how to calculate loadset & prescaler
All information is given in the documentation of the resources I've provided.
Regards,
Ryan
I don`t know is zigbee2mqtt (my coordinator is 3.0) compatible with ZigBee 2007 ( ZBOSS v1.0 OpenSource version )
BTW: ZBOSS 3.0 ... is compiled with 72 missing functions as NVRAM access and OSIF & HAL API
Zigbee 3.0 can be backwards compatible with previous Zigbee Specifications, and I know that for zigbee2mqtt it is at least operational with Z-Stack HA 1.2 devices. But you appear to be working with quite an old version of Zigbee, Koen Kanters may know if any devices with this stack version have been tested before.
You'd have to speak with DSR with respect to your ZBOSS issues.
Regards,
Ryan
Zigbee 3.0 can be backwards
NICE!
I continue with the experiments....
DSR, they don't answer me
the problem
DSR say .... "don`t ask"...
[] nwk_join.c( 156 ) ::: ne 0x2000242c is not potential parent: panid_ok 1 potent_prnt_ok 0 permit_j_ok 1 cap_ok 1 lqi_ok 1 upd_id_ok 1
[] nwk_join.c( 160 ) ::: <<nwk_choose_parent 0x0
[] nwk_join.c( 223 ) ::: No dev for join....
I thing I found the problem
The node send indirect join request
the coordinator send ACK
here I need to wait response of the join request
but, because there is no ZBOSS documentation, I don`t know how to signal for pending packet
The stack say no indirect response - abort joint...
and response return after this ... with join OK
I will investigate...
[TRACE] zdo_app.c( 440 ) ::: CONGRATULATIONS!
joined status 0, addr 25491, xpanid 0.12.4b.0.22.a5.38.89, ch 12, addr 0x6393
...
[ZB] zb_zdo_startup_complete(----------------------------------------)
[TRACE] cc2652.c( 146 ) ::: Device STARTED OK
[ZB] zb_zdo_startup_complete(---------------- DONE ------------------)
Unfortunately ZBOSS 1.0 not have ZCL and zigbee2mqtt work to device join...
I will port ZStack for experiments
Unfortunately .... ZStack v3,0,2 (8051 version) missing MAC library source code
and last version from SimpleLink is totally mish-mash for GCC compilation without SDK drivers and without TI OS ... brrrr
somehow I managed to compile it, but it will hardly work...
TI, Do you have any basic compilation for GCC ?
I know... need MAC library SRC code to recompile with GCC, but maybe is not free this code
but now I use MAC ROM lib ... just need to port OSAL as for Arduino loop
BTW: MAC library is soft library - not need hardware dependencies
I know .... not need ...
I porting ZStack for CC2652 ( is ARM M4 ) for my PlatformIO/Arduino project
just need MAC src, but this lib exist in ROM
Hello Georgi,
SimpleLink source library/ROM code is only provided for critical business opportunities. You can contact your local TI FAE or Sales Representative to commence an off-forum conversation about this topic.
Regards,
Ryan
OH !!!! I lose my time....
so ROM lib not exist and library is only for IAR + RTOS ... and I need loop for Arduino ( GCC )...
and if TI Zigbee Team are willing to help - you have my email...
for "default" simple user CC2652 SoC - I need this library: maclib_sm_cc26x2_2_4g.a ???
SimpleLink source library/ROM code
Ryan, can you explain file: timac_rom_PG2_0_rom_api_linker.cmd
The ROM starts at memory address 0x10000000 and is 256 kB long. IEEE 802.15.4-based SDK projects use timac_rom_PG2_0_rom_api_linker.cmd to link IEEE 802.15.4 radio stack operations stored in ROM. Since their locations cannot be altered this file should not be modified.
Regards,
Ryan
SimpleLink source library/ROM code is only provided for critical business opportunities.
you say this...
so, The "half" MAC library exis in ROM, next "half" is in lib: maclib_XXX_cc26x2_2_4g.a
only missing "nwk_bufs.c"... maybe and other...
BTW: I not need ROM source code, I just want to port existing code & libraries
Yes, some IEEE 802.15.4 radio stack operations exist in ROM, others are pre-built libraries. And nwk_bufs.c is located inside Z-Stack source code (i.e. pre-built libraries). Please continue this conversation offline for further interest in source code.
Regards,
Ryan
I not need Z-Stack source code... btw nwk_bufs.c is not shared in last SDK ( not exist and in old SDK-s )
I unpack libraries and get compiled object
BTW: Z-Stack it totally mish-mash SDK and can not be used independently from SDK
theoretically, the external source should be User code and OSALL, but this is not the case
and there are really no source codes or if they are compiled, they are dependent on RTOS and drivers
What progress are you asking for? It's been made clear that offline communication is required for interest in files not provide in the SIMPLELINK-CC13X2-26X2-SDK release software package.
Regards,
Ryan
Ryan !!!
how many times should I write to you: I don't need the source codes !!!
YOUR SUPPORT IS VERY BAD
Please give me contact of your manager !!!!
I apologize for the confusion then, I can alert my manager to this thread and you can contact me for their information. Meanwhile, can you please clarify what you are looking for?
Regards,
Ryan
Online support say: go to E2E forum...
You say: go to offline...
FAE say: go to E2E forum
last ... WHERE TO GO? is there at all ТI support
any contact with ZigBee SDK Team?
I've sent you a Friendship Request and will continue this conversation through private messaging.
Regards,
Ryan
Hi Team,
Will there be ZBOSS 3.0 for TI chips ???
screenshot: JOIN to zigbee2mqtt ( ZBOSS 3 hacked version )
Hi Georgi,
That appears to be a question for DSR. As far as I am aware, ZBOSS 3.0 already supports SimpleLink CC13X2 & CC26X2 devices.
Regards,
Ryan
Yep, but they ask money...
I wondered if TI did not have an official ZBOSS 3.0 SDK ( any as for OpenSource projects )
for my tests I use "illegal" SDK libraries...
TI offers Z-Stack 3.0 as part of the SIMPLELINK-CC13X2-26X2-SDK.
Regards,
Ryan
Z-Stack is strongly associated with TI SDK .... and is very difficult to be use independently
.... 4G pack ... wow
Hi Ryan
is this ROM functions valid for default chip
void z_init(void)
{
TIMAC_ROM_Init();
MAC_Init(); <------- this make hardware trap
...