• 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
pilight-flash not working
#1
Hello,

I am trying to get a ATtiny85 to work as a filter as described everywhere on this site. The problem I have is, that it simply doesn't work. It doesn't even print an error-message:

Code:
sudo pilight-flash -f /etc/pilight/pilight_firmware_t85_v3.hex
[ Apr 21 15:49:15:26633] pilight-flash: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/hardware.lua v1.0       
[ Apr 21 15:49:15:45136] pilight-flash: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/settings.lua v1.0         
[ Apr 21 15:49:15:48513] pilight-flash: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/registry.lua v1.0

is all I get. Although set to log-level 6 the log is empty with respect to pilight-flash and I managed to program a blinky on the ATtiny85 - so the chip is working and the sender/receiver as well. I disconnected the sender/receiver, but pilight-flash still shows the same behavior. 

Has anybody a clue what the problem might be?

Thanks,
Danny.
 
Reply
#2
Can you check if pilight-flash of pilight v8 still works?
 
Reply
#3
(04-21-2019, 05:09 PM)curlymo Wrote: Can you check if pilight-flash of pilight v8 still works?

I downgraded to 8.0 and at least there is some more output by now - but still not working:

Code:
sudo pilight-flash -f /etc/pilight/pilight_firmware_t85_v3.hex
[ Apr 21 17:51:32:43232] pilight-flash: INFO: **** START UPD. FW ****    
[ Apr 21 17:51:32:44083] pilight-flash: INFO: Indentifying microprocessor
[ Apr 21 17:51:32:55638] pilight-flash: INFO: Checking for an ATMega328P @115200
[Apr 21 17:51:32:217230] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 17:51:32:228514] pilight-flash: INFO: AVR device signature = 0x00 0x01 0x02
[Apr 21 17:51:32:229676] pilight-flash: INFO: Not an ATMega328P
[Apr 21 17:51:32:236228] pilight-flash: INFO: Checking for an ATMega328P @57600
[Apr 21 17:51:32:397166] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 17:51:32:408423] pilight-flash: INFO: AVR device signature = 0x31 0x00 0x01
[Apr 21 17:51:32:409648] pilight-flash: INFO: Not an ATMega328P
[Apr 21 17:51:32:416029] pilight-flash: INFO: Checking for an ATTiny25 @57600
[Apr 21 17:51:32:576948] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 17:51:32:588150] pilight-flash: INFO: AVR device signature = 0x61 0x01 0x02
[Apr 21 17:51:32:589265] pilight-flash: INFO: Not an ATTiny45
[Apr 21 17:51:32:595796] pilight-flash: INFO: Checking for an ATTiny45 @57600
[Apr 21 17:51:32:760270] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 17:51:32:771477] pilight-flash: INFO: AVR device signature = 0x00 0x0f 0x02
[Apr 21 17:51:32:772653] pilight-flash: INFO: Not an ATTiny85
[Apr 21 17:51:32:779169] pilight-flash: INFO: Checking for an ATTiny85 @57600
[Apr 21 17:51:32:943866] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 17:51:32:955213] pilight-flash: INFO: AVR device signature = 0x00 0x07 0x02
[Apr 21 17:51:32:956397] pilight-flash: ERROR: AVR unknown
[Apr 21 17:51:32:956977] pilight-flash: INFO: First run firmware_getmp
[Apr 21 17:51:32:957170] pilight-flash: INFO: **** FAILED UPD. FW ****


Looks like the 8.1.3 version ist not working correctly, but there seems to be another problem?
 
Reply
#4
Meanwhile I upgraded to 8.1.4 and pilight-flash seems to work here as well, but does not seem to be able to identify the device. I am not having a clue what could be wrong - I double checked the wiring…

