I have a 6418 BIOS-based project which runs fine when using the JTAG
emulator. Now I am moving the project from the emulator to a
standalone project with HPI Host Boot from my ARM processor. I've
finally figured out how to get hex6x to produce the image file I need
for this, using spru186p, SPRAA64 and hints about the undocumented -b
option from TI.
But the documentation for standalone BIOS, especially initialization
without GEL files, is scattered and unclear. I've gone through the
BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
spra964, spra772a, spra743, spra544d, with glances at a dozen others.
Advice and/or pointers to other documents I may have missed would be
appreciated.
BIOS project moving from emulator to standalone HPI Host Boot
Started by ●July 17, 2008
Reply by ●July 17, 20082008-07-17
casner,
On Thu, Jul 17, 2008 at 7:16 AM, casner wrote:
> I have a 6418 BIOS-based project which runs fine when using the JTAG
> emulator. Now I am moving the project from the emulator to a
> standalone project with HPI Host Boot from my ARM processor. I've
> finally figured out how to get hex6x to produce the image file I need
> for this, using spru186p, SPRAA64 and hints about the undocumented -b
> option from TI.
>
> But the documentation for standalone BIOS, especially initialization
> without GEL files, is scattered and unclear. I've gone through the
> BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
> spra964, spra772a, spra743, spra544d, with glances at a dozen others.
>
> Advice and/or pointers to other documents I may have missed would be
> appreciated.
I am not sure about particular docs, but you might try to get it
working with the emulator using no GEL files.
Strategy - make a copy of the GEL file[s] and incrementally work to
whittle them down to 0.
1. Get rid of any optional/unused code.
2. Get rid of the 'memory map' stuff.
3. Add any device initialization stuff to your code and get rid of it.
4. Make sure that you can run from the reset vector.
5. Make sure that you can download load code from the emulator without
using any GEL files and run it from the reset vector.
6. Package it to be downloaded from the ARM.
7. If it doesn't work when downloaded, have the ARM download it but do
not have it issue DSPINT.
8. With CCS, download the 'symbols only' [does not affect target] and
set the PC to the reset vector.
9. You should be able to step from there or set incremental
breakpoints, depending on your debug style.
mikedunn
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
On Thu, Jul 17, 2008 at 7:16 AM, casner wrote:
> I have a 6418 BIOS-based project which runs fine when using the JTAG
> emulator. Now I am moving the project from the emulator to a
> standalone project with HPI Host Boot from my ARM processor. I've
> finally figured out how to get hex6x to produce the image file I need
> for this, using spru186p, SPRAA64 and hints about the undocumented -b
> option from TI.
>
> But the documentation for standalone BIOS, especially initialization
> without GEL files, is scattered and unclear. I've gone through the
> BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
> spra964, spra772a, spra743, spra544d, with glances at a dozen others.
>
> Advice and/or pointers to other documents I may have missed would be
> appreciated.
I am not sure about particular docs, but you might try to get it
working with the emulator using no GEL files.
Strategy - make a copy of the GEL file[s] and incrementally work to
whittle them down to 0.
1. Get rid of any optional/unused code.
2. Get rid of the 'memory map' stuff.
3. Add any device initialization stuff to your code and get rid of it.
4. Make sure that you can run from the reset vector.
5. Make sure that you can download load code from the emulator without
using any GEL files and run it from the reset vector.
6. Package it to be downloaded from the ARM.
7. If it doesn't work when downloaded, have the ARM download it but do
not have it issue DSPINT.
8. With CCS, download the 'symbols only' [does not affect target] and
set the PC to the reset vector.
9. You should be able to step from there or set incremental
breakpoints, depending on your debug style.
mikedunn
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Reply by ●July 17, 20082008-07-17
I forgot to mention in my original post: We eliminated the GEL files, and
incorporated the necessary EMIF initialization from there into the user_init
called by the bios before it calls _main.
I have a 6418 BIOS-based project which runs fine when using the JTAG
>emulator. Now I am moving the project from the emulator to a
>standalone project with HPI Host Boot from my ARM processor. I've
>finally figured out how to get hex6x to produce the image file I need
>for this, using spru186p, SPRAA64 and hints about the undocumented -b
>option from TI.
>
>But the documentation for standalone BIOS, especially initialization
>without GEL files, is scattered and unclear. I've gone through the
>BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
>spra964, spra772a, spra743, spra544d, with glances at a dozen others.
>
>Advice and/or pointers to other documents I may have missed would be
>appreciated.
I have a 6418 BIOS-based project which runs fine when using the JTAG
>emulator. Now I am moving the project from the emulator to a
>standalone project with HPI Host Boot from my ARM processor. I've
>finally figured out how to get hex6x to produce the image file I need
>for this, using spru186p, SPRAA64 and hints about the undocumented -b
>option from TI.
>
>But the documentation for standalone BIOS, especially initialization
>without GEL files, is scattered and unclear. I've gone through the
>BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
>spra964, spra772a, spra743, spra544d, with glances at a dozen others.
>
>Advice and/or pointers to other documents I may have missed would be
>appreciated.
Reply by ●July 17, 20082008-07-17
casner,
On Thu, Jul 17, 2008 at 3:59 PM, wrote:
> I forgot to mention in my original post: We eliminated the GEL files, and
> incorporated the necessary EMIF initialization from there into the user_init
> called by the bios before it calls _main.
1. Have you checked your 'download recipe' but downloading a simple
'LED blinky' program or something similar??
2. Do you know if you are 'downloading what you think you are
downloading'?? [ie, the correct memory image]
2A. You can load a small program via CCS [zero memory first] and do a
'data save'
2B. Zero memory
2C. Download via HPI [don't run] and do a mem save from CCS.
2D. Diff the 2 text files
The top HPI boot problems [IMO]
1. no branch at reset vector
2. some initialization missing
3. downloaded code doesn't match '.out' file.
mikedunn
>
> I have a 6418 BIOS-based project which runs fine when using the JTAG
>>emulator. Now I am moving the project from the emulator to a
>>standalone project with HPI Host Boot from my ARM processor. I've
>>finally figured out how to get hex6x to produce the image file I need
>>for this, using spru186p, SPRAA64 and hints about the undocumented -b
>>option from TI.
>>
>>But the documentation for standalone BIOS, especially initialization
>>without GEL files, is scattered and unclear. I've gone through the
>>BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
>>spra964, spra772a, spra743, spra544d, with glances at a dozen others.
>>
>>Advice and/or pointers to other documents I may have missed would be
>>appreciated.
>
>>
>
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
On Thu, Jul 17, 2008 at 3:59 PM, wrote:
> I forgot to mention in my original post: We eliminated the GEL files, and
> incorporated the necessary EMIF initialization from there into the user_init
> called by the bios before it calls _main.
1. Have you checked your 'download recipe' but downloading a simple
'LED blinky' program or something similar??
2. Do you know if you are 'downloading what you think you are
downloading'?? [ie, the correct memory image]
2A. You can load a small program via CCS [zero memory first] and do a
'data save'
2B. Zero memory
2C. Download via HPI [don't run] and do a mem save from CCS.
2D. Diff the 2 text files
The top HPI boot problems [IMO]
1. no branch at reset vector
2. some initialization missing
3. downloaded code doesn't match '.out' file.
mikedunn
>
> I have a 6418 BIOS-based project which runs fine when using the JTAG
>>emulator. Now I am moving the project from the emulator to a
>>standalone project with HPI Host Boot from my ARM processor. I've
>>finally figured out how to get hex6x to produce the image file I need
>>for this, using spru186p, SPRAA64 and hints about the undocumented -b
>>option from TI.
>>
>>But the documentation for standalone BIOS, especially initialization
>>without GEL files, is scattered and unclear. I've gone through the
>>BIOS class manual, and spra999, spra512, spru578c, spraa74a, spra978,
>>spra964, spra772a, spra743, spra544d, with glances at a dozen others.
>>
>>Advice and/or pointers to other documents I may have missed would be
>>appreciated.
>
>>
>
--
www.dsprelated.com/blogs-1/nf/Mike_Dunn.php
Reply by ●July 18, 20082008-07-18
hi
I have a EVM6437 board and want to have some image processing experiences by it. when I run the loopback example that was on the DVD it capture the images from video encoder in CbYCr format. Imean they are interleaved. In DM642 board I could configure to have them seperately. because I want to process just the Y component . Now I have to copy the Y component to other place and process it and then copy back it to the original place.
Is it possible to configure the CCDC module of VPFE peripheral to save the components of the image in 3 different places I mean the Y and Cb and Cr save in three different places of the memory. Now they are interleaved.
Thanks
Yasser
I have a EVM6437 board and want to have some image processing experiences by it. when I run the loopback example that was on the DVD it capture the images from video encoder in CbYCr format. Imean they are interleaved. In DM642 board I could configure to have them seperately. because I want to process just the Y component . Now I have to copy the Y component to other place and process it and then copy back it to the original place.
Is it possible to configure the CCDC module of VPFE peripheral to save the components of the image in 3 different places I mean the Y and Cb and Cr save in three different places of the memory. Now they are interleaved.
Thanks
Yasser
