wifi-live-or-resetboot-complete-notify# load the sketch/usr/bin/merge-sketch-with-bootloader.lua /www/sd/sketch/sk.cpp.hex/usr/bin/run-avrdude /www/sd/sketch/sk.cpp.hextouch /www/sd/booted#notif the phone/usr/bin/php-cli /www/sd/notif_boot.php# CURL/usr/bin/curl http://domain/url_to_checkexit 0
# load the sketch/usr/bin/merge-sketch-with-bootloader.lua /www/sd/sketch/sk.cpp.hex/usr/bin/run-avrdude /www/sd/sketch/sk.cpp.hex
root@arduino:~# php -vPHP 5.4.5 (cli) (built: Jun 20 2014 10:47:48)Copyright (c) 1997-2012 The PHP GroupZend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologiesroot@arduino:~# php-cli -vPHP 5.4.5 (cli) (built: Jun 20 2014 10:47:48)Copyright (c) 1997-2012 The PHP GroupZend Engine v2.4.0, Copyright (c) 1998-2012 Zend Technologies
/usr/bin/php-cli -v >/mnt/sda1/phpcli.log
ls -al /mnt/sda1/phpcli.log
What do you mean with redundant loading ?
I'm concerned about this part:I'm a little surprised at loading the sketch on each boot, but do you really want to append another copy of the bootloader to the sketch each time that the unit boots? You're going to end up with a lot of redundant data in the file, and will be trying to program the same regions over and over during one boot session.I would think you would want to do the bootloader merging only once, probably when the hex file is created or copied into place (however it is that the hex file comes into being on your system.)
I guess you're talking to me in reference to this?(..)I question whether you should really be programming the ATMega32U4 processor on every boot, but I really question the wisdom of appending the bootloader on every boot. It seems like a really bad idea to me.
Pipe the output into log file.Check log file time stamp after reboot.
I did this because when my Yun is OFF for one or 2 hours, if I switch it on the sketch is no longer active (REST commands unactive etc..) . It's possible I made it wrong.
But first, do you have something that looks like while (!Serial) in your setup function? Of course, since the REST API requires the use of the Linux services, is it possible that you're just not waiting long enough for Linux to fully boot (takes a minute or two) before trying to send the REST commands?
to work perfectly : is there a way to have no cumul of bootloader ?
try just putting "reset-mcu" in rc.local. That will reset the '32U4 once Linux has finished booting. If that works, maybe there is something in the way your sketch starts up that doesn't gracefully handle the longer delay needed for Linux to boot?An even simpler test is to do nothing in rc.local, and when the sketch doesn't start up properly after a power up, just hit the 32U4 RST button that is next to the Ethernet port. If that brings the sketch to life it proves that the sketch is still there and it's not an issue with the sketch being "forgotten."I still think you should post your sketch, someone may see a reason for your inconsistent running issues.
I will try this : http://forum.arduino.cc/index.php?topic=217663.0
which are solved and which are still on going?