Code:
sudo pilight-flash -f /etc/pilight/pilight_firmware_t85_v3.hex
[Apr 21 19:01:04:966575] pilight-flash: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/settings.lua v1.0
[Apr 21 19:01:04:973467] pilight-flash: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/registry.lua v1.0
[Apr 21 19:01:04:982201] pilight-flash: DEBUG: loaded event function /usr/local/lib/pilight/functions/date_format.lua v1.0
[Apr 21 19:01:04:983229] pilight-flash: DEBUG: loaded event function /usr/local/lib/pilight/functions/date_add.lua v2.0
[Apr 21 19:01:04:983781] pilight-flash: DEBUG: loaded event function /usr/local/lib/pilight/functions/random.lua v2.1
[Apr 21 19:01:04:984260] pilight-flash: DEBUG: loaded event function /usr/local/lib/pilight/functions/max.lua v2.1
[Apr 21 19:01:04:984733] pilight-flash: DEBUG: loaded event function /usr/local/lib/pilight/functions/min.lua v2.1
[Apr 21 19:01:04:985543] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/gt.lua v1.0
[Apr 21 19:01:04:986298] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/eq.lua v1.0
[Apr 21 19:01:04:986740] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/or.lua v1.0
[Apr 21 19:01:04:987430] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/and.lua v1.0
[Apr 21 19:01:04:988034] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/le.lua v1.0
[Apr 21 19:01:04:989299] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/ge.lua v1.0
[Apr 21 19:01:04:989771] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/concat.lua v1.0
[Apr 21 19:01:04:990254] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/intdivide.lua v1.0
[Apr 21 19:01:04:990658] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/ne.lua v1.0
[Apr 21 19:01:04:991127] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/minus.lua v1.0
[Apr 21 19:01:04:991507] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/multiply.lua v1.0
[Apr 21 19:01:04:991962] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/lt.lua v1.0
[Apr 21 19:01:04:992381] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/divide.lua v1.0
[Apr 21 19:01:04:992855] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/plus.lua v1.0
[Apr 21 19:01:04:993366] pilight-flash: DEBUG: loaded event operator /usr/local/lib/pilight/operators/modulus.lua v1.0
[Apr 21 19:01:04:994594] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/pushbullet.lua v1.0
[Apr 21 19:01:04:998044] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/dim.lua v4.1
[  Apr 21 19:01:05:1506] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/switch.lua v4.1
[  Apr 21 19:01:05:3560] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/pushover.lua v1.0
[  Apr 21 19:01:05:5182] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/sendmail.lua v4.1
[  Apr 21 19:01:05:6460] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/toggle.lua v4.1
[  Apr 21 19:01:05:8906] pilight-flash: DEBUG: loaded event action /usr/local/lib/pilight/actions/label.lua v4.1
[ Apr 21 19:01:05:12663] pilight-flash: INFO: **** START UPD. FW ****
[ Apr 21 19:01:05:12758] pilight-flash: INFO: Indentifying microprocessor
[ Apr 21 19:01:05:23601] pilight-flash: INFO: Checking for an ATMega328P @115200
[Apr 21 19:01:05:184963] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 19:01:05:195490] pilight-flash: INFO: AVR device signature = 0x62 0x00 0x02
[Apr 21 19:01:05:196606] pilight-flash: INFO: Not an ATMega328P
[Apr 21 19:01:05:202523] pilight-flash: INFO: Checking for an ATMega328P @57600
[Apr 21 19:01:05:363406] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 19:01:05:373966] pilight-flash: INFO: AVR device signature = 0x31 0x01 0x01
[Apr 21 19:01:05:375117] pilight-flash: INFO: Not an ATMega328P
[Apr 21 19:01:05:380884] pilight-flash: INFO: Checking for an ATTiny25 @57600
[Apr 21 19:01:05:541710] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 19:01:05:552270] pilight-flash: INFO: AVR device signature = 0x00 0x3d 0x07
[Apr 21 19:01:05:553417] pilight-flash: INFO: Not an ATTiny45
[Apr 21 19:01:05:559346] pilight-flash: INFO: Checking for an ATTiny45 @57600
[Apr 21 19:01:05:724146] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 19:01:05:734664] pilight-flash: INFO: AVR device signature = 0x00 0x3d 0x00
[Apr 21 19:01:05:735770] pilight-flash: INFO: Not an ATTiny85
[Apr 21 19:01:05:741546] pilight-flash: INFO: Checking for an ATTiny85 @57600
[Apr 21 19:01:05:908600] pilight-flash: INFO: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.00s
[Apr 21 19:01:05:919116] pilight-flash: INFO: AVR device signature = 0x3c 0x01 0x02
[Apr 21 19:01:05:920215] pilight-flash: ERROR: AVR unknown
[Apr 21 19:01:05:921445] pilight-flash: INFO: First run firmware_getmp
[Apr 21 19:01:05:921479] pilight-flash: INFO: **** FAILED UPD. FW ****
 
