telink_zigbee_ble_concurrent_sdk-2.4.1.0 issue

wes58 · 发表于 4 天前

I am trying to convert my old project (Zigbee cooridnator) from TLSR8258 to TL7218 and I can't understand why it is so hard to do.

Here are some of the issues I found:

#1 Creating new project.

To create new project configuration you choose option to copy settings from existing configuration - like in all previous SDK's

To exclude this existing app from build of the new project app you go to Resource Configurations->Exclude From Build and select this app.

It used to work with all previous SDKs. But now when you compile new app it is still looking for the app that was used when creating new configuration. Now, I had to go through all the settings and look what was causing the problem

#2 In the sampleGateway app there are files sampleGatewayMultiBLEController.c and sampleGatewayMultiBLE.c. When I create new project app based on this example, and I have both files in my new app the project doesn't compile because there is nothing that decides which file should be used and it is using both files. I had to delete one of the files for the project to compile.

I am not sure how it works with SampleGateway example!

#3 Other issues related to the conversion of the TLSR8258 project files to TL7218 due to the functions and other const. that were changed/removed in TL7218 API

In TLSR8258 project I used the following function to check link state:

`if(blc_ll_getCurrentState() == BLS_LINK_STATE_ADV) {}`

And of course this function and enumeration of link state don't exist in TL7218 API.

After searching through header files I found function blc_ll_getBleCurrentState() and I use it like this:

`if(blc_ll_getBleCurrentState() == BLE_STATUS_ADVERTISING){}`

Could you please confirm that it is the correct function?

Second issue.

In TLSR8258 I used the following function:

`bls_att_pushNotifyData(RxTx_CMD_OUT_DP_H, txBuf, p - txBuf);`

What is the equivalent function to use in TL7218 API?

I would appreciate your help.

TL_YANGBIN · 发表于 4 天前

wes58 · 发表于 3 天前

<div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102362&ptid=98603" target="_blank"><font color="#999999">TL_YANGBIN 发表于 2026-9-7 21:09</font></a></font>
8258 is the TC32 (Telink Core) platform, and 721x is the RISC-V platform, with significant differenc ...</blockquote></div>

That's what I tried to do. And I wrote about the issues I encounterd.

The issue is not only "...significant differences in their compilation environments." but that someone decided to change function names, remove some functions, enumerations etc. So if you are working on projects using both TLSR8258 and TL7218 you can't just use the same code.

What I wrote in my previous post:

#3 Other issues related to the conversion of the TLSR8258 project  files to TL7218 due to the functions and other const. that were  changed/removed in TL7218 API

In TLSR8258 project I used the following function to check link state:

`if(blc_ll_getCurrentState() == BLS_LINK_STATE_ADV) {}`

And of course this function and enumeration of link state don't exist in TL7218 API.

After searching through header files I found function blc\_ll\_getBleCurrentState() and I use it like this:

`if(blc_ll_getBleCurrentState() == BLE_STATUS_ADVERTISING){}`

**Could you please confirm that it is the correct function?**

Second issue.

In TLSR8258 I used the following function:

`bls_att_pushNotifyData(RxTx_CMD_OUT_DP_H, txBuf, p - txBuf);`

**What is the equivalent function to use in TL7218 API?**

wes58 · 发表于 3 天前

TL_HUANLI · 发表于 3 天前

wes58 · 发表于前天 06:48

<div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102377&ptid=98603" target="_blank"><font color="#999999">TL_HUANLI 发表于 2026-9-8 15:13</font></a></font>
The BLE in the zigbee_ble_8258 SDK is single-connection, while the 721x supports multiple connection ...</blockquote></div>

I found out after a lot of wasted time what caused this exception:

`pc : 0x041604  j        0x41600        <trap_entry+0x5c> `

`pc : 0x041600  c.nop `

`pc : 0x041604  j        0x41600        <trap_entry+0x5c> `

`pc : 0x041602  c.nop `

`pc : 0x041604  j        0x41600        <trap_entry+0x5c>`

In app_cfg.ini there is the following:

`/* Flash protect module */ `

`/* Only the firmware area will be locked, the NV data area will not be locked.`

`*For details, please refer to drv_flash.c file. */ `

`#define FLASH_PROTECT_ENABLE                        1`

When I change to:`#define FLASH_PROTECT_ENABLE   0`the program crashes.

Why can't I disable flash protection?

TL_HUANLI · 发表于前天 10:46

wes58 · 发表于前天 16:18

TL_HUANLI · 发表于昨天 18:55

wes58 · 发表于 16 小时前

<div class="quote"><blockquote><font size="2"><a href="https://forum.telink-semi.cn/forum.php?mod=redirect&goto=findpost&pid=102815&ptid=98603" target="_blank"><font color="#999999">TL_HUANLI 发表于 2026-9-10 18:55</font></a></font>
Yesterday I already pulled the code from GitHub and only changed the FLASH\_PROTECT\_ENABLE macro. I ...</blockquote></div>

I checked what changes I made to sampleGateway that I used to compile it.

