• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 311 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.

TMS320C6748: LCDK won't flash larger sections of code, works in debugger.

Tyler Turcotte
Prodigy 240 points

Part Number: TMS320C6748
Other Parts Discussed in Thread: OMAP-L138

Good Morning,

I've been working code for quite a while and have been able to flash the code to my LCDK using the AISGen Tool that is in the starterware toolkit.  Recently I've added another section of code to my DSP and it has ran perfectly in the debugger.  However, now when I flash it to the DSP using flash_writer it claims to have flashed successfully but my program does not run.  I've gone back to test older variants of code and the DSP is flashed with those piece of code just fine.

Is there a size limit to what can be flashed?  I've put all of my code in DDR2 memory so memory allocation shouldn't be an issue.

I'm using starterware version: C6748_StarterWare_1_20_04_01

AISGen Tool: D800K008 Version 1.9

To me it almost seems like the boot loader isn't working correctly. I haven't changed any of the configuration files though. I just find it very odd that it would work fine in the debugger but not be flashed properly.

I've tried to reduce some of my vector lengths to see if that was an issue and nothings resolved.

  • 0
    TI__Mastermind 27355 points

    Hello Tyler,

    There was a similar issue that was resolved in the following thread, could you please see if the solution presented there helps with your issue?

    https://e2e.ti.com/support/processors/f/791/t/698573

    I'm also attaching some resources below that may be helpful.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/2543.Booting_5F00_from_5F00_flash.pdf

    https://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138

    OMAPL138/C6748 ROM Bootloader Resources and FAQ

    Regards,
    Sahin

  • 0 in reply to Sahin Okur
    Prodigy 240 points

    I've investigated these and they haven't resulted in a solution.  There are many different and badly documented TI documents that demonstrate too many contradicting statements pending OMAP-L138 or LCDK.

    Normally I use the flash_writer program built into Starterware.  This has been working up to this point, and has been the only thing that has worked. I flash using SPI0 (00001010) and Boot the NAND at NAND 8 (00001110).  This is done by utilizing the SFH utility located in the starterware.

    From the previous post you provided he is trying to use UART to flash his software.  Unfortunately, when I built the flash utility and attempted to flash I get no BOOT-ME from the UART configuration. (00010100)  So therefore, I wouldn't be able to flash using UART.  I've tried reflashing the NAND using u-boot-omapl138-lcdk.ais.  However, this hasn't changed anything, nor does it give the result stated in the README once you reset it to nand and monitor the serial output.

    Playing these guessing games is unacceptable.

    It is my understanding that the bootloader will be placed in L2 memory according to posts and documentation, which is 256kB and my CMD file is set at

        CACHE_L2RAM: o = 0x1180400, l = 0x3FC00

    as recommended in the above sample.

    If my .ais Bootloader file developed by AISgen tool is 532kb and runs just fine, how does it if fit in L2?  My new AIS file is now 844kB.

    A clear cut method of flashing or problem resolution would be greatly appreciated.

  • 0 in reply to Tyler Turcotte
    TI__Mastermind 27355 points

    Can you confirm you are erasing the NAND before flashing? Also, if it is NAND boot on LCDK then it uses NAND 16 and not NAND 8.

    Can you please share the command line arguments used with SFH so we can confirm it matches the hardware configuration of the platform? 

    Even if ROM uses RAM when loading the image, the image is loaded in one page (2K) at a time so it shouldn't be an issue, we've tested boot images that were larger (in MBs). 

    Also, can you please run the debug GEL file after ROM boot fails and post the output here? 

    Instructions on running the debug GEL file can be found in section 4 "Debugging Bootloader" of the following application note.

    OMAPL138/C6748 ROM Bootloader Resources and FAQ

    The debug GEL file is located in the CCS directory at ~\ccs_base\emulation\boards\lcdkc6748\gel\C674x_debug.gel

    Regards,
    Sahin

    Also, if it is NAND boot on LCDK then it uses NAND 16 and not NAND 8