Atmel-8390-WIRELESS-AVR2054-Serial-Bootloader Upload Error

[vishal]

I have downloaded the Atmel-8390-WIRELESS-AVR2054-Serial-Bootloader_v3_2_0 . After reading the documentation I could successfully upload the bootloader.The MCU is avr-atmega256rfr2.The fuse bits we used are FF,9C,62(as specified in the documentation).After that, i converted the Bitcloud application code in ".elf" to ".srec" .Then I tried to upload the application code using boot loader PC tool.At this time it shows to reset the device.We reset it.After some seconds the PC bootloader raises an error showing  "Node cannot be programmed.Exceed try count" ..I tried the same thing through command prompt.What will be the issue?please help.

[ataradov]

This bootloader is very old and not really maintained. Do you have to use it? If not - use something else. I doubt anyone here will be able to help you, you will have to debug this stuff yourself.

[vishal]

I need a bootloader to upload the bitcloud application code and don't want to necessarily use this one.Are there any other Atmel's bootloader for supporting avr-atmega256rfrMCU?

[ataradov]

There is one in LwMesh package, for example. But ATmega's are very annoying in a way it supports bootloaders, so if you specifically need BitCloud support, then you better off just debugging that one.

[vishal]

We are also using Lwmesh_1_2_1 ..In which directory of Lwmesh the bootloader resides?

[ataradov]

Bootloader got removed from v1.2. Here is v1.1.1, and bl is still there. https://www.dropbox.com/s/qoft7d1kavu6u00/lightweight_mesh_stack_v1.1.1.zip?dl=0

But it will not work with BitCloud. BitCloud will want flash access functions to make PDS work, and it will expect them located in a specific way.

[vishal]

Thank you so much ataradov.We dont need to necessarily burn bitcloud.Lwmesh is enough.We haven't seen any documentation for how to use this bootloader.

[vishal]

I referred
http://www.avrfreaks.net/forum/lightweight-mesh-otau
http://www.avrfreaks.net/sites/default/files/OTA%20Upgrade%20Guide.pdf.
Added support for avr-atmega256rfr2MCU(linker).I could compile the bootloader.c file for avr-atmega256rfr2.Then I uploaded the bootloader image with fuse bits FF,1C,E2.After that I tried to load WSNDemo.elf file using the command 
python otaServerDemo.py -d -p COM4 -a 0x8555 -t 0x0010 WSNDemo.elf.
But I am getting the following error:

Port            : COM4
Baudrate     : 38400
Server        : 0x8555
Client         : 0x0010
PAN ID       : 0x1234
Channel      : 15 (0x0f)
Firmware     : WSNDemo.elf
Firmware size: 1483276 bytes
-> UART_COMMAND_COMM_CHECK
Error:response timeout.
What will be the reason for it?please help

[ataradov]

What are you trying to do?  This is an OTA server, not a bootloader utility. It also takes raw binary files, not ELF files.

There is no script for the bootloader itself, it uses Xmodem protocol, so any terminal program that can send files over Xmodem will upload a file (again, raw binary only).

[vishal]

Thanks .After loading the bootloader I tried to load a WSNDemo.bin file using an extraPutty terminal which supports Xmodem protocol.But I couldn't upload the image.I read that

To enter bootloader mode power on/reset the board while holding button down (the only
button in case of RCB and SW1 in case of MeshBean). Terminal emulator should receive
capital letter “C” every second.

I reset the device before sending file from extraPutty.But when I click send button the terminal waits for some time and exit.I am attaching the bootloader code of the atmega256rfr2 image.Why it happens so?

[ataradov]

Do you see letters 'C' in a terminal? That's the first step to debugging.

I really don't know off the top of my head. AVR is a really bad architecture for devices with large memory size. I switched to ARM and now my life is good again.

[vishal]

Do you see letters 'C' in a terminal? That's the first step to debugging.

I am not getting letters 'C' .  .  I reset the device after connecting the device to serial terminal and before sending file.Is that correct.

[ataradov]

Your code indicates PE0 as a boot entry pin. You need to pull that low and reset the device. This will requires a bootloader, and it will start sending letters 'C'. No need for any further resets.

[vishal]

Hi ,I could successfully uploaded the booloader.After that I tried to load application.For this I compiled WSNDemo application for a coordinator and loaded WSNDemo.bin using ExtraPutty with Xmodem protocol.No error has shown while loading the application.But When I tried to connect it to a serial terminal its only showing 'C'.We expected to display the coordinator name as "coordinator."Why it happens so.please reply.I am using avr-atmega256rfr2MCU The Code bootloader.c and Makefile also attached

[ataradov]

You are clearly still in bootloader mode, check that your boot entry condition is false after image upload. Also read out the resulting image and see if anything was written into the flash. Basically debug your stuff, I can't do that remotely.

[vishal]

Hi,I debug it and i could see that the booloader entry section is has not become false after WSNDemo.bin upload.since I chnaged the code from 128rfr1 to 256rfr2 i am confused wther any buffer or configuration is missing for it.Thats why I attached the files too.
The section 

