Massive issue with 2.2.2 and 05.04 firmware

[codypchristian]

Hello,

I've been running 2.2.1 since it came out with "Serial API Version: 05.00" firmware. However 2 days ago I upgraded to 2.2.2 and then upgraded firmware to "Serial API Version: 05.04" and now nothing appears to be working device wise. I get "Device appears to be dead" on all 20+ devices now. I tried going back to 2.2.1 and same results. Any ideas? My only thought is the 5.04 upgrade caused this. Anyway to go back? I can't even locate that firmware in git anywhere. Thank you.

Side note: I also attempted to use OpenHAB2 as well and exact same issues so I really do think its a problem with the firmware on the daughter board chip.

Controller Data:

Code: Select all

/: None (11:54)
    nodeId: 1 (11:54)
    homeId: -190074062 (11:54)
    SUCNodeId: 1 (11:54)
    isPrimary: true (11:54)
    isInOthersNetwork: false (11:54)
    isRealPrimary: true (11:54)
    isSUC: true (11:54)
    SISPresent: true (11:54)
    libType: Static Controller (11:54)
    SDK: 6.51.06 (11:54)
    ZWlibMajor: 4 (11:54)
    ZWlibMinor: 5 (11:54)
    ZWLib: 1 (11:54)
    ZWVersion: 5 (11:54)
    ZWaveChip: ZW0500 (11:54)
    APIVersion: 05.04 (11:54)
    manufacturerId: 327 (11:54)
    vendor: RaZberry by Z-Wave.Me (11:54)
    manufacturerProductType: 1024 (11:54)
    manufacturerProductId: 2 (11:54)
    capabilities: 2,3,4,5,6,7,8,9,10,16,17,18,19,20,21,22,23,24,28,32,33,34,35,36,39,40,41,42,43,44,45,65,66,68,69,70,71,72,73,74,75,76,77,80,81,83,84,85,86,87,94,96,97,98,99,102,103,120,128,144,146,147,152,180,182,183,184,185,186,189,190,191,210,211,212,239,242,244,245 (11:54)
    controllerState: 0 (12:29)
    nonManagmentJobs: 0 (11:54)
    lastIncludedDevice: None (12:25)
    lastExcludedDevice: None (12:25)
    secureInclusion: true (12:22)
    oldSerialAPIAckTimeout10ms: 10 (11:54)
    oldSerialAPIByteTimeout10ms: 10 (11:54)
    curSerialAPIAckTimeout10ms: 10 (11:54)
    curSerialAPIByteTimeout10ms: 10 (11:54)
    countJobs: false (11:54)
    memoryGetAddress: None (11:54)
    memoryGetData: None (11:54)
    functionClasses: 2,3,4,5,6,7,8,18,19,21,22,23,32,33,34,35,36,39,41,42,43,44,45,65,66,68,70,71,72,73,74,75,76,77,80,81,82,83,84,85,86,87,96,97,98,99,128,186,190,210,211,242,243,244,245 (11:54)
    functionClassesNames: SerialAPIGetInitData,SerialAPIApplicationNodeInformation,ApplicationCommandHandler,GetControllerCapabilities,SerialAPISetTimeouts,GetSerialAPICapabilities,SerialAPISoftReset,SendNodeInformation,SendData,GetVersion,SendDataAbort,RFPowerLevelSet,GetHomeId,MemoryGetByte,MemoryPutByte,MemoryGetBuffer,MemoryPutBuffer,FlashAutoProgSet,NVMGetId,NVMExtReadLongBuffer,NVMExtWriteLongBuffer,NVMExtReadLongByte,NVMExtWriteLongByte,GetNodeProtocolInformation,SetDefault,ReplicationReceiveComplete,AssignReturnRoute,DeleteReturnRoute,RequestNodeNeighbourUpdate,ApplicationNodeUpdate,AddNodeToNetwork,RemoveNodeFromNetwork,CreateNewPrimary,ControllerChange,SetLearnMode,AssignSUCReturnRoute,EnableSUC,RequestNetworkUpdate,SetSUCNodeId,DeleteSUCReturnRoute,GetSUCNodeId,SendSUCNodeId,RequestNodeInformation,RemoveFailedNode,IsFailedNode,ReplaceFailedNode,GetRoutingTableLine,RFPowerLevelGet,SendTestFrame,WatchDogStart,WatchDogStop,ZMEFreqChange,ZMERestore,ZMEBootloaderFlash,ZMECapabilities (11:54)
    softwareRevisionVersion: v2.2.1 (11:54)
    softwareRevisionId: a52a38822b6872f5b9fab0903b30ab65a2c70605 (11:54)
    softwareRevisionDate: 2016-02-18 17:41:33 +0300 (11:54)
    uuid: 2a8c99c9d6c0290da77cf2a352488b1d (11:54)
    caps: 0,0,255,5 (11:54)
    frequency: US (12:37)

