Not sure if I sent the email to the correct address (just replied the notification email from the forum) …but anyway I seem to understand a bit more now how things are layed out.
This is my current understanding (please correct me if I am wrong).
After installing all the boards using the Arduino IDE you get the following 3 main.cpp files
which provides the start-entry points for solo-coding, friendship-coding and “out-of-the box messaging”.
Functions provided in the *.ino will be called directly or indirectly from the above main.cpp files.
So I assume if I want to modify anything then just changing the code in either
causes the Arduino IDE to cross-compile the changes before it uploads it onto the Jewelbot - right ?
Or is there an extra step required? I assume some of the code is shared between those 3 modes (like messaging.c)?
Do I need to rebuild JWB_update_1_1_6a.zip as well somehow (not sure about what those zip’s actually contain)?
The content of main.cpp for \Jewelbots_Firmware_Update and Jewelbots_Friendship_Library makes sense to me
but the “Firmware”-one just seems to be
int attribute ((weak)) main( void )
Does this mean I could still implement setup() and loop() when I do “Firmware Update” (I thought that it needed to be empty). Given that main() is stuck in that loop() all the time how is the “checking if friends are near” etc implemented in this case. Is there a timer event that causes the arduino to check ? The friendship main.cpp has all kind of setup/state-machine code in it but I could not find if a similar thing is happening when using “Firmware Update” …
Thanx so much for your help (sorry for so many questions)