This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Light_bulb example for 52840 Dongle

Please guide what changes are to be done for the Light bulb example to be run in 52840 Dongle?

I am using VS Code and built the Build Configuration using the Dongle configuration that was available.  Since the compilation gave this error, I updated the PWM Driver to the one mentioned in the DTS file. 

/* Use onboard led4 to act as a light bulb.
 * The app.overlay file has this at node label "pwm_led3" in /pwmleds.
 */
#define PWM_DK_LED4_NODE                DT_NODELABEL(blue_pwm_led)

It build fine and generates the .hex file.  However, after loading the hex file in the Dongle using the Programmer V2.0.0 the DFU loading is fine but upon completion it gives the below

12:29:13.049
Uploading image through SDFU: 99%
12:29:13.271
Uploading image through SDFU: 100%
12:29:13.421
All dfu images have been written to the target device
12:29:16.444
Failed to write: Timeout while waiting for device EF30A289B89F to be attached and enumerated

The dongle is not corrupted as I again again reset the same and reinstall. I have also loaded my earlier dongle firmware and it runs fine.  So the Dongle is fine.  Just need to check why is the above error after successful write?

Parents
  • Hi

    Can you show me a picture of how the Dongle is connected to your DK? Does it no longer work at all when you power it again? What might have happened is that the UICR has been erased for some reason, and you need to do as Einar explains in the Dongle Programming tutorial

    After the other Dongle has been flashed successfully and reset, does the LED blink as it should when transmitting data to the Zigbee2MQTT device? How do you determine that it doesn't send data anymore?

    Best regards,

    Simon

  • After the other Dongle has been flashed successfully and reset, does the LED blink as it should when transmitting data to the Zigbee2MQTT device? How do you determine that it doesn't send data anymore?

    There is no LED blinking.  Also I verified through the sniffer.  It is strange that I have 3 dongle, all sent a device announcement to zigbee2mqtt the first time it was flashed and by making small tweak like change of just a manf name and flashing it back does not send the message. Yes, I also re-flashed the same hex that was working earlier and it still does not annouce to zigbee 2mqtt.

    Is there a "blank" zigbee code available for the dongle, which does nothing but just send a general attributes to check whats wrong?

Reply
  • After the other Dongle has been flashed successfully and reset, does the LED blink as it should when transmitting data to the Zigbee2MQTT device? How do you determine that it doesn't send data anymore?

    There is no LED blinking.  Also I verified through the sniffer.  It is strange that I have 3 dongle, all sent a device announcement to zigbee2mqtt the first time it was flashed and by making small tweak like change of just a manf name and flashing it back does not send the message. Yes, I also re-flashed the same hex that was working earlier and it still does not annouce to zigbee 2mqtt.

    Is there a "blank" zigbee code available for the dongle, which does nothing but just send a general attributes to check whats wrong?

Children
No Data
Related