I have followed the tutorial at http://designsomething.org/leopardboard/f/22/p/103/178.aspx#178 and I got hung up on the make installbootloader command. When I run it using the serial port I get:
wsn329@WSN329-3:/opt/DM355SDK789311$ sudo make installbootloader Ridgerun Linux SDK Board configuration: Leopard Board 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: *** [installbootloader] Error 255
I somehow managed to get this working once after receiving this message many times, but when I can't reproduce my results. The reason I tried again was because after I successfully loaded the bootloader I tried minicom and it didn't show anything (I think it is because it was accessing a different port, not ttyS0, which I changed). If I try doing it over the USB port I get this error:
wsn329@WSN329-3:/opt/DM355SDK789311$ sudo make installbootloader Ridgerun Linux SDK Board configuration: Leopard Board Installation system of uboot images over USB DFU Please disconnect and reconnect the USB cable from your board Press return to continue... Please be sure u-boot is running on port /dev/usbmon4 and none process (like minicom) is using it u-boot port /dev/usbmon4 Performing handshake with u-boot...stty: /dev/usbmon4: Inappropriate ioctl for device ERROR: failed to perform handshake with u-boot. Be sure u-boot is active on port /dev/usbmon4 and you have terminal programs like minicom closed.Exit: -1make: *** [installbootloader] Error 255
Any help as to why I cant load the bootloader onto the Leopard Board?
Have you verified that your board is on the uboot prompt?
When you open a program like minicom to communicate with your board, you should see the uboot prompt that looks like this:
If not, reset your board and make sure the board is on this prompt.
Embedded Software Engineer, RidgeRun
I was also wondering what the settings should be on the host computer (Linux or Windows) regarding the network IP address, etc. ?
It seems that my board does not connect to the Leopard Board through Ethernet (it says "no connectivity, cable disconnected")...
I have also not been able to install the boot loader. But I have been able to verify the u-boot prompt through a USB to Serial port. The things I had to figure out include:
doing "sudo chmod a+rw /dev/ttyUSB0",
running minicom -s to change the serial port it uses, the buad rate, etc, then save to dfl (default)
editing the minicom config file, ~/.minirc.dfl, to turn off modem initialization by adding the following lines:
so run minicom and press the reset button of the leopard board press enter when prompted to prevent
booting to linux. When you see a prompt like "Leopard 365", you are running uBoot on the board, exit
minicom (using the obvious command ctrl-a, q).
I think you also need to type "export PORT=/dev/ttyUSB0" so the script also knows to use the different port.
I got that part working but I was trying to use tftp and the build script did not copy the image files to /srv/tftp.
Does anybody know what files should be in that directory?
I'm new, and french, so sorry for my bad English but it would be nice if somebody answer me.
I received the LeopardBoard 365 last week, and have installed rigde run sdk. I have no problem to compile (make) but I can't install (make install or make installbootloader).
I want use the UART port. So I configurate it with (make config) and set the switch on the board at 011 (UART boot). When I do "make install" I have the same error than adriendude06. I don't understand why. Moreover, when I open minicom (on dev/ttyS0 and rate of flow: 115200 8N1) I can read BOOTME BOOTME BOOTME ...
youu want to see the uboot bootloader prompt, not BOOTME. Put the switches back, power the board on, and using your favorite terminal emulator (e.g. picocom -b 115200 -r -l /dev/ttyUSB2) verify you see the uboot prompt - something like
then exit the terminal emulator and run
I must necessary connect the USB between the board and the PC?
Serial cable is used for 'make install' (along with tftp networking depending on your configuration). I power the board with external power supply instead of using USB for power. So if you are using an external power supply, you don't need USB cable.
Also, if you run into problem, run
make install VERBOSE=1
and include the output when asking for assistance.
Thank you for your help.
I have do that: Put the switches back, power the board on, and using your favorite terminal emulator(e.g. picocom -b 115200 -r -l /dev/ttyS0) but on dev/ttyS0 and not dev/ttyUSB2 and I have this:
picocom -b 115200 -r -l /dev/ttyS0
port is : /dev/ttyS0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
noinit is : no
noreset is : yes
nolock is : yes
send_cmd is : ascii_xfr -s -v -l10
receive_cmd is : rz -vv
T WARN: emac_send_packet: No link
WARN: emac_send_packet: No link
and about make install VERBOSE=1 I have always the same problem:
Ridgerun Linux SDK
Board configuration: Leopard Board DM365
echo -e "\040" Installation system of uboot images over serial port "/dev/ttyS0"
Installation system of uboot images over serial port /dev/ttyS0
echo -e "\040" Please be sure u-boot is running on port "/dev/ttyS0" and none process \(like minicom\) is using it
Please be sure u-boot is running on port /dev/ttyS0 and none process (like minicom) is using it
if [ -n "`lsof -t "/dev/ttyS0"`" ] ; then \
echo -e "\040" "\033[31mError: u-boot "/dev/ttyS0" port in use\033[0m\n"; \
lsof "/dev/ttyS0"; \
exit -1; \
echo -e "\040" "u-boot port "/dev/ttyS0"\n"; \
u-boot port /dev/ttyS0
cd /home/stephane/DM365SDK844703/installer/u-boot-installer/ ; perl installer all
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.
make: *** [install] Erreur 255
I still didn't see the uboot prompt, please get back into picocom and press enter a few time and paste the output please.
Yes: the problem is that I have not the uboot prompt: Here is the result with picocom:
Retry count exceeded; starting again
TFTP from server 192.168.0.162; our IP address is 192.168.0.100
Load address: 0x80700000
Loading: WARN: emac_send_packet: No link
Thank you for your patience
I still don't see the uboot prompt. That is why the installer tool can not get into sync with uboot (that is what is meant by "failed to perform handshake with u-boot.") The installer first sends a simple echo command to uboot and expects the echo response. If no echo response is received, it stops with the failed to perform handshake with u-boot message.
The No link means you are not connected to a live network port. You are in the middle of a tftp download when the network seems to be down.
With picocom active, power cycle the board, press return a few times to verify uboot is alive, and paste the output. Then exit picocom and run 'make install VERBOSE=1' and paste that output too.
I have just power cycle when pipocom is active and obtain: I don't see any changements when I press return. Is it normal?
�DM36x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Jumping to entry point at 0x81080000.
U-Boot 1.3.4-svn21 (Feb 24 2010 - 10:04:27)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot: 0
I have to go (I'm an interned). Can I keep your mail-address ?
You have autoboot enabled.
You need to press Enter key before the the countdown at 'Hit any key to stop autoboot: 0 ' reaches zero.
I don't understand, I can't stop autoboot, I try with several key (included Enter) but no change whereas it says "Hit any key to stop autoboot",