Reply
#5
Then you probably did something work with wiring.
 
Reply
#6
Unfortunately I am not getting any further. I checked the wiring multiple times - the only thing I am unsure with is the RESET pin. The wiring scheme in the wiki needs RESET to be connected to PIN 24, where I suppose it refers to the physical pin (eg. BCM 8) is this correct? If I configure it to "mode OUT" manually and run pilight-flash it is always "mode IN" afterwards.

Is pilight-flash using spidev? Do you have any other ideas what the problem might be or are there any ways to configure the pins to be used by pilight-flash manually? Could I simply use the manual avrdude via spidev to flash the pilight-firmware-hex file or ist pilight-flash doing some magic with it before flashing?

Thanks!

PS: Using the guide at http://www.instructables.com/id/Programm...pberry-Pi/ with the wiring set up as described there I can perfectly communicate with the ATTINY using spidev. But it never works with RESET connected to pin 24 (although I follow the description accordingly).
 
Reply
#7
Have you checked the wiring as described in the pilight manual?
 
Reply
#8
Yes and I just build it again from scratch - triple checked - without success. I even tried a different ATTINY85.


Is it possible to flash the *.hex file directly with avrdude or ist it modified by pilight-flash (because pilight-flash seems to read operators and actions on startup according to the output)?
 
Reply
#9
(04-27-2019, 05:40 PM)danny Wrote: Yes and I just build it again from scratch - triple checked - without success. I even tried a different ATTINY85.


Is it possible to flash the *.hex file directly with avrdude or ist it modified by pilight-flash (because pilight-flash seems to read operators and actions on startup according to the output)?

I just realized that obviously my GPIO 1 and 2 are blown due to experimenting around with 5v :Crying.. is the connection of DATA required to have pilight-flash working? I could use a working GPIO instead.
 
Reply
#10
You can use any pin. Just configure them properly in the config. Check the manual for the appropriate settings.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  update pilight Traeumer 0 53 07-29-2021, 09:41 PM
Last Post: Traeumer
  problem publish to pilight MQTT server Emiks5 8 1,588 07-24-2021, 06:46 PM
Last Post: Emiks5
  Hardware Switch and pilight-send/-control iTommix 3 549 02-14-2021, 09:25 PM
Last Post: iTommix
  pilight error after update to 8.1.5 on Odroid C2 WitchDoctor 4 1,731 02-07-2021, 09:50 PM
Last Post: pilightalpine
  pilight in Docker not accepting connections due to possible SYN flooding akloeckner 3 477 02-07-2021, 04:22 PM
Last Post: akloeckner
  ping not working, am I missing something? steffeneilers 2 293 02-03-2021, 08:09 PM
Last Post: steffeneilers
Lightbulb working MQTT in version v8.1.5-nightly-1af4c284 fleisch 1 686 12-28-2020, 05:04 PM
Last Post: psbest
  pilight-debug format Rschnauzer 2 461 12-17-2020, 07:09 PM
Last Post: Rschnauzer
  pilight does not start, Deamon is not found. Dekkertje 6 776 12-08-2020, 06:55 PM
Last Post: Dekkertje
  Failed pilight-send that say they succeeded hepcat72 2 500 12-05-2020, 05:30 PM
Last Post: hepcat72

Forum Jump:


Browsing: 1 Guest(s)