Actions
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 355 subscribers
  • Views 1011 views
  • Users 0 members are here
Related

UltraZed EG not booting

xlmnsp

I am having some problems getting my UltraZed EG starter kit to boot. 

I've followed all of the quick start steps and inserted the supplied SD card. The fan is working.

 

After turning on the board, D10 on the carried board lights up and D15 on the carried board stays dark.

 

D4 on the SOM flashes and if the boot mode is set to SD, D3 on the SOM lights up continously. If the boot mode is set to one of the QSPI modes the SOM stays dark after the D4 flash. Except in some cases if I leave the board on for a while, D3 turns on.

 

Nothing shows up on the serial connection.

 

I hope this description helps with identifying the problem. I would greatly appreciate any help.

  • 0

    Hi there,

    Are you using Windows 10?
    If so, sometimes you will see multiple serial ports appearing.  Can you check your serial settings and ensure you are on the actual serial port?  FYI, both will have a port number assigned.  You can try the second port to see if this is the issue.

    Is your board a red or black?

    When set to SD mode, D3 indicates that there is something wrong with your SDCARD boot.bin.  You should attempt to copy a new one from the resources page.

    In come cases, the boot will time out if you have not accessed it and D3 can light.

    --Dan

  • 0 in reply to drozwood90

    Hi, thanks for the help,

    Yes I'm using Windows 10.

     

    Since I wasn't sure which serial connection was the correct one, I always had both connected at once. Now I also tried just being connected to one at a time. I also double checked the configuration in both Windows and PuTTY. Still nothing sadly.

     

    My board is black.

     

    I downloaded this file and copied its extracted contents to the root of my SD card http://www.ultrazed.org/sites/default/files/design/uz3eg_iocc_oob_plnx_2017_2.zip. This didn't change anything about the boot behavior.

  • 0

    Hi there,

    That was a good idea to try to connect both. Typically it is the HIGHER port number. For example, on my PC (running Windows 10), I have ports 5 and 6 for serial ports. 6 happens to be the one I need to use to see the terminal.

    Just a few more questions to help me understand, and I am sorry if they seem annoying or simple.
    *are you in fact using 115,200/8N1 for your serial terminal (we did not confirm this)?
    *are you using Tera Term?
    *can you look at your boot switch matrix and tell me what the switches are set to?
    The switch is labeled 1-4 and one side should say ON.

    For example, you can write it like this:
    1   2   3   4
    OFF ON  ON  ON

    NOTE: this configuration will boot from the built in QSPI, and load the factory loaded code (unless you have overwritten it).

    If you have NOT seen it, other boot configurations are in the SOM manual on page 32.

    For example, SDCARD Boot is:
    1   2   3   4
    OFF ON  OFF ON

    While we are gathering information, can you try the two above configurations? First, try the FIRST example Matrix setup.

    Next delete all files and folders from the included SDCARD.  Ensure it is the INCLUDED SDCARD.  If it is not, this could be your issue (see Storage Insights Article on Element 14).
    Next, extract ONLY the BOOT.BIN and image.ub to the SDCARD.  Place this in the Carrier Card and change the boot switch matrix configuration to the SDCARD boot.

    Power each on one at a time and please let me know what you see.

    --Dan

  • 0

    Hi there,

    One more thought.  With the POWER removed and the power switch set to OFF, you should also try to take the SOM off and reseat it into the carrier card.

    Ensure all connections are firm and the male and female sides are properly touching/seated.  Use firm and nor excessive pressure along each edge of the SOM that has a connector.

    *Note, when doing this, ensure you follow proper static protection methods, like with all electronics, ESD can cause damage to this board!

    --Dan

  • 0

    I had the same issues - until firm (not excessive) pressure was applied - though rather firm pressure was required.  Fully seated the top of the SOM is flush with the top of the jumper on JP1.  

    I jumpered JP1 per the Getting Started instrutions provided with the kit (received ~7/24/18).  Boot from QSPI gave me garbled output on the serial console (@115200 baud), but booting from SD with the latest out of box image downloaded from zedboard.org booted linux as expected.