• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error with loading LPF firmware
#1
Hallo,

I installed the LPF and the advised receiver/sender and get the following message while trying to install the firmware the second time after reboot.
Code:
pi@raspberrypi ~ $ sudo pilight-flash -f /etc/pilight/pilight_firmware_t45_v3.hex
[Apr 12 18:15:17:209914] pilight-flash: INFO: **** START UPD. FW ****
[Apr 12 18:15:17:213849] pilight-flash: INFO: Indentifying microprocessor
[Apr 12 18:15:17:229507] pilight-flash: DEBUG: running on a raspberrypi
[Apr 12 18:15:17:420612] pilight-flash: ERROR: AVR device not responding
[Apr 12 18:15:17:435761] pilight-flash: INFO: Not an ATMega328P
[Apr 12 18:15:17:671603] pilight-flash: ERROR: AVR device not responding
[Apr 12 18:15:17:678981] pilight-flash: INFO: Not an ATTiny45
[Apr 12 18:15:17:882120] pilight-flash: ERROR: AVR device not responding
[Apr 12 18:15:17:895676] pilight-flash: INFO: Not an ATTiny85
[Apr 12 18:15:18:116957] pilight-flash: ERROR: AVR device not responding
[Apr 12 18:15:18:119170] pilight-flash: ERROR: AVR unknown
[Apr 12 18:15:18:119735] pilight-flash: INFO: First run firmware_getmp
[Apr 12 18:15:18:119929] pilight-flash: INFO: **** FAILED UPD. FW ****
pilight-receive works and reports messages and also pilight-send works and sends messages.
I checked the cabling and did not find an error.
What does run firmware_getmp mean?
Raspberry B+  
Low-pass filter, Receiver RXB6, Sender I-XI
Version 7.0.178 (nightly version), Android App 6.0.4
 
Reply
#2
That it failed to indentify the MicroProcessor. This means your cabling is incorrect.
 
Reply
#3
(04-12-2015, 10:59 PM)curlymo Wrote: ... This means your cabling is incorrect.
I have a problem to understand the cabling schema.
In the cabling schema the pins are partly labeled by name or by pin-number in the wiki schema.
GPIO 23 is on pin 16, GIPIO 23 is on pin 18.

I cabled the following:
at 1 - GPIO 24 pin 18
at 2 - GPIO 18 pin 12
at 3 - Data of receiver
at 4 - GND
at 5 - 5V
at 6 - GPIO 23 pin 16
at 7 - GPIO 9 MISO pin 21
at 8 - GPIO 10 MOSI pin 19
Is this the correct cabling?
Raspberry B+  
Low-pass filter, Receiver RXB6, Sender I-XI
Version 7.0.178 (nightly version), Android App 6.0.4
 
Reply
#4
See the quickstart guide on the homepage for the correct cabling.
 
Reply
#5
Yes, the cabling schematic does need an update, the pin numbers do not correspond to anything I have found. An easy way of getting it right is to look at the default pins on the settings.json page of the wiki and using those as wiringPi pin numbers.
 
Reply
#6
Thanks,
I have found one difference:
I connected Att 6 to GPIO 23 pin 16 and not to GPIO 11 (SCLK) pin 23
Which one is correct?
Raspberry B+  
Low-pass filter, Receiver RXB6, Sender I-XI
Version 7.0.178 (nightly version), Android App 6.0.4
 
Reply
#7
As per manual: pin 23 (SCLK) is correct, this is WiringX GPIO 14/BCM GPIO 11, on a RasPi B+.
It has to be this pin because this is the SPI-SCLK pin.

[Image: q9EyutQ.jpg]
(click for large)
 
Reply
#8
Hello,

I changed at pin 6 to pi pin 23, but the chip is still not recognised.
Same messages as in first post.
This is the actual cableing:
at 1 - GPIO 24 pin 18
at 2 - GPIO 18 pin 12
at 3 - Data of receiver
at 4 - GND
at 5 - 5V
at 6 - GPIO 11 SCLK pin 23
at 7 - GPIO 9 MISO pin 21
at 8 - GPIO 10 MOSI pin 19
Is there still an other error?
Raspberry B+  
Low-pass filter, Receiver RXB6, Sender I-XI
Version 7.0.178 (nightly version), Android App 6.0.4
 
