Hey,
I'm new, French, so sorry for my bad English, but it would be nice if somebody answer me as soon as possible.
I received last week the Leopard 365 Board, and I have installed Ridge Run SDK. After a lot of problems with the compilation that I succeed to solve, the "make" run, but when I do "make install" or "make installbootloader" or "make installkernel" I have a problem:
I want to use the UART port, so I configure it in the "make config" ,I choose 011(UART boot) on the switch of the board, and I connect the board to the PC via the serial port. But when I do "make install" I have this error:
Ridgerun Linux SDK Board configuration: Leopard Board DM365 Installation system of uboot images over serial port /dev/ttyS0 Please be sure u-boot is running on port /dev/ttyS0 and none process (like minicom) is using it u-boot port /dev/ttyS0 Performing handshake with u-boot... ERROR: failed to perform handshake with u-boot. Be sure u-boot is active on port /dev/ttyS0 and you have terminal programs like minicom closed.Exit: -1make: *** [install] Erreur 255
I don't understand why. Moreover, when I open minicom (on dev/ttyS0 and rate of flow: 115200) I can just read: BOOTME BOOTME BOOTME BOOTME...
When I do "reset" on the board, it makes no change.
Do you have any idea to resolve my problem?
Hello Aurelie,
You are most likely receiving that error because you have your jumpers set to 011 - the board is waiting to be booted via mono(monoxide). At least - that's what I read in this guide to "Recovering a Bricked Leopardboard"--> designsomething.org/.../97.aspx
If you login to the board over the serial connection using Putty, minicom, etc., return the jumpers to 000 and reboot the board, you should see the normal U-boot loading process occur on your terminal. Interrupt the "Automatic Loading process" - just hit any key before the countdown finishes - and you will be placed at the Leopardboard 365> prompt. Close whatever serial connection you are using (Putty, minicom, etc) and then run the "make install" command from the RR SDK directory. You should see the U-boot handshake complete sucessfully, and load the appropriate data over serial.
It has been mentioned on this board, but not rectified as far as I know, to NOT USE "make installbootloader" on the Leo 365, or you WILL brick the board. As far as I know, and from any documentation I can find, the default U-boot Utilities provided with the SDK do not communicate properly with the Leo: if you HAVE bricked the board, there is a second SD-card Flashing utility listed in the same thread I linked above, that should help you to recover the board.
**Note, use a REGULAR SD card for the SD flashing procedure, Leo365 does NOT support SDHC type cards and the init process simply fails/hangs with no warning.
Hope that helps!!
-Ian
Thank you for your help.
But I have a problem: I can't stop the autoboot, I tried with several key, but no change whereas it says "hit any key to stop autoboot" so I haven't the prompt.
Hi,
I have seen that problem before due to incorrect settings on your serial connection (Most common: hardware flow control enabled). Please verify your settings on the following link:
processors.wiki.ti.com/.../Beginners_guide
Cristina Murillo
Embedded Software Engineer, RidgeRun
Thank you to answer me
I don't know what to do.
I think I have the good configuration : flow: 115200 8N1, flow control: none(hard and soft), ttyS0.
I can't have the u-boot prompt. It's as if uboot don't respond to my keyboard inputs.
I have seen that if we put "bootdelay" at -1, it disables autoboot.
Is there an other solution?
I've just solved my problem: It was due to my serail port (my serial port doesn't run: no data out)
So, I have used a serial port adaptor USB and it works!!
Great! Always important to check if the port is working! :)