[codypchristian]

I've rebooted again and now all I get is that it can't find the daughterboard. Man this firmware has really screwed stuff up!

[2016-06-26 13:18:19.651] [C] [i/o] Failed to open device /dev/ttyAMA0: No such file or directory

Both zbw_connect and z-way-server were running and haven't been touched, all I did was restart. Now zbw_connect is still up but z-way-server dies because it can't connect to the device.

Ideas?

[PoltoS]

Upgrading to new f/w can not affect AMA0, since it is h/w port on your Pi. So, if AMA0 is missing, means your kernel parameters were screwed up. What is your OS?

[codypchristian]

Hey, the only change was upgrading the firmware. The OS was not modified or upgraded.

Currently it is:
Linux raspberrypi 4.4.13-v7+ #894 SMP Mon Jun 13 13:13:27 BST 2016 armv7l GNU/Linux
Raspbian GNU/Linux 8 (jessie)

[PoltoS]

Solved?

[vosmont]

Hello,

I was on 2.2.3 and try to upgrade with

Code: Select all

wget -q -O - razberry.z-wave.me/install | sudo bash

reboot

now I've got the same problem :

Code: Select all

 [C] [i/o] Failed to open device  /dev/ttyAMA0: No such file or directory

Some infos on my Raspberry B:

Code: Select all

pi@openLuup:~ $ uname -a
Linux openLuup 4.1.18+ #846 Thu Feb 25 14:11:56 GMT 2016 armv6l GNU/Linux

pi@openLuup:~ $ cat /proc/version
Linux version 4.1.18+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #846 Thu Feb 25 14:11:56 GMT 2016

pi@openLuup:~ $ cat /etc/issue
Raspbian GNU/Linux 8 \n \l

pi@openLuup:~ $ cat /etc/debian_version
8.0

pi@openLuup:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

dmesg :

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.1.18+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #846 Thu Feb 25 14:11:56 GMT 2016
[    0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine model: Raspberry Pi Model B Rev 2
[    0.000000] cma: Reserved 8 MiB at 0x1b400000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 114688
[    0.000000] free_area_init_node: node 0, pgdat c0839994, node_mem_map db010000
[    0.000000]   Normal zone: 1008 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 114688 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113680
[    0.000000] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708.boardrev=0xe bcm2708.serial=0x3f4c4a29 smsc95xx.macaddr=B8:27:EB:4C:4A:29 bcm2708_fb.fbswap=1 bcm2708.uart_clock=3000000 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000  console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 436836K/458752K available (5792K kernel code, 488K rwdata, 1788K rodata, 352K init, 720K bss, 13724K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xdc800000 - 0xff000000   ( 552 MB)
    lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc076f1f0   (7581 kB)
      .init : 0xc0770000 - 0xc07c8000   ( 352 kB)
      .data : 0xc07c8000 - 0xc0842260   ( 489 kB)
       .bss : 0xc0842260 - 0xc08f63e0   ( 721 kB)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:522
[    0.000000] clocksource stc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[    0.000015] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[    0.000055] Switching to timer-based delay loop, resolution 1000ns
[    0.000342] Console: colour dummy device 80x30
[    0.001249] console [tty1] enabled
[    0.001306] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)
[    0.001392] pid_max: default: 32768 minimum: 301
[    0.001768] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.001839] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.002896] Initializing cgroup subsys blkio
[    0.002991] Initializing cgroup subsys memory
[    0.003061] Initializing cgroup subsys devices
[    0.003122] Initializing cgroup subsys freezer
[    0.003182] Initializing cgroup subsys net_cls
[    0.003302] CPU: Testing write buffer coherency: ok
[    0.003420] ftrace: allocating 19747 entries in 58 pages
[    0.107952] Setting up static identity map for 0x81c0 - 0x81f8
[    0.110127] devtmpfs: initialized
[    0.120836] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[    0.121291] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.123292] pinctrl core: initialized pinctrl subsystem
[    0.124199] NET: Registered protocol family 16
[    0.129628] DMA: preallocated 4096 KiB pool for atomic coherent allocations
[    0.131057] bcm2708.uart_clock = 3000000
[    0.135949] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[    0.136026] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.136233] Serial: AMBA PL011 UART driver
[    0.136532] 20201000.uart: ttyAMA0 at MMIO 0x20201000 (irq = 83, base_baud = 0) is a PL011 rev2
[    0.501688] console [ttyAMA0] enabled
...

[PoltoS]

@vosmont This is because you use some custom openLuup distro. Make sure how serial port is accessed there.

@pepeEL please don't write in unrelated threads about your problem