04-27-2018, 08:48 PM
(This post was last modified: 04-27-2018, 08:49 PM by sensorback.)
After playing around with the CH340 nanos, I found out, that it doesn't matter if the pilight service is started or not, and also the config doesn't matter. It sometimes works, more often not.
Then I ordered a nano with FT232RL ("AptoFun Nano V3.0 Pro ATmega328P / FT232RL"). Same procedure, different symptoms, but same result: doesn't work properly. This one at least doesn't freeze after the "INFO: Checking for an ATMega328P @115200" line, but always gives this:
I guess I have to lookup the pilight-flash code, to understand what's up with those nanos o_0
Then I ordered a nano with FT232RL ("AptoFun Nano V3.0 Pro ATmega328P / FT232RL"). Same procedure, different symptoms, but same result: doesn't work properly. This one at least doesn't freeze after the "INFO: Checking for an ATMega328P @115200" line, but always gives this:
Code:
[Apr 27 19:39:50:605140] pilight-flash: INFO: **** START UPD. FW ****
[Apr 27 19:39:50:605176] pilight-flash: INFO: Indentifying microprocessor
[Apr 27 19:39:50:607273] pilight-flash: INFO: Checking for an ATMega328P @115200
[Apr 27 19:39:56:662955] pilight-flash: ERROR: ser_recv(): programmer is not responding
[Apr 27 19:39:56:663043] pilight-flash: ERROR: stk500_recv(): programmer is not responding
[Apr 27 19:39:56:663071] pilight-flash: ERROR: stk500_getsync() attempt 1 of 1: not in sync: resp=0x30
[...] same output the same for other baudrates and processors [...]
I guess I have to lookup the pilight-flash code, to understand what's up with those nanos o_0