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.

  • Resolved

Linux/AM4379: CUSTOM BOARD BOOT-UP

Expert 1255 points

Replies: 6

Views: 287

Part Number: AM4379

Tool/software: Linux

Hi All,

We have custom board with AM4379.

I succeed to boot up our board with following steps 

- Set SYS_BOOT pin for SD Card boot
- Plug Bootable SD Card to board
- Power up board
- Launch selected configuration (@UBUNTU-Host PC w/CCS)
- Connect Target CORTEX-A9 
- Load GEL File idk_am437x.gel (modified gel file . SK_IDK_EVM_DDR3_SDRAM_CONFIG value changed)
- Run initialization Script IDK_EVM
- CPU Reset ---> PC=0 
- Tools > Load Memory > u-boot.bin (@0x80800000 w/32bit)
- set PC to 0x80800000
- Resume

But, when i follow the https://training.ti.com/linux-board-porting-series-module-7-debugging-u-boot-jtag-ccs?cu=399066

- Set SYS_BOOT pin for SD Card boot
- Plug Bootable SD Card to board
- Power up board
-  Launch selected config
- Connect A9
-  Load GEL File idk_am437x.gel (modified gel file . SK_IDK_EVM_DDR3_SDRAM_CONFIG value changed)
-  Run initialization Script IDK_EVM
-  CPU Reset ---> PC=0
- Check CPSR - T value. Not thumb mode ! 
- Load Memory > u-boot-spl.bin > 0x402f4000. 
- Run > Load > Load Symbols > u-boot-spl 
- Set PC 0X402F4000
- Resume

@SerialOutputTerminal
U-Boot SPL 2018.01-00569-gf9c38b91a2-dirty (May 14 2019 - 11:47:55)
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

- Run > Load > Load Program > > u-boot
- Resume

 

After this with steps, board does not boot-up.

Code hang :

"bootstage_error(){Show_boot_stage_progress(-id)}"

What could be the reason for this ?

 

 

Best Regards,

Mehmet

 

  • ubuntu version -> 18.04.2
    sdk version -> ti-processor-sdk-linux-am437x-evm-05.03.00.07
    sd-card images (for windows host)-> am437x-evm-linux-05.02.00.10
  • In reply to Mehmet:

    Hello Mehmet,

    I do not recommended loading the GEL file while stepping through the SPL/Uboot code. If you have verified your DDR, please move the configuration to the Uboot. Also, if you refer to the AM437x TRM, you will notice the ram starts at address 0x40300000 instead of 0x402f4000.

    Regards,
    Krunal
  • In reply to Krunal Bhargav34:

    Hello Krunal,

    Thank you for your response.

    "I do not recommended loading the GEL file while stepping through the SPL/Uboot code. If you have verified your DDR, please move the configuration to the Uboot"
    In fact i don't want to use GEL File, but if i dont use initializing script of GEL File i cannot see anything on terminal. If i use initialize script i can see "SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### " message on serial terminal.
    I want to be sure. i shouldn't use GEL File right ? Is u-boot "board.c" file doing the same thing with GEL File? 

    "if you refer to the AM437x TRM, you will notice the ram starts at address 0x40300000 instead of 0x402f4000."
    I think ram starts at 0x402f4000. you can see @section 5.2.3.2 Public L3 RAM Memory Map" 
    And you can examine this post for RAM Start address https://e2e.ti.com/support/tools/ccs/f/81/t/779823?tisearch=e2e-quicksearch&keymatch=Trouble%20Writing%20Memory%20Block%20At%200x402F0400

    I'm waiting for your answer.

    Best Regards,
    Mehmet

  • In reply to Mehmet:

    Hello,

    Please help me TI.

    Thanks
  • In reply to Mehmet:

    Hi Mehmet,

    I apologize for the incorrect address and I verified the start address of ram at 0x402f4000 in the file u-boot-spl.map. Also, most of the changes for the DDR will take place in the <u-boot>/board/ti/am43xx/board.c file.

    Regards,
    Krunal
  • In reply to Krunal Bhargav34:

    The problem has not been resolved, but Thanks for the help

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.