StackVersion: 6.4.1

I'm testing an OTA upgrade.My device recognizes the new image and is ready to upgrade.But an error occurred while receiving the  data, and the system crashed, and the network went offline after the restart. Follow is my issue log . I need some help .  thanks!!

>>>>>>>>> S001 Main Start <<<<<<<<<<
EEPROM init: 0x00
sched report event for: 0x00000000
EMBER_NETWORK_UP 0xBDB3
Bootload state: Random Delay before start
Delaying 174 seconds before starting OTA client
>>>>>>>>> Stack Status:90 <<<<<<<<<<
>> emberNetworkState:2
>>>>>>>>> S001 Init Start <<<<<<<<<<
>>>>>>>>> Network State:0 state:2 <<<<<<<<<<
sched report event for: 0x00360038
sched report event for: 0x00360038
sched report event for: 0x00360038
sched report event for: 0x00360035
Processing message: len=5 profile=0104 cluster=0006

T00000003:RX len 5, ep 01, clus 0x0006 (On/off) FC 00 seq 00 cmd 0B payload[0A 00 ]
Processing message: len=5 profile=0104 cluster=0006

T00000003:RX len 5, ep 03, clus 0x0006 (On/off) FC 00 seq 02 cmd 0B payload[0A 00 ]
Processing message: len=5 profile=0104 cluster=0006

T00000003:RX len 5, ep 04, clus 0x0006 (On/off) FC 00 seq 03 cmd 0B payload[0A 00 ]
YQSwitch_K4>YQSwitch_K4>MFG String: 
AppBuilder MFG Code: 0x2333
node [(>)99B457FFFE98FBE7] chan [11] pwr [20]
panID [0xA357] nodeID [0xBDB3] xpan [0x(>)1E3E1FBB69B1ECC7]
parentID [0x0000] parentRssi [-31]
stack ver. [6.4.1 GA build 408]
nodeType [0x02]
Security level [05]
network state [02] Buffs: 75 / 75
Ep cnt: 4
ep 1 [endpoint enabled, device enabled] nwk [0] profile [0x0104] devId [0x0100] ver [0x00]
    in (server) cluster: 0x0000 (Basic)
    in (server) cluster: 0x0003 (Identify)
    in (server) cluster: 0x0004 (Groups)
    in (server) cluster: 0x0005 (Scenes)
    in (server) cluster: 0x0006 (On/off)
    out(client) cluster: 0x0019 (Over the Air Bootloading)
ep 2 [endpoint enabled, device enabled] nwk [0] profile [0x0104] devId [0x0100] ver [0x00]
    in (server) cluster: 0x0000 (Basic)
    in (server) cluster: 0x0003 (Identify)
    in (server) cluster: 0x0004 (Groups)
    in (server) cluster: 0x0005 (Scenes)
    in (server) cluster: 0x0006 (On/off)
    out(client) cluster: 0x0019 (Over the Air Bootloading)
ep 3 [endpoint enabled, device enabled] nwk [0] profile [0x0104] devId [0x0100] ver [0x00]
    in (server) cluster: 0x0000 (Basic)
    in (server) cluster: 0x0003 (Identify)
    in (server) cluster: 0x0004 (Groups)
    in (server) cluster: 0x0005 (Scenes)
    in (server) cluster: 0x0006 (On/off)
    out(client) cluster: 0x0019 (Over the Air Bootloading)
ep 4 [endpoint enabled, device enabled] nwk [0] profile [0x0104] devId [0x0100] ver [0x00]
    in (server) cluster: 0x0000 (Basic)
    in (server) cluster: 0x0003 (Identify)
    in (server) cluster: 0x0004 (Groups)
    in (server) cluster: 0x0005 (Scenes)
    in (server) cluster: 0x0006 (On/off)
    out(client) cluster: 0x0019 (Over the Air Bootloading)
Nwk cnt: 1
nwk 0 [Primary (pro)]
  nodeType [0x02]
  securityProfile [0x05]
