resetVecs no longer moves correctly with tirtos_tivac_2_00_01_23

Barry Andrews

I have just updated a CCS V6 program to tirtos_tivac_2_00_01_23 and now find that resetVects is still left at 0 even though I wish to move it to 0x8000 to allow for a bootloader.

Previously under tirtos_1_21_00_09 I had to add the following line to the config script

Program.sectMap[".resetVecs"] = "FLASH_VEC";

Then in the CMD file I set the address I wanted resetVect to now be set at.

MEMORY
{
// This is where our application can start
FLASH_BT (RX) : origin = 0x00000000, length = 0x00008000
FLASH_VEC (RX) : origin = 0x00008000, length = 0x00000400
FLASH (RX) : origin = 0x00008400, length = 0x000F8C00
SRAM (RWX) : origin = 0x20000000, length = 0x00040000
}

Previously this would correctly locate everything at the new address - example offset to 0x5000

run origin load origin length init length attrs members
---------- ----------- ---------- ----------- ----- -------
00005000 00005000 00000360 00000360 r--
00005000 00005000 00000360 00000360 r-- .resetVecs
00005400 00005400 00024aa0 00024aa0 r-x
00005400 00005400 0001f782 0001f782 r-x .text
00024b84 00024b84 00004a58 00004a58 r-- .const
000295e0 000295e0 000008c0 000008c0 r-- .cinit
20000000 20000000 00000360 00000000 rw-
20000000 20000000 00000360 00000000 rw- .vecs
20000400 20000400 0001b694 00000000 rw-
20000400 20000400 0001a2ac 00000000 rw- .bss
2001a6ac 2001a6ac 00000fe8 00000000 rw- .data
2001b694 2001b694 00000400 00000000 rw- .stack

However I now find that regardless of what I do there are 0x3C bytes located at address 0 - example below setting resetVecs to 0x8000

run origin load origin length init length attrs members
---------- ----------- ---------- ----------- ----- -------
00000000 00000000 0000003c 0000003c r--
00000000 00000000 0000003c 0000003c r-- .resetVecs
00008400 00008400 00022c68 00022c68 r-x
00008400 00008400 0001e28c 0001e28c r-x .text
0002668c 0002668c 000044b8 000044b8 r-- .const
0002ab48 0002ab48 00000520 00000520 r-- .cinit
20000000 20000000 00000360 00000000 rw-
20000000 20000000 00000360 00000000 rw- .vecs
20000400 20000400 0001b528 00000000 rw-
20000400 20000400 0001a588 00000000 rw- .bss
2001a988 2001a988 00000ba0 00000000 rw- .data
2001b528 2001b528 00000400 00000000 rw- .stack

Is there now a new method of setting resetVecsor is there a bug with this latest release of TIRTOS?

over 11 years ago

0 Emmanuel Trinidad - Alicea over 11 years ago

TI__Genius 10260 points

Hi Barry,

For TI-RTOS 2.0 the platforms have been moved out of XDCTools and into SYS/BIOS. As part of this change, the resetVecs should now be modified through SYS/BIOS; particularly, the device specific Hwi module in the config file (.cfg). Please see the code below:

// Import the device specific Hwi module
var m3Hwi = xdc.useModule('ti.sysbios.family.arm.m3.Hwi');
m3Hwi.resetVectorAddress = 0x20010000;  // New address

Regards,

-- Emmanuel

0 Barry Andrews over 11 years ago in reply to Emmanuel Trinidad - Alicea

Genius 3460 points

Thanks

That fixed the issue

Is there any document that explains these changes?

Also I take it the m3Hwi.resetVectorAddress must be set to an absolute value and not to a segment name like was previously done

0 Emmanuel Trinidad - Alicea over 11 years ago in reply to Barry Andrews

TI__Genius 10260 points

Hi Barry,

Please see the SYS/BIOS & XDCtools release notes.

Yes, the resetVectorAddress should be an absolute value.

Thanks,

-- Emmanuel

Processors

Processors forum

resetVecs no longer moves correctly with tirtos_tivac_2_00_01_23