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.

66AK2H06: UART boot

Part Number: 66AK2H06

Hi,

Customer wants to check UART boot function with 66AK2H06.
They refer to below documents.

http://www.ti.com/lit/an/spracn3/spracn3.pdf

http://www.ti.com/lit/ug/spruhj3/spruhj3.pdf

Questions:
1) Which UART pins are used, UART0 or UART1?
2) Section 8.4.5 mentions uartImage.dat, uartStage1.dat and uartStatge2.dat, but there is no such files.
The uartImage1.bin is the correct file name?



Thanks and regards,
Koichiro Tashiro

  • Hi,

    I looked at the http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_Foundational_Components.html#k2h-k2e-k2l. There is no mentioning the UART boot on K2H device.

    The UART boot described in http://www.ti.com/lit/an/spracn3/spracn3.pdf is very new. Let me check how this package is maintained and tested.

    Regards, Eric

  • Tashiro-san,

    UART boot examples in the KS2 Bootloader application notes were created and validated using K2H EVM which uses UART instance 0. The UART instance used for initlal ROM boot is also guided by the BOOTMODE pin settings that can be read from DEVSTAT register. 

    The file name for the UART boot images seem to not match with the prebuilt binaries. the correct file names for multi-stage boot are uartImage1.bin and uartImageStage2.bin and for single stage boot is uart_data.bin.

    If you open the makefile in the following path, you can see the target names match the file names that I have mentioned and found in the package:

    Keystone_boot-examples\examples\k2h\uart\singleStage

    Keystone_boot-examples\examples\k2h\uart\multiStage

    I will file a litbug to fix the file names.

    Regards,

    Rahul

  • Hi Rahul,

    Thanks for your detailed reply.

    Customer tested the prebuild files for mult-stage boot (uartImage1.bin and uartImageStage2.bin) on EVMK2H and it works fine.
    Here is terminal output.


    But when same images are used on the customer board, the terminal output is corrupted.


    BOOTMODE[15:0] configuration used on the customer board is below.


    Is this the same configuration when EVMK2H is configured UART boot (SW1 off, on, off, off)?



    Thanks and regards,
    Koichiro Tashiro