Reply
#9
Just go with a combination of the wiringX numbering, the schematic, and the default pins on the wiki:

Code:
+------------+---------+------+------+---------+----------+
|  Function  | wiringX | Chip | Chip | wiringX | Function |
+------------+---------+------+------+---------+----------+
| RESET      | 10      |    1 | 5    | 5V      | 5V       |
| pilight IN | 1       |    2 | 6    | 14      | SCK      |
| data IN    | n/a     |    3 | 7    | 13      | MISO     |
| GND        | GND     |    4 | 8    | 12      | MOSI     |
+------------+---------+------+------+---------+----------+

This is what I always use and it works very well
 
Reply
#10
Hallo,

it seems that I now have the correct cabling.
Code:
pi@raspberrypi ~ $ sudo pilight-flash -f /etc/pilight/pilight_firmware_t45_v3.hex
[Oct 17 15:53:09:467651] pilight-flash: INFO: **** START UPD. FW ****
[Oct 17 15:53:09:468904] pilight-flash: INFO: Indentifying microprocessor
[Oct 17 15:53:09:482633] pilight-flash: INFO: Checking for an ATMega328P @115200
[Oct 17 15:53:09:485749] pilight-flash: DEBUG: running on a raspberrypi
[Oct 17 15:53:09:647988] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:09:659778] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:09:661887] pilight-flash: INFO: Not an ATMega328P
[Oct 17 15:53:09:675142] pilight-flash: INFO: Checking for an ATMega328P @57600
[Oct 17 15:53:09:836894] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:09:848483] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:09:850788] pilight-flash: INFO: Not an ATMega328P
[Oct 17 15:53:09:872145] pilight-flash: INFO: Checking for an ATTiny25 @57600
[ Oct 17 15:53:10:42811] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[ Oct 17 15:53:10:54603] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[ Oct 17 15:53:10:56724] pilight-flash: INFO: Not an ATTiny45
[ Oct 17 15:53:10:78208] pilight-flash: INFO: Checking for an ATTiny45 @57600
[Oct 17 15:53:10:244689] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:256282] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:10:260999] pilight-flash: INFO: Not an ATTiny85
[Oct 17 15:53:10:272355] pilight-flash: INFO: Checking for an ATTiny85 @57600
[Oct 17 15:53:10:444653] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:456273] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:10:463938] pilight-flash: INFO: Firmware running on an ATTiny85
[Oct 17 15:53:10:694176] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:695540] pilight-flash: INFO: AVR device signature = 0x1e 0x93 0x0b
[Oct 17 15:53:10:696533] pilight-flash: INFO: AVR lfuse reads as E1
[Oct 17 15:53:10:697498] pilight-flash: INFO: AVR hfuse reads as E1
[Oct 17 15:53:10:697574] pilight-flash: INFO: AVR FLASH memory has been specified, an erase cycle will be performed
[Oct 17 15:53:10:697650] pilight-flash: INFO: AVR chip being erased
[Oct 17 15:53:10:859699] pilight-flash: INFO: reading input file "0xe1"
[Oct 17 15:53:10:859977] pilight-flash: INFO: writing lfuse (1 bytes)
Writing | ################################################## | 100% 0.00s
[Oct 17 15:53:10:860564] pilight-flash: INFO: 1 bytes of lfuse written
[Oct 17 15:53:10:909113] pilight-flash: INFO: verifying lfuse memory against 0xe1:
[Oct 17 15:53:10:909385] pilight-flash: INFO: load data lfuse data from input file 0xe1:
[Oct 17 15:53:10:909568] pilight-flash: INFO: input file 0xe1 contains 1 bytes
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:910359] pilight-flash: INFO: verifying ...
[Oct 17 15:53:10:910510] pilight-flash: INFO: 1 bytes of lfuse verified
[Oct 17 15:53:10:912610] pilight-flash: INFO: reading input file "0xe1"
[Oct 17 15:53:10:912865] pilight-flash: INFO: writing lfuse (1 bytes)
Writing | ################################################## | 100% 0.00s
[Oct 17 15:53:10:923747] pilight-flash: INFO: 1 bytes of lfuse written
[Oct 17 15:53:10:960820] pilight-flash: INFO: verifying lfuse memory against 0xe1:
[Oct 17 15:53:10:961095] pilight-flash: INFO: load data lfuse data from input file 0xe1:
[Oct 17 15:53:10:961278] pilight-flash: INFO: input file 0xe1 contains 1 bytes
Reading | ################################################## | 100% 0.00s
[Oct 17 15:53:10:962075] pilight-flash: INFO: verifying ...
[Oct 17 15:53:10:962224] pilight-flash: INFO: 1 bytes of lfuse verified
[Oct 17 15:53:10:964567] pilight-flash: INFO: reading input file "/etc/pilight/pilight_firmware_t45_v3.hex"
[Oct 17 15:53:10:969016] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex auto detected as Intel Hex
[Oct 17 15:53:10:970895] pilight-flash: INFO: writing flash (1146 bytes)
Writing | ################################################## | 100% 0.80s
[Oct 17 15:53:11:772157] pilight-flash: INFO: 1146 bytes of flash written
[Oct 17 15:53:11:815442] pilight-flash: INFO: verifying flash memory against /etc/pilight/pilight_firmware_t45_v3.hex:
[Oct 17 15:53:11:818296] pilight-flash: INFO: load data flash data from input file /etc/pilight/pilight_firmware_t45_v3.hex:
[Oct 17 15:53:11:818979] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex auto detected as Intel Hex
[Oct 17 15:53:11:820727] pilight-flash: INFO: input file /etc/pilight/pilight_firmware_t45_v3.hex contains 1146 bytes
Reading | ################################################## | 100% 0.69s
[Oct 17 15:53:12:515097] pilight-flash: INFO: verifying ...
[Oct 17 15:53:12:515344] pilight-flash: INFO: 1146 bytes of flash verified
[Oct 17 15:53:12:518345] pilight-flash: INFO: AVR lfuse reads as E1
[Oct 17 15:53:12:520299] pilight-flash: INFO: AVR hfuse reads as E1
[Oct 17 15:53:12:520872] pilight-flash: INFO: AVR fuses OK
[Oct 17 15:53:12:531723] pilight-flash: INFO: Finished updating firmware
[Oct 17 15:53:12:531999] pilight-flash: INFO: **** DONE UPD. FW ****
pi@raspberrypi ~ $
[/code]
But it seems to filter all my unknown Mumbi and SLG devices completely.
I get no entries with receive or debug.

