Hi, neighbors and friends...
As the expert control panel said I was using my Razberry v2 (blue) in version 3.27. I visited the firmware map and saw there was an update to 5.36 with this file: https://service.z-wave.me/expertui/uzb/ ... 000002.bin
So I uploaded the firmware via expert UI, after a minute or so, went back to the firmware update page again, and now my Razberry is dead, it cannot be detected by the z-way server anymore.
I tried to completely shutdown the system, disconnect form electricity, wait 5 minutes, connect again cycle for a couple of times, but didn't work.
I can't attach the z-way-server.log file, because "It's too big" error in the web (even .tgz), so I provide a link to it: Link to z-way-server.log
Password: z-way-server-log
I guess it's bricked out (Don't know why), so I just acquire a new one, but I'd like to know what happened, so it won't happen again!
Thanks in advance!
PS:
BTW, I am on z-way-server 3.0.1 and raspbian buster updated
Razberry v2 dead after firm upgrade
Re: Razberry v2 dead after firm upgrade
Today I did the same. Tried to upgrade my Razberry via expert UI from Version 5.27 to 5.36 using file UPD_FIRMWARE_Razberry_STATIC_2ch_ZME_05_1b_04000002_ZME_05_24_04000002.bin according to map:
https://service.z-wave.me/expertui/uzb/ ... all&uuid=1
After upgrade device is not responding and both leds are constantly on.
z-way-server.log is as follows:
ZMESerialupdater is not able to communicate with a board, but it was the same before upgrade.
zme_updater.log:
Is there any way to force bootloader and FW upgrade to make it up an running again ?
Board pictures attached.
https://service.z-wave.me/expertui/uzb/ ... all&uuid=1
After upgrade device is not responding and both leds are constantly on.
z-way-server.log is as follows:
Code: Select all
[2019-10-06 15:24:23.563] [D] [zway] Opened device: /dev/ttyAMA0
[2019-10-06 15:24:23.564] [D] [zway] Worker thread successfully created
[2019-10-06 15:24:23.564] [D] [zway] Worker thread entry point
[2019-10-06 15:24:23.564] [I] [zway] Adding job: Get controller info and supported function classes
[2019-10-06 15:24:23.574] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2019-10-06 15:24:23.775] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2019-10-06 15:24:23.775] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2019-10-06 15:24:23.977] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2019-10-06 15:24:23.977] [D] [zway] SENDING: ( 01 03 00 07 FB )
[2019-10-06 15:24:24.179] [I] [zway] Job 0x07 (Get controller info and supported function classes): No ACK received before timeout
[2019-10-06 15:24:24.179] [W] [zway] Job 0x07 (Get controller info and supported function classes) dropped: too many resends
[2019-10-06 15:24:24.179] [D] [zway] Job 0x07 (Get controller info and supported function classes): fail
[2019-10-06 15:24:24.179] [C] [zway] Get Serial API Capabilities returned zero.
[2019-10-06 15:24:24.179] [I] [zway] Removing job: Get controller info and supported function classes
[2019-10-06 15:24:24.189] [D] [zway] Worker thread exit point
[2019-10-06 15:24:24.189] [D] [zway] Worker thread successfully finished
[2019-10-06 15:24:24.200] [I] [zway] SaveData will not save data since it wasn't loaded. This is to prevent data loss.
[2019-10-06 15:24:24.219] [I] [core] Error: Bad data - communication failed
[2019-10-06 15:24:24.222] [I] [core] Tried 5 times without success. Stopping tries.
[2019-10-06 15:24:24.226] [I] [core] Notification: critical (z-wave): Cannot start Z-Wave binding: Error: Bad data - communication failed
zme_updater.log:
Code: Select all
Programmer starting on Linux.
ARGS:['./ZMESerialUpdater', 'serialapi_uzbupdate', '-d', '/dev/ttyAMA0'] VERSION:LWE0.9 MD5:--NA--
SILENT=True
>> {HEX, len = 5} 01 03 00 07 FB
>> {HEX, len = 5} 01 03 00 07 FB
>> {HEX, len = 5} 01 03 00 07 FB
>> {HEX, len = 5} 01 03 00 07 FB
>> {HEX, len = 5} 01 03 00 07 FB
>> {HEX, len = 5} 01 03 00 07 FB
>> {HEX, len = 5} 01 03 00 07 FB
Board pictures attached.
- Attachments
-
- IMG_5175.jpg (273.1 KiB) Viewed 6978 times
-
- IMG_3816.jpg (284.68 KiB) Viewed 6978 times
Re: Razberry v2 dead after firm upgrade
Can anyone tell me what is the pinout for TTL Uart interface ?
I would like to use external interface in order to program the chip.
I would like to use external interface in order to program the chip.
Re: Razberry v2 dead after firm upgrade
The pinout obviously fits Raspberry Pi pinout.
If both LEDs are faint, it is dead. Are they?
If both LEDs are faint, it is dead. Are they?
Re: Razberry v2 dead after firm upgrade
Hi buddy, can you share stats of the LEDs?Xusqui wrote: ↑05 Oct 2019 11:32Hi, neighbors and friends...
As the expert control panel said I was using my Razberry v2 (blue) in version 3.27. I visited the firmware map and saw there was an update to 5.36 with this file: https://service.z-wave.me/expertui/uzb/ ... 000002.bin
So I uploaded the firmware via expert UI, after a minute or so, went back to the firmware update page again, and now my Razberry is dead, it cannot be detected by the z-way server anymore.
I tried to completely shutdown the system, disconnect form electricity, wait 5 minutes, connect again cycle for a couple of times, but didn't work.
I can't attach the z-way-server.log file, because "It's too big" error in the web (even .tgz), so I provide a link to it: Link to z-way-server.log
Password: z-way-server-log
I guess it's bricked out (Don't know why), so I just acquire a new one, but I'd like to know what happened, so it won't happen again!
Thanks in advance!
PS:
BTW, I am on z-way-server 3.0.1 and raspbian buster updated
Regards,
Jivo Smith