I found that the line that I added before `blc_smp_smpParamInit();` is causing an exception:

`blc_smp_setSecurityParameters(Bondable_Mode, 1, LE_Secure_Connection, 0, 0, IO_CAPABILITY_DISPLAY_ONLY);`

You wrote before that I can check the code in except_handler but in your example you have the following function to show whether excetpion occurred:

```
static void sampleGwSysException(void) {
#if 0
        SYSTEM_RESET();
#else 
        gpio_toggle(LED_POWER);
        while(1);
#endif 
}

static void sampleGwSysException(void) {
#if 0
SYSTEM_RESET();
#else
gpio_toggle(LED_POWER);
while(1);
#endif
}

```

So why LED_POWER doesn't turn on when exception occurred?

#2 I have another problem with the code ported from my old TLSR8258 project to TL7218.

I have a function int RxTxWrite(void * p) where I receive data sent from my phone via BLE. It has been working fine on TLSR8258 for many years but it doesn't work with TL7218.

I send for example the following command to get all joined nodes `5500400000`

The data received in RxTxWrite function is wrong and is the same no matter what data I send from the phone

> [13:00:04]:
> TC32 EVK: Swire ok
> 255 byte(s) have finished
> 00050364: 37 23 4e 0e 13 03 03 c0 23 a0 62 00 b7 02 14 80
> 00050374: 93 82 22 16 05 43 23 80 62 00 97 b1 00 00 93 81
> 00050384: c1 e2 b7 02 10 80 93 82 02 70 01 43 a3 80 62 50
> 00050394: 97 02 04 00 93 82 62 f8 16 81 8b 12 cd ff 82 92
> 000503a4: 8b 12 1d 98 82 92 99 62 f3 a2 02 30 73 10 30 00
> 000503b4: 8b 92 0f d7 73 90 52 30 73 60 01 7d b7 02 00 c4
> 000503c4: 09 43 23 a0 62 00 f3 22 a0 7c 93 e2 12 00 93 e2
> 000503d4: 22 00 73 90 a2 7c 0f 10 00 00 b7 f2 ff a3 93 82
> 000503e4: 02 79 39 43 23 86 62 78 b7 f2 ff a3 93 82 02 79
> 000503f4: 83 83 82 79 13 0e 00 08 e3 08 7e fe b7 f2 ff a3
> 00050404: 93 82 02 79 19 43 23 86 62 78 81 43 23 8e 72 76
> 00050414: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00050424: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00050434: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00050444: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00050454: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0
> [13:00:04]: Total time: 185 ms

Variable MyRxTxData (in BDT) has nothing in it as well. So I am not sure where the received data is stored.

Here is the code that I am using:

