Okay i found my problems.

1. One of my nrf24 board seems to have an defect. It does not send anything but receive works.#
2. After i've changed my nrf24 board, the node appeared just after burning the bootloader at my gateway.
3. Flashing via ethernet gateway (Arduino uno and w5100 board) was not possible.

• I figured out, that lot of people have trouble with this, because the arduino reboots very often.
• After updating to mysensors lib 2.2.0-beta this was better, but mostly my ethernet connection was lost during ota firmware update.
  -There are lot of interesing things, that problmes came up with avr board revision 1.6.8. Also some problems are there with an resistor. I've no idea if the resistor problem occures only with newer board revisions.

I got my ethernet problems solved, with removing the sd card from the ethernet shield. I did not used it, it was there from an older project. No really idea, whats up with that sd card, but without an sd card connected, i was able to update my sketches.

I also used the bootloader from MySensorsBootloaderRF24-development and figured out that this one is needed to reassign the id.

When i burn a sketch in the node, it hangs after sending the ota flash command.

Same occures if i send a reboot command.

How do i have to flash the sketch the first time?

Hi,

I've connected mysyscontroller and rebootet the node after i reconnected the nrf radio chip.

But the node has only the bootloader, it has no sketch installed.

The radio works, because the gateway receives data. The postet log in my post #1 repeats endless and is shown in captured from the mysyscontroller .

I've burned the mysensors bootloader onto a arduino nano.

I see in the debug output from my gateway (serial and ethernet tested) that there is a communication between the node and the gatway.
But the node is not registered in the mysyscontroller tool. So how can i upload a firmware to that node?

That is, what i can see in the debug log:

0;255;3;0;9;TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=1,l=1,sg=0:0
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=255
0;255;3;0;9;TSF:CKU:OK,FCTRL
0;255;3;0;9;TSF:MSG:GWL OK
0;255;3;0;9;TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
0;255;3;0;9;TSF:MSG:READ,255-255-255,s=255,c=3,t=7,pt=1,l=1,sg=0:0
0;255;3;0;9;TSF:MSG:BC
0;255;3;0;9;TSF:MSG:FPAR REQ,ID=255```


That is how i flashed the arduino:

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 "Z:\Programme\Arduino\hardware\tools\avr/etc/avrdude.conf"

     Using Port                    : usb
     Using Programmer              : usbasp
     AVR Part                      : ATmega328P
     Chip Erase delay              : 9000 us
     PAGEL                         : PD7
     BS2                           : PC2
     RESET disposition             : dedicated
     RETRY pulse                   : SCK
     serial program mode           : yes
     parallel program mode         : yes
     Timeout                       : 200
     StabDelay                     : 100
     CmdexeDelay                   : 25
     SyncLoops                     : 32
     ByteDelay                     : 0
     PollIndex                     : 3
     PollValue                     : 0x53
     Memory Detail                 :

                              Block Poll               Page                       Polled
       Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
       ----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
       eeprom        65    20     4    0 no       1024    4      0  3600  3600 0xff 0xff
       flash         65     6   128    0 yes     32768  128    256  4500  4500 0xff 0xff
       lfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       hfuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       efuse          0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       lock           0     0     0    0 no          1    0      0  4500  4500 0x00 0x00
       calibration    0     0     0    0 no          1    0      0     0     0 0x00 0x00
       signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00

     Programmer Type : usbasp
     Description     : USBasp, http://www.fischl.de/usbasp/

avrdude: auto set sck period (because given equals null)
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: auto set sck period (because given equals null)
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: reading input file "Z:\Programme\Arduino\hardware\arduino\avr/bootloaders/MySysbootloader/MYSBootloader_1.3pre3.hex"
avrdude: writing flash (32762 bytes):

Writing | ################################################## | 100% 0.00s

avrdude: 32762 bytes of flash written
avrdude: verifying flash memory against Z:\Programme\Arduino\hardware\arduino\avr/bootloaders/MySysbootloader/MYSBootloader_1.3pre3.hex:
avrdude: load data flash data from input file Z:\Programme\Arduino\hardware\arduino\avr/bootloaders/MySysbootloader/MYSBootloader_1.3pre3.hex:
avrdude: input file Z:\Programme\Arduino\hardware\arduino\avr/bootloaders/MySysbootloader/MYSBootloader_1.3pre3.hex contains 32762 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: 32762 bytes of flash verified
avrdude: reading input file "0x0F"
avrdude: writing lock (1 bytes):

Writing | ################################################## | 100% 0.01s

avrdude: 1 bytes of lock written
avrdude: verifying lock memory against 0x0F:
avrdude: load data lock data from input file 0x0F:
avrdude: input file 0x0F contains 1 bytes
avrdude: reading on-chip lock data:

Reading | ################################################## | 100% 0.00s

avrdude: verifying ...
avrdude: 1 bytes of lock verified

avrdude done. Thank you.```

I've also tested the mysensors bootloader from the development branch, but that wasn't better.

I hope someone has an idea, whats going wrong.

Sidey