• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 375 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.

TMDSIDK437X: AM437x IDK - Unable to boot from SD card using default sdk image or via tftp/NFS method

James Shealy
Prodigy 60 points
Part Number: TMDSIDK437X

Intro

I am working with the AM437x IDK board using the Linux-RT devkit as a reference, and with the the mainline branch of Yocto Linux + Meta-TI and its dependencies in parallel since I require a fairly customized image for my end goals.

My setup is as follows: A host PC connected to a wired network via an ethernet switch with the IDK board connected to the same switch. The serial over USB port on the IDK is connected to a USB port on the host PC.

SDK version: v06.03  

Detailed description of issue

I am unable to boot the AM437 using:

  • The default SDK image on an SD card created using the provided create-sdcard.sh
  • A core-image-base image I generated for an am437-evm target. I imaged the SD card using the provided create-sdcard.sh and pointing it toward the boot and rootfs partitions
  • The above using the Linux-RT SDK's provided setup.sh routine (so booting via tftp + NFS is not working either)
  • Key symptom: no output from the serial console via serial over usb cable

I have tried this on:

  • The recommended Ubuntu 18.04 LTS host system.
  • Arch Linux (I patched the sdk setup scripts to support this) when Ubuntu did not work since I am familiar with it and wanted to make sure nothing was wrong on the host end of things. I have triple checked my NFS and tftp configurations for this host system and am confident in them.

Other things I have tried:

  • Swapping the ethernet cable and USB 2.0 type A to micro USB type B cable for known good cables
  • Using a AM335x development board I also have with its corresponding SDK - this board booted using its default SDK image - this seems to rule out any cabling cor connection issues
  • Made sure no driver or userspace issues (permissions, groups, udev rules, etc) were preventing a serial connection

Other info/thoughts that may be of use:

  • The IDK's power indicator and serial connection indicator LEDs light up
  • The indicator lights on the ethernet RJ45 jack appear to indicate some type of signaling is active when connected to the host system via an ethernet switch
  • My first guess was that I messed something up with Yocto, but in that case the default SDK image should have booted

My Questions

  1. What sorts of problems have I overlooked that could be causing this behavior?

  2. Is it possible that the board itself is bad considering that my AM335x board works?

Any assistance is much appreciated,

James

  • 0
    TI__Guru** 102120 points

    Hello James,

    Are you able to boot using the SD card that came packaged with the board? Have you made any modifications to the board?

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Prodigy 60 points

    Nick,

    No to both. I have also inspected the board and found no visible signs of damage, corrosion, or detached components. I should have also noted in the original post that I am able to see the serial over usb interfaces as /dev/ttyUSB0 and /dev/ttyUSB1. They both when read yield no indication that the AM437 is booting or attempting to boot (no u-boot prompt, etc).

    -James