```
typedef enum {
ATT_H_START = 0,
...
...
//// Custom RxTx ////
/**********************************************************************************************/
RxTx_PS_H,                                                                 //UUID: 2800,         VALUE: 1F10 RxTx service uuid
RxTx_CMD_OUT_CD_H,                                                //UUID: 2803,         VALUE:                          Prop: read | write_without_rsp
RxTx_CMD_OUT_DP_H,                                                //UUID: 1F1F,  VALUE: RxTxData
RxTx_CMD_OUT_DESC_H,                                        //UUID: 2902,         VALUE: RxTxValueInCCC

ATT_END_H,
} ATT_HANDLE;

// RxTx Char
const  u16 my_RxTxUUID                        = 0x1f1f;
const  u16 my_RxTx_ServiceUUID        = 0x1f10;
_attribute_data_retention_ u8 my_RxTx_Data[16];
_attribute_data_retention_ u8 RxTxValueInCCC[2];

//// RxTx attribute values
static const u8 my_RxTxCharVal[5] = {
CHAR_PROP_READ | CHAR_PROP_NOTIFY | CHAR_PROP_WRITE_WITHOUT_RSP,
U16_LO(RxTx_CMD_OUT_DP_H), U16_HI(RxTx_CMD_OUT_DP_H),
U16_LO(0x1f1f), U16_HI(0x1f1f)
};

static const attribute_t my_Attributes[] = {

{ATT_END_H - 1, 0 , 0, 0, NULL, NULL, NULL, NULL},  // total num of attribute
...
...

// RxTx Communication
{4,ATT_PERMISSIONS_READ,2,2,(u8*)(&my_primaryServiceUUID),         (u8*)(&my_RxTx_ServiceUUID), 0},
{0,ATT_PERMISSIONS_READ, 2,sizeof(my_RxTxCharVal),(u8*)(&my_characterUUID),        (u8*)(my_RxTxCharVal), 0},                                //prop
{0,(ATT_PERMISSIONS_READ | ATT_PERMISSIONS_WRITE), 2,sizeof(my_RxTx_Data),(u8*)(&my_RxTxUUID), (u8*)&my_RxTx_Data, &RxTxWrite, 0},
{0,(ATT_PERMISSIONS_READ | ATT_PERMISSIONS_WRITE), 2,sizeof(RxTxValueInCCC),(u8*)(&clientCharacterCfgUUID),         (u8*)(RxTxValueInCCC), 0},        //value
};

u8 zz_data[255] = {0};        //for debugging
int RxTxWrite(void * p){
led_toggle(LED5);
rf_packet_att_data_t *req = (rf_packet_att_data_t*)p;
u8 Len = req->rf_len - 7;        //9;
zz_data[254] = Len;
for(u8 i = 0; i < Len; ++i){
zz_data<i> = req->dat<i>;
}
if(req->dat[0] == 0x55){
u16 cmd_type =  req->dat[1] ;
cmd_type <<= 8;
cmd_type |= req->dat[2] ;
--Len;
notify_resp = 1;
zb_ble_hci_cmd_handler(cmd_type, Len, &(req->dat[3]));
}
}

typedef enum {
ATT_H_START = 0,
...
...
//// Custom RxTx ////
/**********************************************************************************************/
RxTx_PS_H,                                                                 //UUID: 2800,         VALUE: 1F10 RxTx service uuid
RxTx_CMD_OUT_CD_H,                                                //UUID: 2803,         VALUE:                          Prop: read | write_without_rsp
RxTx_CMD_OUT_DP_H,                                                //UUID: 1F1F,  VALUE: RxTxData
RxTx_CMD_OUT_DESC_H,                                        //UUID: 2902,         VALUE: RxTxValueInCCC

ATT_END_H,
} ATT_HANDLE;

// RxTx Char
const  u16 my_RxTxUUID                        = 0x1f1f;
const  u16 my_RxTx_ServiceUUID        = 0x1f10;
attribute_data_retention u8 my_RxTx_Data[16];
attribute_data_retention u8 RxTxValueInCCC[2];

//// RxTx attribute values
static const u8 my_RxTxCharVal[5] = {
CHAR_PROP_READ | CHAR_PROP_NOTIFY | CHAR_PROP_WRITE_WITHOUT_RSP,
U16_LO(RxTx_CMD_OUT_DP_H), U16_HI(RxTx_CMD_OUT_DP_H),
U16_LO(0x1f1f), U16_HI(0x1f1f)
};

static const attribute_t my_Attributes[] = {

{ATT_END_H - 1, 0 , 0, 0, NULL, NULL, NULL, NULL},  // total num of attribute
...
...

// RxTx Communication
{4,ATT_PERMISSIONS_READ,2,2,(u8*)(&my_primaryServiceUUID),         (u8*)(&my_RxTx_ServiceUUID), 0},
{0,ATT_PERMISSIONS_READ, 2,sizeof(my_RxTxCharVal),(u8*)(&my_characterUUID),        (u8*)(my_RxTxCharVal), 0},                                //prop
{0,(ATT_PERMISSIONS_READ | ATT_PERMISSIONS_WRITE), 2,sizeof(my_RxTx_Data),(u8*)(&my_RxTxUUID), (u8*)&my_RxTx_Data, &RxTxWrite, 0},
{0,(ATT_PERMISSIONS_READ | ATT_PERMISSIONS_WRITE), 2,sizeof(RxTxValueInCCC),(u8*)(&clientCharacterCfgUUID),         (u8*)(RxTxValueInCCC), 0},        //value
};

u8 zz_data[255] = {0};        //for debugging
int RxTxWrite(void * p){
led_toggle(LED5);
rf_packet_att_data_t req = (rf_packet_att_data_t)p;
u8 Len = req->rf_len - 7;        //9;
zz_data[254] = Len;
for(u8 i = 0; i < Len; ++i){
zz_data<i> = req->dat<i>;
}
if(req->dat[0] == 0x55){
u16 cmd_type =  req->dat[1] ;
cmd_type <<= 8;
cmd_type |= req->dat[2] ;
--Len;
notify_resp = 1;
zb_ble_hci_cmd_handler(cmd_type, Len, &(req->dat[3]));
}
}

```

Any suggestion what is wrong?

Is it something to do with this line:

```
        {0,(ATT_PERMISSIONS_READ | ATT_PERMISSIONS_WRITE), 2,sizeof(my_RxTx_Data),(u8*)(size_t)(&my_RxTxUUID), (u8*)&my_RxTx_Data, &RxTxWrite, NULL},

```

I get a warning during compilation, but I don't understand because it has been working before:

> ../../../apps/ZGateway/ZGatewayMultiBLE.c:635:132: warning: initialization of 'int (*)(u16,  void *)' {aka 'int (*)(short unsigned int,  void *)'} from incompatible pointer type 'int (*)(void *)' [-Wincompatible-pointer-types]
> 635 |         {0,(ATT_PERMISSIONS_READ | ATT_PERMISSIONS_WRITE), 2,sizeof(my_RxTx_Data),(u8*)(size_t)(&my_RxTxUUID), (u8*)&my_RxTx_Data, &RxTxWrite, NULL},
> |                                                                                                                                    ^
> ../../../apps/ZGateway/ZGatewayMultiBLE.c:635:132: note: (near initialization for 'my_Attributes[34].w')