API not responding

[MADHUKARAVS]

Hi there,
I gone through the link and downloaded the code.
Im using Xmega32a4u board , Avr studio 4.18
Created Xboot.h hex file( enable UART and A LED for communication, Enable the API)
Programmed the Xboot.hex file and i can see the LED blinking and also UART responds with Xboot++ when i send 'S' through UART.

My problem is whenever i call Any API (get version) from my application code, its restarting
am i doing anything wrong?

[alexforencich]

No idea. Are you building your code with the xboot makefile? Have you read out the chip after writing the bootloader to make sure it was written to the proper location? Can you print out the jump table offset and confirm that the jump table is sitting at that location after programming?

[MADHUKARAVS]

Thank you for your quick response

• YES

*After Programming the Xboot.hex, i checked if its sits in the proper location.
For me It looks like its situated in proper location.
Please check it
/////////////////////////////////////////////////////
.
..............................................
:107FA000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFE1
:107FB000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFD1
:107FC000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFC1
:107FD000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFB1
:107FE000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFA1
:107FF000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF91
:108000000C94C5400C94DB400C94DB400C94DB409A
:108010000C94DB400C94DB400C94DB400C94DB4074
:108020000C94DB400C94DB400C94DB400C94DB4064
:108030000C94DB400C94DB400C94DB400C94DB4054
:108040000C94DB400C94DB400C94DB400C94DB4044
:108050000C94DB400C94DB400C94DB400C94DB4034
:108060000C94DB400C94DB400C94DB400C94DB4024
:108070000C94DB400C94DB400C94DB400C94DB4014
:108080000C94DB400C94DB400C94DB400C94DB4004
:108090000C94DB400C94DB400C94DB400C94DB40F4
:1080A0000C94DB400C94DB400C94DB400C94DB40E4
:1080B0000C94DB400C94DB400C94DB400C94DB40D4
:1080C0000C94DB400C94DB400C94DB400C94DB40C4
:1080D0000C94DB400C94DB400C94DB400C94DB40B4
:1080E0000C94DB400C94DB400C94DB400C94DB40A4
:1080F0000C94DB400C94DB400C94DB400C94DB4094
:108100000C94DB400C94DB400C94DB400C94DB4083
:108110000C94DB400C94DB400C94DB400C94DB4073
:108120000C94DB400C94DB400C94DB400C94DB4063
:108130000C94DB400C94DB400C94DB400C94DB4053
:108140000C94DB400C94DB400C94DB400C94DB4043
:108150000C94DB400C94DB400C94DB400C94DB4033
:108160000C94DB400C94DB400C94DB400C94DB4023
:108170000C94DB400C94DB4058426A01704777470F
:10818000A647D047BD477947E54711241FBECFEF2B
:10819000DFE2DEBFCDBF18BE19BE1ABE1BBE11E2A4
:1081A000A0E0B0E201C01D92A130B107E1F70E944A
:1081B00033440C94EC470C9400403BB78BBFFB015D
:1081C00086913BBF08953BB78BBFFB01879196918A
:1081D0003BBF089542E097C041E095C08093C00145
.
........................................
///////////////////////////////////////////////////////////////////////////////////////////

*Jump table? can u explain what exactly the jump table is?

[MADHUKARAVS]

Also after programming Xboot.hex, i m able to program my application code only once, second tie its giving verification error
.
Im currently trying the firmware upgrade thing.
When i call
xboot_get_version() function from my main, it return XB_ERR_NO_API

When i call
xboot_get_api_version() function from my main, its restart
(if i comment
ptr = PGM_READ_WORD(JUMP_TABLE_INDEX(0)); (in xbootapi.c)
its not restarting , looks like issue in jump table, know any solution ?)

[MADHUKARAVS]

Loaded the xboot.hex file to xmega32a4u and boot file starts from the location 0x8000

None of the API are working.
Im totally lost
Added Xbootapi.c and .h to my application code and called some of the API. None of them working

[alexforencich]

Are you sure you're compiling both your application and xboot for the atmega32a4u? There is an important difference between the two wrt. the size of the interrupt vector table. If this setting disagrees, then the API code will attempt to load the jump table from the wrong offset.

[alexforencich]

It looks like this is exactly the problem. iox32a4.h has the following:

#define _VECTOR_SIZE 4 /* Size of individual vector. */
#define _VECTORS_SIZE (94 * _VECTOR_SIZE)

while iox32a4u.h has:

#define _VECTOR_SIZE 4 /* Size of individual vector. */
#define _VECTORS_SIZE (127 * _VECTOR_SIZE)

The jump table is located at the end of the .vectors section in api.c:

struct xboot_jump_table_s api_jump_table __attribute((section(".vectors")))

The location of the table in xbootapi.c is determined like so:

#define JUMP_TABLE_LOCATION (BOOT_SECTION_START + _VECTORS_SIZE)

If the size of the vector table does not agree in both your user code and in xboot, then the API wrappers in xbootapi.c will not find the jump table.

Each of the 0C94xxxx in your hex dump corresponds to a jump instruction in the vector table. I count 94 of them. The 58426A after the last one is the 'magic number' 'XBj' that the API wrapper in xbootapi.c uses to detect the jump table. This indicates that xboot was compiled for the atxmega32a4 (non-u). My guess is that your application was compiled for the atmega32a4u and hence has a different value for _VECTORS_SIZE that makes it look in the wrong spot for the table. Try compiling xboot for the correct device and try again.

[MADHUKARAVS]

ho, thank you alex for your valueable display.

Yes, just checked the code and as you said, in boot code i selected 32a4 and in my app 32a4u.
i will change the setting and i will check again.

.
Again i have noticed in boot code If i select 'MCU = atxmega32a4u ' , it will give error as

xboot.c:1: error: MCU 'atxmega32a4u' supported for assembler only

[alexforencich]

That's very strange. What version of avr-gcc are you using? I can compile for the x32a4u just fine on my machine. I am running avr-gcc 4.8.1, avr-binutils 2.24, and avr-libc 1.8.0.

[MADHUKARAVS]

I am running avr-gcc 4.3.3, avr-binutils 2.19, and avr-libc 1.6.7.

[alexforencich]

Well, you may need to update that if you're having trouble compiling it. However, I fail to see why your program would build successfully for the x32a4u when xboot has issues, even though you're using the same make file. That is very strange.

[MADHUKARAVS]

thank you, i will update my AVR and will check my code again.
Thank you very much for your valuable reply :)