YQSwitch_K4>starting OTA client state machine
Bootload state: Discovering OTA Server
YQSwitch_K4>Processing message: len=6 profile=0000 cluster=8006
Setting OTA Server to 0x0000
Bootload state: Get OTA Server EUI
OTA Cluster: setting IEEE address of OTA cluster
Last offset downloaded: 0x00000000
No image found in storage.
Processing message: len=16 profile=0104 cluster=0019

T0000005D:RX len 16, ep 01, clus 0x0019 (Over the Air Bootloading) FC 19 seq 04 cmd 02 payload[00 33 23 14 00 06 01 00 00 90 60 03 00 ]
Query next image response: New image is available for download.
Starting download, Version 0x00000106
Bootload state: Downloading Image
Starting erase from offset 0x00044000 to 0x0007F000
EEPROM Erase complete
EMBER_NETWORK_DOWN
>>>>>>>>> Stack Status:91 <<<<<<<<<<
>> emberNetworkState:3
>>>>>>>>> Network State:6 state:3 <<<<<<<<<<
EMBER_JOIN_FAILED
>>>>>>>>> Stack Status:94 <<<<<<<<<<
>> emberNetworkState:3
EMBER_NETWORK_UP 0xBDB3
>>>>>>>>> Stack Status:90 <<<<<<<<<<
>> emberNetworkState:2
>>>>>>>>> Network State:6 state:2 <<<<<<<<<<
Timeout waiting for message.
ERROR: tx 66, Profile: HA (0x0104), Cluster: 0x0019, 17 bytes, ZCL Cluster Cmd ID: 3

