xbee and bootloader

Hello,

Is it possible to upload sketch on mega 2560 via xbee?

Here my configuration :

  • DFRobot 2560 + Xbee Shield + Xbee 1mw s 1
  • Xbee Usb Explorer + Xbee 1mW s 1

When i send the command :

Code: [Select]

E:\Arduino\arduino-1.0\hardware/tools/avr/bin/avrdude -CE:\Arduino\arduino-1.0\hardware/tools/avr/etc/avrdude.conf -v -v -v -v -patmega2560 -cstk500v2 -P\.\COM5 -b115200 -D -Uflash:w:E:\Arduino\Xbee\Blink.cpp.hex:i

avrdude send the command 1B 01 00 01 0E 01 14
1B : begin
01 : number
00 01 : length
0E : begin of msg
01 : th msg who ask to execute CMD_SIGN_ON
14 : checksum

Normaly, the bootloader reply 1B 01 00 0B 0E 01 00 08 41 56 52 49 53 50 5F 32 74
1B : begin
01 : number
00 0B : length
0E : begin of the msg
01 00 08 41 56 52 49 53 50 5F 32 : th msg
01 : command CMD_SIGN_ON
00 : STATUS_CMD_OK
08 41 56 52 49 53 50 5F 32 : 8AVRISP_2
74 : checksum

When i send via xctu directly to mega 2560 just ater push the reset button and without the xbee module, i’ve got the right answer.
When i send via xctu thrue the xbee module to mega 2560 just ater push the reset button, i’ve got the answer.
1B 01 80 21 80 49 53 50 5 32 74
The length of the msg is 80 21, 32801 bytes and avrdude is waiting for a long time.

I put a snapshot of xctu in attachment.
COM7 is the usb explorer, COM5 the arduino.

I thing that the bootloader is not the problem.
Is there a problem on the mega board?

Jerome

In fact, i think my 0x00 (Null caracter) are change in 0x80 in the response between xbee - xbee - driver ftdi. Is it a problem of configuration ? Is someone as an idea ?

Jérôme