-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backup running firmware (getting .ebl or .hex) #622
Comments
Not without connecting a SWD debugger (unless you can figure out how to execute code from RAM via EZSP commands!). The bootloader doesn't provide this functionality either. Is your EM3581 from a HUSBZB-1? I do have a full flash dump of an original HUSBZB-1 that can be converted into an EBL firmware with a bit of effort. There's little point in restoring it though unless you specifically want to run an ancient version of EmberZNet. |
This is for a cheap hub being sold as an orvibo rebrand thing. I have more info about it here: https://github.com/fakuivan/orvibo-gynoid-zigbee-hub-hack . I got so far as to strip the logic on the SOC and connecting it directly to HA via a serial to TCP relay. Say I have a SWD debugger, jtag or whatever. What would be the steps for dumping it? Also is I wasn't able to find any router firmware, all the ones out there are just for controller functionality, is there any chance you know where to get that? |
Dis you find some photos if the connected Zigbee chip so we can getting the pin / pads its using ? Dumping the chip (all flash consent also boot loader and saved settings) shall not being any problem can being done with one simple SWD probe and GDB that is free. |
I've added board pictures to the repo here the pins used for UART are PB1 and PB2, baud rate is 57600. If you want we can continue in fakuivan/orvibo-gynoid-zigbee-hub-hack#1 |
Is it possible to dump the running firmware into something that can be restored to later? I'm messing around with a EM3581 and it'd be cool to be able to make a backup before flashing something onto it.
The text was updated successfully, but these errors were encountered: