OSD3358-512M-BAS Boot Question

Tagged: OSD335x-BAS boot question

This topic has 3 replies, 3 voices, and was last updated 1 month, 1 week ago by Neeraj Dantu.

Viewing 3 reply threads

Author
Posts
- October 8, 2024 at 3:44 am #15222
  Dong David
  Participant
  We made a demo based on the Beaglebone Black wireless development board. The PCB diagram is exactly the same as the development board, but there is an issue:
  1. U-boot cannot start. Attached is the information printed during startup, and above the red line is the log printed by our circuit board. Below the red line is the normal startup information printed by the Beaglebone Black Wireless development board.
  2. Our circuit board cannot run after SDRAM initialization. Is there a need to make other configurations for the new chip during SDRAM initialization? Now I want to pinpoint where the problem lies and find a solution. thank you.
  Attachments:
  log.webp
- October 8, 2024 at 3:49 am #15224
  Dong David
  Participant
  Chip?OSD3358-512M-BAS-XB
  Attachments:
  OSD3358-CHIP.jpg
- October 11, 2024 at 2:28 pm #15232
  Alexio Velazquez
  Participant
  The system seems to stop right before calling board_init_f. Early_board_init succeeds
- October 11, 2024 at 3:50 pm #15233
  Neeraj Dantu
  Moderator
  Alexio,
  Do you mean early_system_init() here: https://github.com/u-boot/u-boot/blob/master/arch/arm/mach-omap2/am33xx/board.c#L504 ?. If you are referring to this location, this is SPL still running out of AM335x internal SRAM. sdram_init() is called after board_early_init_f().
  In addition to the inputs on the other thread, another thing to try is using Starterware for AM335x here: https://www.ti.com/tool/download/STARTERWARE-AM335X/02.00.01.01. You can use code composer studio(CCS) to run baremetal example applications via JTAG as another avenue for debug. One step further is debugging SPL in CCS: https://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components/U-Boot/Apps-SPL-Debug.html.
  Best,
  Neeraj
Author
Posts