CC2538: How to update ZNP firmware from Raspberry pi

Dhanraj

Part Number: CC2538
Other Parts Discussed in Thread: Z-STACK,

Hello,

we are using cc2538-cc2592emk as znp (z-stack 3.0.2) over USB interface along with Raspberry Pi as a Host for zigbee gateway.

So now how can we update znp firmware from raspberry Pi? is it possible over existing USB interface or we need to make a provision of extra UART interface between znp and Raspberry pi?

over 5 years ago

0 Ryan Brown1 over 5 years ago

TI__Guru**** 217457 points

Hello Dhanraj,

The interface would be the same as for a BeagleBone Black or Linux host using the XDS100v3 backchannel UART communication USB port. There are several related posts on this matter, including your own:

https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/817001
https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/872605
https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/784392
https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/862301

You can reference the OTA upgrade section of the Z-Stack Linux Gateway User's Guide for further instructions.

Edit: Misunderstood that the SmartRF06EB is not used. Also not asking for OTA updates

Regards,
Ryan

0 Dhanraj over 5 years ago in reply to Ryan Brown1

Guru 14820 points

Hello Ryan,

I think there is some miscommunication, so let me clear that.

I have my zigbee gateway with CC2538-CC2592EMK as ZNP and connected to host i.e. Raspberry Pi over USB interface.That is working fine.

I want to update the firmware of znp module that is connected to raspberry pi over USB as a gateway which is running on-field.

There will be no physical access to the gateway and new firmware for znp has to be triggered and transferred from Raspberry pi host either from USB interface or from an extra UART interface.

0 Ryan Brown1 over 5 years ago in reply to Dhanraj

TI__Guru**** 217457 points

Ah, thank you for clarifying and apologies for the confusion. Yes, you will need additional UART connections for the backdoor bootloader connected to the PA0/PA1 pins along with a backdoor bootloader enable pin set by the CCFG. Please refer to SWRA466 for more information: http://www.ti.com/lit/swra466

Regards,
Ryan

0 Dhanraj over 5 years ago in reply to Ryan Brown1

Guru 14820 points

This application report covers UART and is intended to be used with associated example file, which can be downloaded from the following URL: www.ti.com/.../swra466. The example is created in Visual Studio® Professional 2015 and utilizes a library called Serial Bootloader Library to demonstrate an implementation of the serial bootloader protocol on Windows®.

This implementation is for windows, how can we do it from linux??

0 Ryan Brown1 over 5 years ago in reply to Dhanraj

TI__Guru**** 217457 points

You are referring to an example application but all communication protocol sequences have been provided. You will have to port the example or create a custom application for your needs. https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/648595

I had forgotten about the cc-rom-sbl tool that is now included with the Z-Stack Linux Gateway: https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/701092

Building this on Linux requires running make in the root directory. Here is the usage information:

Usage: ./cc-rom-sbl [SERIEL DEVICE] [FILE] [DEVICE TYPE] [OPTION]...

-e Erase with optional [START ADDRESS]

-p Program [FILE] with optional [START ADDRESS]

-v Verify [FILE] with optional [START ADDRESS]

--start=[START ADDRESS] Start address for Flash erase, program load and verify

Example:./cc-rom-sbl /dev/ttyUSB1 ZNP.hex cc2538 -e -p -v

Currently, only .hex files are supported. If the CC2538 is erased, it will automatically boot into the ROM Bootloader and can be tested with this app. In order to access the ROM Bootloader while there is an image on the device, you must access the ROM Bootloader Backdoor. In Z-Stack, search for ".cca" in startup_ewarm.c and modify the parameter which is set to BOOTLOADER_BACKDOOR_DISABLE by default.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

CC2538: How to update ZNP firmware from Raspberry pi