Code: [Select]

if (0 == (status & ((1 << FE1) | (1 << DOR1) | (1 << UPE1)))){

      return true;
}
returns true .but after that any of the condition in

Code: [Select]


if (XMODEM_EOT == buf[0])
      {
        timeout = 0;
        handle_buffer();
        send(XMODEM_ACK);
        return;
      }
    }

     
    if (0 == ptr)
      continue;

    crc = get_crc();

    if (XMODEM_SOH == buf[0] && (uint8_t)seq == buf[1] && 0xff == (buf[1] + buf[2]) &&
        (buf[131] == (uint8_t)(crc >> 8)) && (buf[132] == (uint8_t)(crc)))
    {
      handle_buffer();
      seq++;
      send(XMODEM_ACK);
    }
    else
    {
      flush();
      send(XMODEM_NAK);
    }

not working.Simply returns to bootloader mode again.

[ataradov]

Entry section is sampling of the external pin. The code you shown here is just a part of the Xmodem protocol that has noting to do with entry.

Jut remove your active entry signal from the pin.

[vishal]

We removed the active entry signal on PE0 after images is uploaded and it exit from the bootloader mode.But it does not start the application.What may be the mistake with us.

[ataradov]

Have you checked that application was actually uploaded? Read out the device flash, and compare with what you have actually tried to upload.

There are only 2 ways bootloader can run - though explicit request or as a fall-trough if there is no application.

[vishal]

Have you checked that application was actually uploaded? Read out the device flash, and compare with what you have actually tried to upload.

I read out the device flash, the application was not uploaded successfully.But when i upload the code extra putty is not showing any error.What will the reason for this upload failure.Anyhow, I am debugging the code.But little confused whether it's because of hardware issue or bootloader issue.I tested  the same application without bootloader and it worked

[ataradov]

This clearly has nothing to do with the application, since bootloader fails to write received data into the flash. You need to debug that. Just manually call write_page()  and see if does anything. And tweak it until it does.

It may be related to EIND usage. I really don't remember any of this, I moved on to sane architectures, and it has been a long time since I did anything with AVR.

[vishal]

This clearly has nothing to do with the application, since bootloader fails to write received data into the flash. You need to debug that. Just manually call write_page()  and see if does anything. And tweak it until it does.

Sorry to disturb you again.I called write_page(addr,buf) from the main.But nothing has happened.The fuses i used are FE,1C,E2. Is it may be because of any configuration error?
I am debugging it.Surely i will try my best to solve it.Since the code is copied from avr-atmega128rfa1 little bit confused wther there any configuration has missed or not?

It may be related to EIND usage. I really don't remember any of this, I moved on to sane architectures, and it has been a long time since I did anything with AVR.

I main i set EIND=1 on entry  and EIND=0 on exit just before starting the application

[ataradov]

If you want help, decode fuse settings, I have no idea what those numbers mean in human language.

You should probably try examples from avr-libc and see if they work. Comment out all the Xmodem stuff and just make sure you can write a single page.

I really have no idea and without trying on a real hardware, I would not be able to tell what is wrong. And I don't have any real m256RFR2 hardware or programmers at the moment.

[vishal]

If you want help, decode fuse settings, I have no idea what those numbers mean in human language.

Code: [Select]

BODLEVEL  - 1 v8
OCDEN       - Enable
JAGEN        - Enable
SPIEN        -  Enable
WDTON     -  Disable
EESAVE      - Disable
BOOTSZ     -  1024w-1FC00
BOOTRST   -  Enable
CKDIV8     -  Disable
Ckout       -   Disable
CKSEl-SVT - INTRCOSL-6CK-65Ms
These are the fuse settings

You should probably try examples from avr-libc and see if they work. Comment out all the Xmodem stuff and just make sure you can write a single page.

I will try this.
Also I strated the work by refering this link

[url]http://www.avrfreaks.net/forum/lightweight-mesh-otau]http://www.avrfreaks.net/forum/lightweight-mesh-otau]
[url]http://www.avrfreaks.net/forum/lightweight-mesh-otau
[/url]

[vishal]

It Worked  .In linker script i had written

Code: [Select]

MEMORY
{
 text   (rx)  :  ORIGIN=0x00000000, LENGTH =256K-2K
 boot   (rx)  : ORIGIN=0x0003f800,  LENGTH=2K
 data   (rw!x): ORIGIN=0x00800190,LENGTH=32K-500
}
Then I modified this with following

Code: [Select]

MEMORY
{
  text  (rx)  : ORIGIN = 0x0003f800,LENGTH=2K
  boot (rx)   : ORIGIN=0x0003fffc,LENGTH=4
  data  (rw!x) : ORIGIN=0x00800190,LENGTH=16K-500
}

With this It worked.I could load the application with bootloader.
Noow I am trying to work on over the air upgrade.What are the necessary changes to make it work for avr-atmega256rfr2 rcb.I found it has only support for atmega128.Can I adopt the same withmodification for avr-atmega256rfr2?