• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 213 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Debug Bootcode using CCS Simulator

Bernhard Fuchs
Intellectual 320 points

I´m starting to develop the bootcode for a c6727 EVM and came accross some questions which i was not able to clarify.

 

After reset the PC is set to 0x00000000 -> This is a read only location where the first stage bootloader is located.

In case of a boot from parallel flash this loader copies the first 1kb of data located at 0x90000000 at location 0x10000000.

0x10000000  - 0x10000400 contains my boot.asm code which inits the pins, pll, emif

after init the application code gets copied

 

my first questions according to SPRAAS8: the bootloader at 0x0000 0000 uses internal ram at 0x10000000 to
0x10000FFF for saving status information and working variables.

But isn´t the information lost in case of a parallel flash boot? since the first possible entry point for me is the my own bootcode at 0x1000 0000.

Where should i store my interrupt vector table?

 

Is it possible to debug the code using the simulator? I am new to CCS and did not find a possible way to "emulate" this kind of boot process.

I would need the code of the ROM content and place it at 0x0000 0000 to simulate the first stage bootloader. Is this correct or does there exist an other solution?

 

kind regards

Bernhard

 

 

  • 0
    TI__Guru*** 125430 points

    Bernhard Fuchs said:
    my first questions according to SPRAAS8: the bootloader at 0x0000 0000 uses internal ram at 0x10000000 to
    0x10000FFF for saving status information and working variables.

    I cannot find that literature number.  The 6727 bootloader doc is spraa69.  According to this document the bootloader utilizes address range 0x10000400 - 0x10000FFF.  Therefore there is no conflict with your code residing in the first 1KB.  Furthermore, once your code begins executing it will never return to the ROM bootloader so from the time your code starts executing you no longer need to worry about preserving that address range (in the case of parallel flash boot).

    Bernhard Fuchs said:
    Is it possible to debug the code using the simulator? I am new to CCS and did not find a possible way to "emulate" this kind of boot process.

    I don't know how you would debug this on the simulator.  It will be much better on hardware.  Please refer to this wiki page:

    http://processors.wiki.ti.com/index.php/Debugging_from_Flash