I am currently using bitcloud 3.2.0 and have I am using the Atmega2564RFR2 on all my devices. My main board that I will use as a coordinator I am using the rf chip as a zigbee supporting chip to the main atmega1284P. Currently I can do OTA's to my 1284P and have created another bootloader with my own protocol to program the rf chip and it appears all my bootloaders are programming my chips correctly (Verified with ICE flash read and general application operation).
My issue is that while reading the zigbee configuration.h file and looking at the hex file, I have 2 options. I can disable the dependecy on the bootloader by leaving the definition "#define PDS_NO_BOOTLOADER_SUPPORT" uncommented, but it adds a small application to the bootloader section of the hex file. Or I can comment the line out and it creates a dependency on the bootloader, typically the atmel bootloader from the application note (if I read one of the previous posts correctly).
Am I correct in what I have mentioned above? Or have I somehow misread the comments?
Ideally I would like to use my own bootloader on the coordinator chip, use it as the OTA server and pass the flash file to it so it can do the OTA to the routers and/or end devices that use the default bootloader. Can this be done without going too deep into the stack?
Looking forward to some advice,