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.

UART Boot Host Issues

Hi everyone,

I changed and combined few examples to one working in debug mode but attempt to run this using UART Boot Host failed. Another example ( also usage of McASP ) working in Debug mode works fine with UART2 using AIS Image. First thought was to tailor cmd file. Using the same cmd file from working example doesn;t help. Is it possible something else then cmd file is causing the trouble or should I try working on cmd files some more?

  • You may need to describe more clear what happened.

    Do the AIS image download failed? then it will report some failure message on UART boot Host program.

    Does program hang after download? You can check which code make it hangs by JTAG or you can simply send out data via UART if not in debug mode.

  • There is no problem to download Image. Everything is like it supposed to be. I comment a source code of McASP elements and add some blinking LEDs using interrupts. In debug mode it works fine. Just after download process using UART2  there is no blinking. It probably doesn't get to main() function ( But I have no idea how to check this).

    How Can I check where it hangs when I dowload AIS Image?

  • You may check Pinmux & AISGen configuration. It may help.

    Do power control, PLL configure as you expected.

    See map file to check the program location as you expected. For example, Improper DRAM configuration & program download into DRAM area, it may fail. If PSC not turn on, the peripheral will not work.

  • To be precise about source code, I'm using mcasp example from wiki: http://processors.wiki.ti.com/index.php/QuickStartOMAPL1x_rCSL

  • I found problem: It stucked in while loop when checking if there is another transition in progress:

    //Stall until both PSC domains are not in trasition
       /while(((CSL_FEXT(psc0Regs->PTSTAT, PSC_PTSTAT_GOSTAT0)==CSL_PSC_PTSTAT_GOSTAT0_NO_TRANSITION) && (CSL_FEXT(psc0Regs->PTSTAT, PSC_PTSTAT_GOSTAT1)==CSL_PSC_PTSTAT_GOSTAT0_NO_TRANSITION)));


  • Any idea why it's sticking there?  Did you figure out a solution yet, or are you waiting for someone to suggest something?  If it only happens in release mode perhaps a timing problem is created by turning on the C optimizer.  You can right-click on that file and choose file specific compiler options (i.e. no optimization) to see if that resolves the issue.  If that does resolve the issue, there might be a bug in that code (or even the compiler) that we need to fix.

  • I did solve this by using macro from another library packet. It works fine. Now I have jet another issue but think I should post another thread to be alonge with regulations of this forum.

  • Yes, please start a new thread for a new issue. I'm curious to see your updated code snippet that fixed the issue if you're willing to share. What library did it come from?