[DOCUMENTATION] Links to how-to upgrade firmware on Bitron Video AV2010/10 and SMaBiT AV2010/10 USB-sticks? #348
Comments
|
The official manuals page is https://manuals.smabit.eu/av2010_281.html but there is nothing written about updates. The stick is sold by german Telekom for their "magenta smarthome" system. |
|
@martin3000 as I understand it, if it comes with a standard Ember bootloader then it should be possible for anyone with access to the EmberZNet PRO SDK to create an EmberZNet NCP application firmware for it which then can be upgraded/flashed via XMODEM. @walthowd has for example posted great instructions on upgrading HUSBZB-1 firmware on its EM3581 (EM358x series) chip: https://github.com/walthowd/husbzb-firmware There are similar instructions for upgrading Telegesis ETRX357USB firmware with X-MODEM: https://community.home-assistant.io/t/eu-usb-sticks-for-the-new-zigbee-component/16718/10 The main problem with that is that there needs to be a personal interest to first create such firmware for your specific device as you really need to own one and open it up in order to figure out the GPIO pin layout (pins design, e.g. TX and RX port) that the chip uses before compiling the firmware so that the EmberZNet NCP application will communicate using the correct TXD and RXD ports. Also, to create and compile firm you need access to the EmberZNet PRO SDK through the Simplicity Studio software from Silicon Labs you need to have bought and registered an EFR32 Development Kit, like for example the EFR32xG22 Wireless Gecko Starter Kit: This is basically the process what has been done for some other Silicon Labs devices, like; HUSBZB-1, Telegesis ETRX357USB, and Sonoff ZBBridge, which all have EmberZNet NCP application EZSP firmware available for them release by independent developers. Think that this is mainly of interest for people wanting to replace their Telekom or QIVICON controller with Home Assistant ZHA. As such many people in Germany and the United Kingdom might already own such USB adapter that they wish to reuse. Otherwise, could be attractive adapter because of the very low price (~$10/~€10) that it can sometimes be found at in Europe. https://www.amazon.de/-/en/Wireless-Qivicon-Openhab-AV2010-10/dp/B07T6ZKSMF/ https://www.amazon.co.uk/Bitronvideo-ZigBee-Wireless-QIVICON-Home/dp/B07T6ZKSMF/ |
|
I don't speak german but it looks like at least some AV2010/10 ship with "Firmware 5.8.1" which could refer to old EmberZNet 5.8.1 If that is the case then that in indeed shipped with very old firmware (similar to HUSBZB-1 which some even ship with old 5.7 FW). |
Do you happen to know the inside of these contain the same chip and firmware as Qivicon Funkstick for Magenta Smart Home? https://www.conrad.com/p/99922197-magenta-smarthome-usb-memory-stick-1384483 https://www.amazon.de/-/en/Telekom-Smart-Home-ZigBee-Stick/dp/B015TCBZIE/ https://www.amazon.co.uk/Bitronvideo-99920750-Telekom-QIVICON-Zigbee/dp/B00JVMP2YM/ Some people from OpenHAB and FHEM have commented that Bitron Video AV2010/10 works when a Qivicon Funkstick did not. https://community.openhab.org/t/zigbee-dongle-compatible/10249/20 https://forum.fhem.de/index.php?topic=35743.0 Their outside shell/enclosure looks different but many OpenHAB comments mention both those as "Funkstick" for "Qivicon". Could, of course, be that they have the same chip but similar to Telegesis ETRX357USB it will not work unless flash a other FW. Oh, someone did open up a Qivicon Zigbee Funkstick branded dongle and looks to be same hardware as Telegesis ETRX357 |
|
EM3587 zigbee chip and CP2104 USB to uart.
|
|
If someone builds a firmware, I'll buy a second stick and try it out. |
|
Have you tried to connect to the Bootloader via XMODEM? That is probably a prerequisite before even building a firmware for it. |
|
Using minicom, I do not find the correct baud rate. I only get strange characters. |
|
Maybe start by testing the docker image that @walthowd provides an environment to see if can connect to check firmware info. https://github.com/walthowd/husbzb-firmware You do not need to try to flash the adapter (as the firmware image that he provides is probably not right for chip in you adapter). https://github.com/zigpy/bellows/blob/dev/README.md
From your pictures it looks like it has a CP2104 USB to Serial / UART chip from Silicon Labs so make sure have drivers for it https://www.silabs.com/products/development-tools/software/usb-to-uart-bridge-vcp-drivers Maybe try software that supports software "flow control" (try with and without) and also try both rate of 57600 and 115200 bps.
If can probably trigger Recover / Bootload mode (Bootloader) by resetting the stick and shorting a specific pin to GND https://github.com/walthowd/husbzb-firmware Worse case you need to connect something like a JTAG debug adapter like a SEGGER J-Link to manually trigger Bootload on a GPIO https://www.silabs.com/documents/public/application-notes/an706-ezsp-uart-host-interfacing-guide.pdf |
|
Telegesis ETRX357 procedure for reference (with unknown firmware image): https://community.home-assistant.io/t/eu-usb-sticks-for-the-new-zigbee-component/16718/10
|
|
stty -F /dev/ttyUSB0 tells me it is 57600 with xon/xoff, but connecting via minicom, I do not get an answer from AT command. After some modification to the tool, python3 Elelabs_EzspFwUtility.py probe -p /dev/ttyUSB1 -b 57600 returns firmware 5.8.1, EZSP v4 |
|
That probably means that they hardcoded the EmberZNet NCP application firmware to the baud rate of 57600 bps in that image. Note that the bootloader might still have different baud rate if it comes to having to force reset bootload for firmware recovery. So, in summary, sounds like it has basically same hardware chips on the board as Telegesis ETRX357USB but different firmware? If want to risk it then you could now go ahead and try flashing the same firmware image as they use for Telegesis ETRX357USB, but as you mentioned that would likely mean that you would have to first buy another adapter to experiment on and lab with. If you can flash that same firmware image as Telegesis ETRX357USB then could request a new image for it and this AV2010/10. |
Hedda
changed the title
|
Elelabs_EzspFwUtility.py works a little bit, but with minicom I do not get the "OK" answer. So how to do the firmware update? Maybe I could try it with the elelabs tool. |
Yes you can try flashing with Elelabs tool as long as are aware that successfully flashing the wrong firmware might corrupt EmberZNet NCP application so that you then have to manually reset it to force it into bootload recovery mode to load the Bootloader. https://github.com/Elelabs/elelabs-zigbee-ezsp-utility The firmware images that they provide is however not for EM357x series so need to try some other firmware image (even tough both Elelabs Zigbee USB Adapter EZBUSBA & Elelabs Zigbee Raspberry Pi Shield EZBPIS has EM357 Silicon Labs MCU inside). You could try them but assume that their firmware has been compiled to use the layout of the pins that they specifically use. If you are willing to risk it then could first that same firmware image as the community use for Telegesis ETRX3USB-LRS: https://community.home-assistant.io/t/eu-usb-sticks-for-the-new-zigbee-component/16718/10 em357-ncp-uart-xon-xoff-use-with-serial-uart-bl-500.ebl image file from: As mentioned, before you might have to change the baud rate in the serial port communication to 115200 baud for Bootloader. If that is successful then you can try asking the community if someone is willing to make a newer such image for EM357 using a later EmberZNet PRO stack that then is used by both these AV2010/10 USB-sticks and other Telegesis ETRX357USB products. Even if you do flash the wrong EmberZNet NCP application firmware image then that should still be recoverable as the Bootloader firmware is separate and if you load/start that then you can try flashing an other EmberZNet NCP application firmware image, though if the EmberZNet NCP application firmware image has been corrupted then you need to force it into bootload recovery mode to make it reset and load/start the Bootloader (to do that you usually need to short-circuit a specific pad on the board with a gnd/ground-pad on the same board). The normal worst-case scenario is probably if you manage to corrupt the Bootloader firmware too and in that case, you might need to connect something like a JTAG debug adapter like a SEGGER J-Link to flash a new Bootloader to recover it back to that. You should, of course, be warned that it is possible to fully brick adapters like these but it is unusual as they are designed to be recoverable with the right hardware, software tools, and expertise. |
|
You could also try docker environment + instructions by @walthowd meant for HUSBZB-1 (Silicon Labs EM3581 / EM358 / EM358x): https://github.com/walthowd/husbzb-firmware https://github.com/walthowd/husbzb-firmware/blob/master/README.md Those instructions are also for flashing a .ebl image but can not assume that the specific firmware image that he provides for the HUSBZB-1 is compatible as the application in that firmware has been compiled to use the layout of the pins that HUSBZB-1 uses.
@walthowd also has process for HUSBZB-1 firmware recovery which will probably be similar on AV2010/10 and Telegesis ETRX357. HUSBZB-1 Firmware RecoveryIn the event of a bad flash or unexpected event, the bootloader for the EM3581 on the HUSBZB-1 can be accessed by resetting the stick and shorting TP17 to GND with a a serial connection (115200 8/N/1 no hw or sw flow control). On device startup, unshort TP17 and send a carriage return over the serial connection. You should be returned to the bootloader menu where a image can be uploaded via XMODEM.
|
|
You can try with that "ncp-uart-sw-6.6.5.ebl" firmware file for husbzb-1 (EM3581) and hope that the pin layout matches AV2010/10 https://github.com/walthowd/husbzb-firmware/blob/master/ncp-uart-sw-6.6.5.ebl |
|
The page https://www.texim-europe.com/getfile.aspx?id=101076 says:
Maybe this means that the AT interface is not available on the EM3587. |
The interface is provided by the firmware, so if it is not in the firmware then no, if it is in the firmware then yes. So likely the firmware on AV2010/10 does not have AT interface but then it should have some other interface. "Custom application firmware can be developed on the ETRX3587 module using the latest Ember development firmware". That sentence implies that they probably use the standard EmberZNet NCP application firmware with EZSP interface. |
|
I asked Smabit (Bitron Video) about firmware updates. They told me that updates are done automatically if you are using the stick together with the Magenta system. This means that there must be a server hosting the firmware, and that there are sticks with the up-to-date firmware. |
|
@martin3000 OK, but just because they say that they release firmware updates does not mean that Smabit (Bitron Video) as the manufacturer releases major upgrades to much newer firmware. It might only mean that they release updates to an older version. It is common for manufacturers to stick with older firmware versions for historical reasons or they have no monetary gain in upgrading. As you noted the firmware shipped with your own EM3587 / ETRX3587 adapter was EmberZNet 5.8.1 which is really old today. Smabit (Bitron Video) as the manufacturer should if they wanted to be able to upgrade it to the latest EmberZNet 6.5.x.x and stay backwards compatible with EZSP v4 protocol plus with that version make it also be compatible with EZSP v5, EZSP v6, and EZSP v7. EM3587 chip inside it does even support EmberZNet SDK 6.6.x.x but Smabit (Bitron Video) as the manufacturer might be more reluctant to upgrade to that EmberZNet version as it removes EZSP v4 backwards compatibility which would mean that it would also require all supported applications like Magenta SmartHome Telekom to also add support for EZSP v5, EZSP v6, or EZSP v7. Again, independent developers who owns an EFR32 Development Kit, like for example the EFR32xG22 Wireless Gecko Starter Kit, as as such has registered access to EmberZNet PRO SDK in Silicon Labs Simplicity Studio could also build EmberZNet 6.5.x.x and/or EmberZNet SDK 6.6.x.x firmware for EM3587 but they would need to know specific pins layout AV2010/10 USB-sticks. https://github.com/zigpy/bellows/blob/dev/README.md EmberZNet and EZSP Protocol VersionSilicon Labs do not currently have a consolidated list of changes by EmberZNet SDK or EZSP protocol version. The EZSP additions, changes and deletions have only ever been listed in the "Zigbee EmberZNet Release Notes" (EmberZNet SDK) under the "New items" section as well as the matching UG100 EZSP Reference Guide included with each EmberZNet SDK release. The largest change was between EZSP v4 (first added in EmberZNet 4.7.2 SDK) and EZSP v5 that was added in EmberZNet 5.9.0 SDK which requires the Legacy Frame ID 0xFF. The change from EZSP v5 to EZSP v6 was done in EmberZNet 6.0.0 SDK. The change from EZSP v6 to EZSP v7 was in EmberZNet 6.4.0 SDK. EmberZNet 6.7.0 SDK added EZSP v8 (and Secure EZSP Protocol Version 2). Perhaps more important to know today is that EZSP v5, v6 and v7 (EmberZNet 6.6.x.x) use the same framing format, but EmberZNet 6.7.x.x/EZSP v8 introduced new framing format and expanded command id field from 8 bits to 16 bits. |
|
I have a new stick for experiments. |
|
Suggest maybe post in #243 and nicely there for someone to compile a new EmberZNet NCP application firmware image file that is made your specific EM3587 chip (exact model of that chip) for the flash size, noting TX/TXD and RX/RXD paths are needed then. Other options when compiling firmware are Hardware Flow Control or Software Flow Control or none, Baud Rate, and flash size. Best would be if you would first read the specification of the CP2104 USB to UART chip so know which pins are TX/TXD and RX/RXD on the serial/UART side, and then trace those on the circuit board to figure which pins on the EM3587 chip are used for TX/TXD and which is RX/RXD. Then you can read specification EM3587 chip to know which paths the firmware needs to be compiled for. Developer compiling the firmware would for example TX and RC plus probably the size of the flash memory on the specific chip : NCP UART TX --> PA0 But for you to know that you would have to trace the paths on the circuit board to figure what is connected to CP2104 chip: Example (again this is just an example which might not be true for your AV2010/10 adapter, which is why need to trace path): CP210x USB to UART chip "RX/RXD" --> "PA0" on EM35x Zigbee SoC --> NCP UART "TX" interface compiled in the firmware. It just as well is other PA/PB's for RX and TX, some EFR32 adapters for example uses PB14 and PB15 for NCP TX and RX ports: CP210x USB to UART chip "RX/RXD" --> "PB14" on EM35x Zigbee SoC --> NCP UART "TX" compiled in the firmware. An alternative option is to chance and build several different firmware using common paths and test just try them one by one. Did you also try flashing the much older random blob FW that works with ETRX357USB-LRS and ETRX357USB-LRS+8M or? https://community.home-assistant.io/t/eu-usb-sticks-for-the-new-zigbee-component/16718/10 |
|
@martin3000 maybe talk to @walthowd and @macfly92 as they figured out a way to flash Telegesis ETRX357 adapters in #347 |
|
I have the flash tool and it should work with the right firmware file. |
|
I own an AV2010/10 mysel, too. |
What is an OVP? |
|
Sorry! That is a german abbreviation. |
|
Did you guys manage to flash your Bitron Video / SMaBiT / Telekom Magenta USB-sticks based on Silicon Labs EM358x hardware? FYI, there is a lot of recent discussion in the last week about EM35x firmware updates in walthowd/husbzb-firmware#12 @grobasoz has uploaded new firmware images for both EM357 and EM358x in his repository here: https://github.com/grobasoz/zigbee-firmware https://github.com/grobasoz/zigbee-firmware/tree/master/EM358x https://github.com/grobasoz/zigbee-firmware/tree/master/EM357 Try it at your own risk as this could brick the stick, though that might be a good thing as would be excuse to buy a new dongle ;) PS: If you do manage to flash it then please update the documentation for any firmware tool and/or guide that you use |
|
AFAIK Bitron accepted standard builds which came with older emberznet versions, this means this firmware is not going to work. At least it doesn't work with HUSBZB-1 |
|
@Adminiuga Have you trying to load the 6.7.8.0 for EM3581 / HUSBZB-1 and its not working ? One user have loading the EM357 on Telegesis ETRX357USB and its loaded OK and looks working OK. I think the EM358X its little more tricky then its one combo device. |
|
Its looks like the firmware cooker (Gary) have solving the problem with HUSBZB-1 and have getting EZSP 6.7.8.0 up and running on HUSBZB-1. One thing with 6.7.X.X its using only the new protocol version 8 and is not backwards compatible with older protocols pre V8. If its possible flashing one earlier 6.6.X.X EZSP it should being pretty secure trying the 6.7.8.0 and is its not working only flashing back the working 6.6.X.X. |
|
I not understand, it's possible upgrade the firmware on Bitron Video AV2010/10? on this repository "https://github.com/grobasoz/zigbee-firmware/tree/master/EM358x" result deprecated... |
|
Siirlabs have flagged EM35X and EFR32 devices with 256 kb flash as deprecated and also most code for EM35X devices is deleted in the EZSP 6.9.2.x release. But our master cooker have doing one working ESZP 6.7.8.0 for EF35X devices and also one for EM3581. Some is saying the EM3581 shall working on EM3587 but no user have successful trying flashing it with our EM3581 firmware. One reason is we dont have any firmware to going back if it is flashed and not working (no have dumping the original firmware or getting one working upgrade file). Feel free trying it but no one is leaving and grantee and you can braking your device if you not have (if its possible) dumped the original firmware before you is doing it and can re flashing it with J-Tag / SWD debugger. |
|
EZSP 6.7.X is not having any precompiled NCP for EM3587 only for EM3588 but i have "finding" 6.5.0.0 and 6.6.0.0 and attaching the latest HW and SW versions in EBL and S37 format if some have use of them then flashing there device as security for going back to one working version (if Bitron is using the default settings). |
|
Ok thansks for a lot information! |
|
If its the Itead / Sonoff USB Zigbee 3 dongle I can not recommend then its having large problems with the hardware and is barely working at all (the same problem with ZBB but worth). Look in HA continuity forums and also Zigpy and bellows issues for getting info on Sonoff FER32 coordinators. They is also releasing one EFR32 with Ethernet that looks OK on the Ethernet side (ESP32) but is using the same bad Zigbee module (SM-011) that making all one NO GO!! zigpy/zigpy#635 (comment) |
|
I would recommend cc2652r or cc2652rb or cc2652p |
|
|
Looks like Gary have cooked one working EZSP 6.7.8.0 by mistake that is working with AV2010/10 USB-Stick grobasoz/zigbee-firmware#15. I have not testing but 2 user have flagged its working. |
Nice! Also see new comment in grobasoz/zigbee-firmware#15 that a user now managed to flash with walthowd docker image too. Note that this requires defining a baud rate of 115200 instead of 57600 which I believe is the baud rate on the default firmware. |
|
something offtopic: are there modules which allow the creation of DIY zigbee sensors? |
@martin3000 Better post such off-topic topics as new discussions here instead -> https://github.com/zigpy/zigpy/discussions But here short summary as answer; Yes there are. Texas Instruments CC2530 based radio modules from Ebyte and RF-star was previously most popular for DIY project until recently when more hobbyist started moving over to their newer modules based on CC2652 series (CC2650R or CC2652P). Examples modules are RF-BM-2652P1 and RF-BM-2652P2 modules from RF-Star, and E72-2G4M20S1E module from Ebyte. What drives most those projects Zigbee Configurable Firmware tool by PTVO -> https://ptvo.info as it allows just about anyone to build firmware for Texas Instruments based radio modules -> https://ptvo.info/zigbee-configurable-firmware-features/ and that recently also added support for CC2652 and CC1352: https://ptvo.info/zigbee-switch-configurable-firmware-v2-210/ https://ptvo.info/cc2652r1-cc2652rb-cc2652p-cc1352p2-configurable-router-firmware-748/ I think the most active community around such DIY Zigbee products is "DIYRuZ" at https://github.com/diyruz/ which I believe post most on https://modkam.ru/ and they have several open source projects posted for different Zigbee sensors. Checkout examples: https://www.zigbee2mqtt.io/supported-devices/#v=DIYRuZ Also checkout some cool Zigbee sensors from smartboxchannel -> https://github.com/smartboxchannel?tab=repositories |
FYI, EmberZNet 6.7.10 for EM3587 has now also been made available by grobasoz https://github.com/grobasoz/zigbee-firmware/blob/master/EM3587/NCP_USW_EM3587_6710-LR.ebl EmberZNet 6.7.10 has been confirmed working by Elix-g in a discussion about flashing here: Again, this requires defining a baud rate of 115200 instead of 57600 which I believe is the baud rate on the default firmware. |
Does anyone have links to info on how-to upgrade firmware on SMaBiT AV2010/10 and Bitron Video (BV) AV2010/10 USB stick?
Would be good to add links to step-by-step in bellows README.md file https://github.com/zigpy/bellows/blob/master/README.md
Plus links to publicly available firmware images with newer EmberZNet NCP application FW image files for them?
From the info that I could find these are based on Ember EM3587 (EM358x series) chip + has a CP2104 USB-to-Serial/UART chip? This AV2010/10 USB-stick is effectively an RS232 to USB bridge connected to a SiLabs ETRX3 Series ZigBee module.
https://silabs-prod.adobecqms.net/support/resources.p-wireless_zigbee-and-thread_em358x-wireless-zigbee-socs
https://www.silabs.com/documents/public/reference-manuals/TG-PM-0509-ETRX358x.pdf
https://www.texim-europe.com/getfile.aspx?id=101076
That probably means users preferably want later version of EmberZNet 6.6 / 6.6.x / 6.6.x.x if possible for EZSP v5/v6/v7 support?
https://bv.smabit.eu/index.php/smart-home-produkte/zb-funkstick/
"The ZigBee USB radio device can be used to use ZigBee devices that run QIVICON Home Base 1 and Telekom Speedport Smart. The product is not compatible with QIVICON Home Base 2. You can still use the wireless Stick with another OpenHAB-based system."
@martin3000 added the Bitron Video Zigbee Stick to Home Assistant ZHA list https://www.home-assistant.io/integrations/zha/
@walthowd has for example posted great instructions on upgrading HUSBZB-1 https://github.com/walthowd/husbzb-firmware
PS: Submitted a PR to update bellows README.md with a general recommendation to upgrade EmberZNet firmware in #346
PPS: I am only asking this on behalf of the community as I do not actually own any Bitron Video/Smabit USB dongles myself.
The text was updated successfully, but these errors were encountered: