Actions
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 354 subscribers
  • Views 832 views
  • Users 0 members are here
Related

Ultrazed "production" SOM doesn't boot

sonictai

Hello,

We've just received and powered on our brand new Ultrazed SOM, with "production" chips. But they don't boot, well they don't boot all the time...

We get some SD card access errors as SDHCI_send_command error.

Are there any differences between the ES1 and Production SOM, except for the Ethernet Phy Address that we already changed?

I saw on the SOM that the POR_OVERRIDE pull up/pull down resistors weren't in the same configuration. This remark is true looking at the broads, not at the schematics which are identical!?

May it have something to do with my boot difficulties?

Regards, Christophe

Parents
  • 0

    Hello Josh, Thank you for your response.

    Yes we're using our own LINUX on our own hardware so it seems difficult to test the factory Linux as you proposed.

    Actually there are two errors :

    The SDHCI_send_command as mentioned earlier, and the system that do not see the file system (that is located in our system on the SD card), so cannot boot.

    We've followed our tests and here are the last results :

    •   Adding the option "rootdelay = 2" in LINUX allows us to wait for 2 additional seconds. Then the system always see the file system and can boot,
    •   But we still have the SDHCI_send_command error! Is this error important because we saw it in the XILINX WIKI page dealing with the SD CARD controller...

    The impact of the rootdelay option tends to indicate that we're having a problem of timing during the boot sequence. Does it have something to do with the POR_OVERRIDE strap that I mentioned earlier? I could do the hardware modification changing the strap position on the Ultrazed but, well, even if I not bad at soldering, I'd preferred not to do it...

    Christophe

Reply
  • 0

    Hello Josh, Thank you for your response.

    Yes we're using our own LINUX on our own hardware so it seems difficult to test the factory Linux as you proposed.

    Actually there are two errors :

    The SDHCI_send_command as mentioned earlier, and the system that do not see the file system (that is located in our system on the SD card), so cannot boot.

    We've followed our tests and here are the last results :

    •   Adding the option "rootdelay = 2" in LINUX allows us to wait for 2 additional seconds. Then the system always see the file system and can boot,
    •   But we still have the SDHCI_send_command error! Is this error important because we saw it in the XILINX WIKI page dealing with the SD CARD controller...

    The impact of the rootdelay option tends to indicate that we're having a problem of timing during the boot sequence. Does it have something to do with the POR_OVERRIDE strap that I mentioned earlier? I could do the hardware modification changing the strap position on the Ultrazed but, well, even if I not bad at soldering, I'd preferred not to do it...

    Christophe

Children
No Data