Zephyr & OpenThread & CC2652 lunchpad

193 views
Skip to first unread message

Valeriy Nyrov

unread,
Jan 16, 2022, 1:40:52 PM1/16/22
to openthread-users
Hello everyone!
I have a CC26X2R1_LAUNCHXL board that I want to use as  FTD device,
but I can not understand how to configure the Zephyr (in menuconfig).
In the dir ../zephyr/os/2.7.99/modules/lib/openthread/example/platforms/cc2652/
there is only a readme.md file, in which it is said that: The OpenThread on CC2652 Example has moved to https://github.com/openthread/ot-cc13x2-cc26x2.
What does it mean? Need to download separately the repository https://github.com/openthread/ot-cc13x2-cc26x2?  If so, how to perform the configuration and assembly?
(I need to generally understand how to integrate an OpenThread into Zephyr for my platform.)

BR,
Valery

Toby Pan

unread,
Jan 18, 2022, 1:59:14 PM1/18/22
to openthread-users
Hi Valery,

The note about "The OpenThread on CC2652 Example has moved to" is inherited from the openthread repository itself.
You should see similar messages for each platform supporting openthread: https://github.com/openthread/openthread/tree/main/examples/platforms

That being said, this development board can be developed as a Thread FTD.

You can then build any of those examples, following the typical flow of TI SDK (an example of this can be found here: https://dev.ti.com/tirex/explore/node?node=APk.N72zgRW8RvRoAhRlUQ__BSEc4rl__LATEST).

From ot-cc13x2-cc26x2 github, you can build the example following this guide: https://github.com/openthread/ot-cc13x2-cc26x2/blob/main/src/cc2652/README.md

Please let us know if you have any further questions.


Thanks,
Toby

Valeriy Nyrov

unread,
Feb 10, 2022, 4:22:20 PM2/10/22
to openthread-users
Hi Toby,
I followed your advice and built the project according to: https://github.com/openthread/ot-cc13x2-cc26x2/blob/main/src/cc2652/README.md
But the size of the generated binary files: ot-cli-ftp (538 660 bytes) and ot-cli-mtd (404 956 bytes) is larger than the CC2652R1F flash memory. What did I do wrong?

Thanks,
Valeriy


вторник, 18 января 2022 г. в 21:59:14 UTC+3, b-...@ti.com:

Seth Rickard

unread,
Feb 10, 2022, 6:25:04 PM2/10/22
to openthread-users
Hey Valeriy,

I think you are referring to the size of the ELF files, not the size of the executable that will be placed in the flash of the device. The ELF file, sometimes called an *.out file, contains more information than the assembly code that is loaded into flash. It also includes the debug information of the executable for a development environment like CCS or OpenOCD.

I just built the code on one of my VMs and notice the difference between the file's size and what the arm toolchain lists as it's text (assembly instructions):

```
vagrant@ubuntu-focal:~/ot-cc13x2-cc26x2/build/bin$ ls -la
total 1728
drwxrwxr-x 2 vagrant vagrant   4096 Feb 10 22:03 .
drwxrwxr-x 8 vagrant vagrant   4096 Feb 10 22:03 ..
-rwxrwxr-x 1 vagrant vagrant 610876 Feb 10 22:03 ot-cli-ftd
-rwxrwxr-x 1 vagrant vagrant 477672 Feb 10 22:03 ot-cli-mtd
-rwxrwxr-x 1 vagrant vagrant 204088 Feb 10 22:03 ot-cli-radio
-rwxrwxr-x 1 vagrant vagrant 539580 Feb 10 22:03 ot-ncp-ftd
-rwxrwxr-x 1 vagrant vagrant 478732 Feb 10 22:03 ot-ncp-mtd
-rwxrwxr-x 1 vagrant vagrant 225636 Feb 10 22:03 ot-rcp
vagrant@ubuntu-focal:~/ot-cc13x2-cc26x2/build/bin$ arm-none-eabi-size *
   text    data     bss     dec     hex filename
 201200     352   20748  222300   3645c ot-cli-ftd
 138708     352   16484  155544   25f98 ot-cli-mtd
  11027     320    2740   14087    3707 ot-cli-radio
 192176     352   21068  213596   3425c ot-ncp-ftd
 137960     352   16796  155108   25de4 ot-ncp-mtd
  24299     336    6892   31527    7b27 ot-rcp
vagrant@ubuntu-focal:~/ot-cc13x2-cc26x2/build/bin$
```
Reply all
Reply to author
Forward
0 new messages