For cross check I defined some sample devices for pilight webgui. If I switch those in the Android App this is reported with receive.
Does this proof, that my receiver and my sender works correct?
Or will receive report internally when a send request is processed?

Does someone has an idea how to debug my devices?

Best Regards:
Herwig
Raspberry B+  
Low-pass filter, Receiver RXB6, Sender I-XI
Version 7.0.178 (nightly version), Android App 6.0.4
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  433gpio platform error after raspbian dist upgrade HuberDe 2 169 10-12-2019, 07:35 PM
Last Post: HuberDe
  error pilightsend, recieve and control hansipi 2 487 11-04-2018, 03:46 PM
Last Post: hansipi
  generic_dimmer error / or not visible in 8.0.5 terrar 13 1,654 01-16-2018, 10:04 PM
Last Post: terrar
  pilight does no longer start because of hardware error stratege-0815 2 1,041 12-27-2017, 11:16 PM
Last Post: stratege-0815
  ERROR: uv_custom_poll_cb: bad file descriptor Gisto 6 1,583 12-19-2017, 03:03 PM
Last Post: Gisto
  [Solved] Error manual compiling Thuurke 2 1,234 09-02-2017, 05:06 PM
Last Post: Thuurke
  ERROR: config is not in a valid json format Sisko4 6 1,597 03-27-2017, 08:24 AM
Last Post: Sisko4
  Setup.sh CMAKE error ripper121 0 811 02-09-2017, 09:22 AM
Last Post: ripper121
  http GET request error 404 Not Found pelipeli 7 2,160 12-02-2016, 01:55 PM
Last Post: pilino1234
  sendmail - pilight terminates after smtp error wo_rasp 8 2,557 08-17-2016, 09:13 AM
Last Post: wo_rasp

Forum Jump:


Browsing: 1 Guest(s)