The LinkMeter Snapshot and YOU

[Steve_M]

No they are blank.

HeaterMeter Information
Version 20140630B

You need to update your HM firmware.

[NickH82]

You need to update your HM firmware.

Thx, did that again now but noticed an error:

Connecting to capnbry.net (71.100.233.140:80)

hm.hex 65% |******************** | 47310 0:00:00 ETA
hm.hex 100% |*******************************| 67722 0:00:00 ETA
Stopping LinkMeter OK

LinkMeter platform is BCM2708
AVR fuses ERROR

Starting LinkMeter

Any idea?

[Bryan Mayland]

EDIT: Ah that's why it didn't get the latest firmware. You've got a problem somewhere in the SPI communication between your HeaterMeter and the Pi. Check these connections with a multimeter for continuity:

[NickH82]

I just checked these connections,but there is zero resistance between them.. Anything else I could check?

[RalphTrimble]

It's always worth a try to reseat the rPi, the SD Card and the ATMega chip in its socket... Only takes a second and I have seen it remedy strange issues.

[NickH82]

It's always worth a try to reseat the rPi, the SD Card and the ATMega chip in its socket... Only takes a second and I have seen it remedy strange issues.

No luck either

[Bryan Mayland]

I don't know! Clearly it worked one time, enough to flash the first image. You try maybe slowing down the bitrate (which is what it does on the first upload because the default clock is very slow). SSH in and type this

insmod spidev
insmod spi-bcm2708
hmdude -v -v -b 128 -P/dev/spidev0.0 -U/lib/firmware/hm.hex

The first two might say "file exists" but that is ok.

[RalphTrimble]

I was gonna ask if this was the exact same hardware that was in place when this ATMega was flashed the first time?.....

[NickH82]

I don't know! Clearly it worked one time, enough to flash the first image. You try maybe slowing down the bitrate (which is what it does on the first upload because the default clock is very slow). SSH in and type this

insmod spidev
insmod spi-bcm2708
hmdude -v -v -b 128 -P/dev/spidev0.0 -U/lib/firmware/hm.hex

The first two might say "file exists" but that is ok.

root@heatermeter:~# hmdude -v -v -b 128 -P/dev/spidev0.0 -U/lib/firmware/hm.hex
hmdude: compiled on Sep 8 2015 at 10:00:37
Using port: /dev/spidev0.0
Loading ihex file: "/lib/firmware/hm.hex" (24072 bytes)
SPI speed: 128 KHz
Can't set AVR programming mode (0x00)

Hardware didn't change since first install...

I also found something in another thread, to run hmdude -b 128 -P/dev/spidev0.0

root@heatermeter:~# cat /dev/ttyAMA0
$HMSU,80,U,283.6,U,U,0,0,0*4F
$HMSU,80,U,283.6,U,U,0,0,0*4F
$HMAR,0,1,0,0,0,1*16
$HMSU,80,U,283.3,U,U,0,0,0*4A
$HMSU,80,U,283.3,U,U,0,0,0*4A
$HMSU,80,U,282.9,U,U,0,0,0*41
$HMSU,80,U,282.9,U,U,0,0,0*41
$HMAR,0,1,0,0,0,1*16
$HMSU,80,U,282.9,U,U,0,0,0*41
$HMSU,80,U,282.6,U,U,0,0,0*4E
$HMSU,80,U,282.6,U,U,0,0,0*4E
$HMSU,80,U,282.3,U,U,0,0,0*4B
$HMAR,0,1,0,0,0,1*16
$HMSU,80,U,282.3,U,U,0,0,0*4B
$HMSU,80,U,282.0,U,U,0,0,0*48
$HMSU,80,U,281.9,U,U,0,0,0*42
$HMSU,80,U,281.9,U,U,0,0,0*42
$HMAR,0,1,0,0,1,1*17
$HMSU,80,U,281.6,U,U,0,0,0*4D
$HMSU,80,U,281.6,U,U,0,0,0*4D
$HMSU,80,U,281.3,U,U,0,0,0*48
$HMSU,80,U,281.3,U,U,0,0,0*48
$HMAR,0,1,0,0,0,1*16
$HMSU,80,U,281.1,U,U,0,0,0*4A
$HMSU,80,U,281.0,U,U,0,0,0*4B
$HMSU,80,U,281.0,U,U,0,0,0*4B
$HMSU,80,U,280.6,U,U,0,0,0*4C
$HMAR,0,1,0,0,0,1*16
$HMSU,80,U,280.6,U,U,0,0,0*4C
$HMSU,80,U,280.3,U,U,0,0,0*49
$HMSU,80,U,280.3,U,U,0,0,0*49

$UCID,HeaterMeter,20140630B*3F
$HMSU,80,U,278.4,U,U,0,0,0*49
$HMAR,0,0,0,0,0,1*17
$HMSU,80,U,281.0,U,U,0,0,0*4B
$HMSU,80,U,280.0,U,U,0,0,0*4A
$HMSU,80,U,279.9,U,U,0,0,0*45

The rPI is type B version 2 with 512MB ram.

[Steve_M]

One of my RasPis exhibits this behaviour. I can do everything with the heatermeter but run a code upgrade on the atmega.