What do you use for burn bootloader on 3v boards?
-
@sergio-rius Yes, if I find time I'll compile a 16Mhz version
@tekka I have some news.
After burning this version, the board doesn't accept loading a sketch through FTDI.Sketch uses 7666 bytes (24%) of program storage space. Maximum is 30720 bytes. Global variables use 348 bytes (16%) of dynamic memory, leaving 1700 bytes for local variables. Maximum is 2048 bytes. C:\Users\sergio\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/bin/avrdude -CC:\Users\sergio\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf -v -patmega328p -carduino -PCOM8 -b57600 -D -Uflash:w:C:\Users\sergio\AppData\Local\Temp\arduino_build_767496/DimmableLEDActuator.ino.hex:i avrdude: Version 6.3, compiled on Jan 17 2017 at 12:00:53 Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/ Copyright (c) 2007-2014 Joerg Wunsch System wide configuration file is "C:\Users\sergio\AppData\Local\Arduino15\packages\arduino\tools\avrdude\6.3.0-arduino9/etc/avrdude.conf" Using Port : COM8 Using Programmer : arduino Overriding Baud Rate : 57600 avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0xaf avrdude: stk500_recv(): programmer is not responding avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0xaf avrdude done. Thank you. Problem uploading to board. See http://www.arduino.cc/en/Guide/Troubleshooting#upload for suggestions.But it shows a new "Booting" node in MYSController and seems FW can be uploaded, but at an absord slow speed.
May this speed be a problem of mine with the rPI gateway. The part of the service that handles radio hangs in periodically and I have to SSH into the rPi and restart the service. During this, MYSC talks with the service but nothing is sent or received.
10 minutes already passed and it's still writing the 30B sketch.
-
Playing with another node I realized that burning bl+sketch through avrdude gives a node with MYSBL that boots asking for sketch but immediately goes on with the sketch. So far is a good solution. :+1:
The firsts still uploading the 30B sketch :flushed:
Are you sure that it's normal?Edit: It has been uploading (i think several times) for the last 50mins and now is stuck in "Booting: 50.1 (BL1.3)"
-
About the issue of my gateway I talked before. I found that the problem must be induced by domoticz.
As I was tired of reseting the GW during those tests (and not being able to open my door garaje), I built a new esp gateway. I ran a 2.4Ghz scanner that covers all the channels and decided for a clean 100+ channel.
The gateway passed the tests and I connected it to domoticz.
I re-configured two nodes for working with it, but they weren't registering. I then realized that my rPi gw was in it's "halt" status... but also the wifi one.
So I've restarted Domoticz and bingo, the nodes started registering on the wifi gw.
Seems that my Domoticz installation may be sending something that makes gw freeze. I thought that could be my mains consumption counter as it was a big number, but I resetted to zero two days ago for this sake.
If devels want to make me dump logs or anything I'll be putting my installation on quarantine.It's halted again. When that occurs this is the only registered on MYSC:
-
@gohan What do you mean? The rPi or the Esp?
For the rPi I first used a NRF24 pa lna getting power from the 5v line with a voltage regulator (ams1117 based)
Then I thought could be problems with this radio or supply and ditched it for a normal NRF24. With identical behavior. Sometimes works for a week or a couple of them or I have to restart the whole Pi several times a day only for being able to go out of home.
When I first implemented the rPiGw worked for weeks. Then the problem appeared. then vanished and was working for months until some point that became worse.
I even thought that my wifi hotspot could be dying and changed it for a unify-pro (nice gadget)
I live in a house far from others, so wifi interference seems not an issue.I run the Pi from a readonly sd for boot partition and then uses an usb drive for the system+controller. logs on tmpfs.
I was fastly implementing it in my home, but as this problems arose, I only have the power monitor node, the garaje door node and a doorbell that is offline because suspiciously started to eat batteries two months ago.
I'm in Domoticz beta.
For the esp gw it's just a nodemcu board on a breadboard paired to a normal nrf24.
Edit: Ups! mysensors versions are all 2.2.0. The arduinos are all 3v3 8mhz boards and one 5v (power)
