Part Number: CC2530
The customer is experiencing below issue and needs your help.
1. Customer burned the boot on the CC2530 (path: C:\Texas Instruments\ZStack-CC2530-2.5.1a\Projects\zstack\Utilities\BootLoad\CC2530). He fully configured according to the Serial Boot Loader For CC253x SoC document. He burned the app with sbdemo. After the burning is finished, the traffic light is always on. But after the restart, the red light keeps flashing. Customer checked the boot code and it seemed to always return false in the sbImgValid function. He looked at the values of 0090~0091 and 0092~0093 in GenericApp.bin are the same (see the figure below). He would like to know why?
2. Customer doesn't want to use the button to jump, he wants to jump to the app after power-on. Is it OK to change the value of SB_UART_DELAY?
Are they evaluating with a SmartRF05EB? Based on the described behavior, it appears that the SBL is preserved but the CRC fails. The customer must make sure to follow Section 10.5.2 of the SBL document and review all of Section 10-12 to ensure completion of all steps. Yes, it is fine to change the SB_UART_DELAY.
To better aid the community, please click on the "This Resolved my issue" button whenever a post answers your question!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Ryan Brown1:
He used the SmartRF04EB+cc2530 mode to debug. Use SmartRF04EB to burn the boot first, then use SBLdemo.exe to burn the protocol stack GenericApp.bin (234kB). The IAR configuration is also configured exactly as described in Sections 10-12 of the documentation.
There is a problem with the values of CRC and CRC in the sbImgValid function. 0x90-0x93 in GenericApp.bin is consistent, but returns false when detecting CRC.
In reply to Annie Liu:
Advise that the customer use a SmartRF05EB instead. So are they not copying the CRC into the CRC Shadow which has been added to the build as described in 10.3 and 10.5.2? If this section of code is entered then the CRCis being read as 0x0000 or 0xFFFF.
1. The customer has changed the CRC according to the document. The values in the 0x90-0x91 and 0x92-0x93 positions in his GenericApp.bin file are the same.
2. Currently, customers only have SmartRF04EB. It used to burn the version. he wants to know why they want to use SmartRF05EB? What is the difference between them? What will be wrong with SmartRF04EB?
In short the SMARTRF04EB does not support the CC2530 device:
Which could explain the customer's Boot Load issues.
1. Customer used the development board he bought and he used to write with SmartRF04EB. He posted the picture of SmartRF04EB. Would you help to review is there any problem with this?
2. He uses the SmartRF04EB to burn uboot and then burns the app with SBdemo. Is it OK?Soc end and cc2530 are connected by serial port. If it is OK, he wants to use the code on the soc to upgrade the cc2530 through the serial port.
This is quite different from the SMARTRF04EB board developed by TI, which clears up my device incompatibility confusion: https://www.ti.com/lit/swra105
So what CC2530 board are they using? Have the customer combine the boot and application codes into a single image to be loaded by FLASH-PROGRAMMER. This will help determine if the issue regards the deprecated SBDemo PC Tool. Also keep in mind that IAR EW8051 v8.10.4 should be used to build the projects.
The board he uses is the development board that he buys online (see the picture below). He is currently debugging on the development board. After that, the project is soc(arm linux)+2530 module. Soc and 2530 are connected through serial port. The function he wants to achieve now is to develop the code on the soc side, and then he can upgrade the program to 2530 through the serial port. So he wants to try it through the SBdemo tool firstly. If it is OK, then he will develop the code on the soc side.
I have no experience witht he SBdemo tool, I have however verified Boot Load project operation with a SmartRF05EB + CC2530EM and Z-Stack 3.0.2 although I know this is of little help given the customer's setup. Please have the customer verify the version of OS and IAR that they are using. By testing the unified image they can verify whether the issue is with the boot program, application image, or software tool.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.