Bitcloud OTAU strange behaviour

Go To Last Post
3 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Good day(or night) to everybody!
Some history...
Some time ago we developed custom board based on AtmegaRfa1 (compatible with RCB board). Software on if based on WSNDemo from Bitclowd 1.14 (with HAL and BSP modifications for additional hardware). All work fine.
Last week I deside to switch on OTAU service on our controller.
External memory AT45DB041D. OTAU Bootloader find controller and start to download image... All was OK, except the final stage... OTAU client continue to request NEXT_IMAGE_BLOCK past end of image size... After changing version number and rebuilding image process restarted from the beginning (as expected) and ended with success.. I can switch to new version... I continue to upgrade... Process stale... Once more... All OK. :(
After some research I find out that success upload was on odd (or may be even) attempts... After parsing log files I found that client unexpectidly request EEPROM header...
When success:
imageSize 0x0001E29D
fileOffset 0x0000003E
maxDataSize 0x08
...
fileOffset 0x0000003E
dataSize 0x08
imageData: 0x00 0x00 0x00 0x00 0x4E 0xD2 0x01 0x00
(proper start position and length of flash part of image)
....
....
fileOffset 0x0001D294
maxDataSize 0x08
...
fileOffset 0x0001D294
dataSize 0x08
imageData: 0x00 0x00 0x81 0x00 0x00 0x10 0x00 0x00
(proper start position and length of eeprom part of image)

When NOT success:
first part is OK, but the second...

fileOffset 0x0001BFBC
maxDataSize 0x08
...
i.e. request for EEPROM part came too early... (At this offset there is flash data) Something went wrong...

Does anybody have this problem...
And what to do? As there is no sources of OTAU part of Bitclowd stack it is very difficult to find the error... (Even with this strange error other part of software worked fine)...

Last Edited: Fri. Oct 16, 2015 - 02:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Contact avr@atmel.com, they've had a number of OTAU related requests, so they might be able to help.

NOTE: I no longer actively read this forum. Please ask your question on www.eevblog.com/forum if you want my answer.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for reply!
I wrote a letter to avr@atmel.com and now waiting for reply... :)