[ASSERT:packet-buffer.c:357]
Reset info: 0x07 (CRS)
Extended Reset info: 0x0701 (AST)
Handler mode using main stack (00000000 to 20001A60), SP = 00000000
0 bytes used (0%) in main stack (out of 6752 bytes total)
No interrupts active
Reset cause: Assert `:0
R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000
R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000
R8 = 00000000, R9 = 00000000, R10 = 00000000, R11 = 00000000
R12 = 00000000, R13(LR) = 00000000, MSP = 00000000, PSP = 00000000
PC = 00000000, xPSR = 00000000, MSP used = 00000000, PSP used = 00000000
CSTACK bottom = 00000000, ICSR = 00000000, SHCSR = 00000000, INT_ACTIVE0 = 00000000
INT_ACTIVE1 = 00000000, CFSR = 00000000, HFSR = 00000000, DFSR = 00000000
MMAR/BFAR = 00000000, AFSR = 00000000, Ret0 = 00000000, Ret1 = 00000000
Ret2 = 00000000, Ret3 = 00000000, Ret4 = 00000000, Ret5 = 00000000
Dat0 = 00000000, Dat1 = 00000000
init pass
>>>>>>>>> S001 Main Start <<<<<<<<<<
EEPROM init: 0x00
deactivate report event
>>>>>>>>> S001 Init Start <<<<<<<<<<
>>>>>>>>> Network State:0 state:0 <<<<<<<<<<
>>>>>>>>> Network State:1 state:0 <<<<<<<<<<
-- Network Steering Start --
NWK Steering State: Scan Primary Channels and use Install Code
Error: NWK Steering could not setup security: 0xB7
NWK Steering State: Scan Secondary Channels and use Install Code
Error: NWK Steering could not setup security: 0xB7
NWK Steering State: Scan Primary Channels and Use Centralized Key
Starting scan on channel 20
NWK Steering: Start: 0x00
Starting scan on channel 24
Starting scan on channel 25
Starting scan on channel 11
Starting scan on channel 14
Starting scan on channel 15
Starting scan on channel 19
NWK Steering State: Scan Secondary Channels and Use Centralized Key
Starting scan on channel 13
Starting scan on channel 14
Starting scan on channel 15
Starting scan on channel 16
Starting scan on channel 17
Starting scan on channel 18
Starting scan on channel 19
Starting scan on channel 20
Starting scan on channel 21
Starting scan on channel 22
Starting scan on channel 23
Starting scan on channel 24
Starting scan on channel 25
Starting scan on channel 26
Starting scan on channel 11
Starting scan on channel 12
NWK Steering State: Scan Primary Channels and Use Distributed Key
Starting scan on channel 19
Starting scan on channel 20
Starting scan on channel 24
Starting scan on channel 25
Starting scan on channel 11
Starting scan on channel 14
Starting scan on channel 15
NWK Steering State: Scan Secondary Channels and Use Distributed Key
Starting scan on channel 25
Starting scan on channel 26
Starting scan on channel 11
Starting scan on channel 12
Starting scan on channel 13
Starting scan on channel 14
Starting scan on channel 15
Starting scan on channel 16
Starting scan on channel 17
Starting scan on channel 18
Starting scan on channel 19
Starting scan on channel 20
Starting scan on channel 21
Starting scan on channel 22
Starting scan on channel 23
Starting scan on channel 24
NWK Steering Stop.  Cleaning up.
Network Steering Completed: FAILED (0x94)
Finishing state: 0x09
Beacons heard: 47
                 Join Attempts: 0
>>>>>>>>> Network State:5 state:0 <<<<<<<<<<
>>>>>>>>> Network State:5 state:0 <<<<<<<<<<
>>>>>>>>> Network State:5 state:0 <<<<<<<<<<

@hai Please also see the post below for more information.
https://www.silabs.com/community/wireless/zigbee-and-thread/forum.topic.html/cannot_send_a_muximumpayloadlengthmessange-b0sL

Bluetooth Low Energy (BLE) beacons have been a leading technology choice for proximity-aware applications in the market for several years. With its low power and simplicity, BLE has been adopted in a wide range of location-based services in smartphone apps and battery-powered beacons. When Bluetooth 5.0 was introduced, several major enhancements for BLE such as new PHY layers and Advertising Extensions have enabled second-generation beacons with fuller, richer content.  

Beacon Basics  

A beacon is a small, inexpensive wireless device, often battery-powered, that uses BLE to advertise its presence. Think of a RF version of a lighthouse, which repeatedly broadcasts an identifier that is recognized by other devices within its range. Beacons do not directly provide information about their exact physical location, instead relying on a receiving device to be aware it is near the beacon. Because of their proximity awareness features, beacons are commonly used in retail and commercial businesses where proximity awareness can improve customer shopping experiences in POS systems, loyalty apps, and inventory.  

Beaconing with Bluetooth 4.X 

BLE in version 4.x defines forty 2MHz wide channels in the 2.4-2.5 GHz ISM band. Three channels are reserved for advertising and the other 37 are data channels. Both advertising packets and data packets use the same format with a variable size payload and are only distinguished by the channel being used. Beacons based on Bluetooth 4.x are extremely power efficient as their payload size is restricted to a maximum 31-bytes of data. When more flexibility in payload and range is desired, the newly enhanced Bluetooth 5.0 beacon provides additional channel selections all while remaining compatible with the older BLE 4.x version.  

Bluetooth 5.0 Enhancements  

With Bluetooth 5.0, new enhancements to the Low Energy standard, radio, channel selection, power, and advertising extensions were added. All of the following elements are designed to maintain backward compatibility with the v4.0 standard:  

• Two New PHYs 

• 10X transmit power 

• Advertising Extensions:  

• Secondary Advertising Channels 

• Advertising Packet Chaining 

• Advertising Data Sets 

• Periodic Advertising 

• High Duty Cycle Advertising  

Advanced Beacons 

The wide-ranging enhancements implemented in Bluetooth 5 open innumerable possibilities for more advanced beacons. With larger advertising packets, more content can be provided in an advertising event. In addition, a single physical beacon can support multiple beacon standards, each with different packet timing and formatting. Existing apps based on Bluetooth 4.0 beacons can still be compatible with Bluetooth 5 beacons, allowing a smooth transition while upgrading to more enhanced capabilities.  

Benefits of Bluetooth 5.0 

Bluetooth 5.0 achieves 2x the speed, 4x the range, and 8x the broadcast capacity of previous versions. As a new and large market potential, the building blocks are now available to create advanced beacons using Bluetooth 5. To learn more about how Bluetooth 5 can enhance your second-generation beacons, read this whitepaper.  

Bluetooth Low Energy (BLE) beacons have been a leading technology choice for proximity-aware applications in the market for several years. With its low power and simplicity, BLE has been adopted in a wide range of location-based services in smartphone apps and battery-powered beacons. When Bluetooth 5.0 was introduced, several major enhancements for BLE such as new PHY layers and Advertising Extensions have enabled second-generation beacons with fuller, richer content.  

Beacon Basics  

A beacon is a small, inexpensive wireless device, often battery-powered, that uses BLE to advertise its presence. Think of a RF version of a lighthouse, which repeatedly broadcasts an identifier that is recognized by other devices within its range. Beacons do not directly provide information about their exact physical location, instead relying on a receiving device to be aware it is near the beacon. Because of their proximity awareness features, beacons are commonly used in retail and commercial businesses where proximity awareness can improve customer shopping experiences in POS systems, loyalty apps, and inventory.  

Beaconing with Bluetooth 4.X 

BLE in version 4.x defines forty 2MHz wide channels in the 2.4-2.5 GHz ISM band. Three channels are reserved for advertising and the other 37 are data channels. Both advertising packets and data packets use the same format with a variable size payload and are only distinguished by the channel being used. Beacons based on Bluetooth 4.x are extremely power efficient as their payload size is restricted to a maximum 31-bytes of data. When more flexibility in payload and range is desired, the newly enhanced Bluetooth 5.0 beacon provides additional channel selections all while remaining compatible with the older BLE 4.x version.  

Bluetooth 5.0 Enhancements  

With Bluetooth 5.0, new enhancements to the Low Energy standard, radio, channel selection, power, and advertising extensions were added. All of the following elements are designed to maintain backward compatibility with the v4.0 standard:  

• Two New PHYs 

• 10X transmit power 

• Advertising Extensions:  

• Secondary Advertising Channels 

• Advertising Packet Chaining 

• Advertising Data Sets 

• Periodic Advertising 

• High Duty Cycle Advertising  

Advanced Beacons 

The wide-ranging enhancements implemented in Bluetooth 5 open innumerable possibilities for more advanced beacons. With larger advertising packets, more content can be provided in an advertising event. In addition, a single physical beacon can support multiple beacon standards, each with different packet timing and formatting. Existing apps based on Bluetooth 4.0 beacons can still be compatible with Bluetooth 5 beacons, allowing a smooth transition while upgrading to more enhanced capabilities.  

Benefits of Bluetooth 5.0 

Bluetooth 5.0 achieves 2x the speed, 4x the range, and 8x the broadcast capacity of previous versions. As a new and large market potential, the building blocks are now available to create advanced beacons using Bluetooth 5. To learn more about how Bluetooth 5 can enhance your second-generation beacons, read this whitepaper.  

Hi,

you can get an overview about the available SoCs, including the CPU frequency values here:
https://www.silabs.com/wireless/bluetooth
But apart from the CPU frequency and BLE data rate, you will really fast run out of available RAM with the 20+MHz 8-bit data which you would like to read..

Thank you to everyone who participated in our Community EFM8 LCK contest! We enjoyed reading your answers to the different application possibilities you could build with the Busy Bee Starter Kit. Submissions were graded on a point basis and the correct answers are shown above.

Summarizing all this, we would like to congratulate the following winners for the EFM8 Busy Bee Contest: 

• Ravi R 
• Wojtek S
• Harri R
• Gordon M
• Philip S
• Alan S
• Eugene N
• Harsh K
• Leijo T
• Miroslaw S

Please join us in congratulating the winners! 

Each of the winners will receive a follow-up email with details on how to receive their prizes. Again, we thank all the participants who took part in the contest. It's great to know there are many cool EFM8 LCK-based projects out there, and we would love to see your final projects shared in the Community or through social media by tagging @siliconlabs. We hope you enjoyed this contest, and wish you a great holiday season! 

The Silicon Labs Team

Thank you to everyone who participated in our Community EFM8 LCK contest! We enjoyed reading your answers to the different application possibilities you could build with the Busy Bee Starter Kit. Submissions were graded on a point basis and the correct answers are shown above.

Summarizing all this, we would like to congratulate the following winners for the EFM8 Busy Bee Contest: 

• Ravi R 
• Wojtek S
• Harri R
• Gordon M
• Philip S
• Alan S
• Eugene N
• Harsh K
• Leijo T
• Miroslaw S

Please join us in congratulating the winners! 

Each of the winners will receive a follow-up email with details on how to receive their prizes. Again, we thank all the participants who took part in the contest. It's great to know there are many cool EFM8 LCK-based projects out there, and we would love to see your final projects shared in the Community or through social media by tagging @siliconlabs. We hope you enjoyed this contest, and wish you a great holiday season! 

The Silicon Labs Team

Thank you to everyone who participated in our Community EFM8 LCK contest! We enjoyed reading your answers to the different application possibilities you could build with the Busy Bee Starter Kit. Submissions were graded on a point basis and the correct answers are shown above.

Summarizing all this, we would like to congratulate the following winners for the EFM8 Busy Bee Contest: 

• Ravi R 
• Wojtek S
• Harri R
• Gordon M
• Philip S
• Alan S
• Eugene N
• Harsh K
• Leijo T
• Miroslaw S

Please join us in congratulating the winners! 

Each of the winners will receive a follow-up email with details on how to receive their prizes. Again, we thank all the participants who took part in the contest. It's great to know there are many cool EFM8 LCK-based projects out there, and we would love to see your final projects shared in the Community or through social media by tagging @siliconlabs. We hope you enjoyed this contest, and wish you a great holiday season! 

The Silicon Labs Team

We invite Silicon Labs Community members to participate in this exciting contest where you can win an EFM8 Busy Bee Starter Kit! The EFM8BB1 Low Cost Kit is an easier to use yet powerful development starting point. With full support in Simplicity Studio, code examples, and a free unlimited Keil license, you can get to prototyping your design quickly. The contest consists of 5 questions related to the EFM8 Busy Bee and 10 winners will receive a kit for free.  

Prize:  

Number of Winners: 10  

Prize: 1 x EFM8BB1LCK 

How to Participate:  

• Contest Period: Oct 18, 2019 - Nov 5, 2019 CDT  

• Answer the 5 questions below and send an email to anna.qi@silabs.com with your answers no later than Nov 5, 2019. You will receive a confirmation that you entered the contest.  

• Winners will be announced on Nov 18, 2019 CDT

  • We highly encourage winners to post a quick demo inside the Silicon Labs Community or personal social media channels on how they are using their new EFM8 Busy Bee Starter Kit!  

Judging:  

If there are more than 10 contestants who answer all the correct answers, we will decide the final 10 winners based on their open-ended question (Q5). Silicon Labs’ staff will evaluate the answers based on relevance and usefulness. The bonus point question is not required but will provide an extra point to your overall score.  

Contest Questions:  

Tip: Use the EFM9BB1LCK Kit Page and User Guide  

Q1 : What key features does the EFM8BB1 have?

1. On-board USB debugger
2. 512 bytes RAM
3. 20-pin expansion header
4. Both 1 and 3
5. All of the above

Q2: The ________________ software packages contains all the tools, drivers, software examples and documentation needed to use the EFM8BB1 Low Cost Kit.

1. VCP Drivers
2. Clockbuilder Pro
3. Simplicity Studio
4. Bluetooth SDK
5. Bluegiga Wi-Fi

Q3: What does the kit hardware layout not contain?

1. MCU Reset Button
2. Hall Effect Sensor
3. Programmable LED
4. Debugger C2 Interface Pins
5. 2.54 mm breakout pads

Q4: What expansion boards are compatible with the Busy Bee kit?

1. WGM110 Wi-Fi Expansion Kit
2. LTE-M Expansion Kit
3. ISOLATED-RS-EK
4. Both 1 and 3
5. All of the above

Q5: Give a specific example of an application that you can build with the Busy Bee and explain why. 

Bonus: We’re excited to hear how you will use your EFM8 Busy Bee Starter Kit! You will earn an extra bonus point if you post your answer to Q5 on Facebook or Twitter. Posts must be public - tag @siliconlabs and use #EFM8BusyBee to enter.   

By entering the contest you acknowledge that you have read and agree to the Community Contest Terms and Conditions. Please review them before entering the contest.