Hello!
After compiling the sdk and running the uboot on the board(I see a prompt: Leopard 365) i enter make install and i get the following error:
ERROR: failed to perform handshake with u-boot.
It looks like this:
...
In: serial
Out: serial
Err: serial
Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot: 0
Leopard 365 :>
CTRL-A Z po pomoc |115200 8N1 | NOR | Minicom 2.3 | VT102 | Offline
maniek@maniek-laptop:~/DM365SDK844703$ make install
Ridgerun Linux SDK
Board configuration: Leopard Board DM365
Installation system of uboot images over TFTP for host 192.168.1.3
Please be sure u-boot is running on port /dev/ttyUSB0 and none process (like minicom) is using it
u-boot port /dev/ttyUSB0
Performing handshake with u-boot...
Be sure u-boot is active on port /dev/ttyUSB0 and you have terminal programs like minicom closed.
What can be an issue?
Marian
Hi Marian,
It looks like you are doing everything right. We need more detail to see what is going wrong.
The installer sent a command to u-boot and didn't get the response it was expecting.
There is a log of the serial transactions in $DEVDIR/logs/install.log
Please paste the log so I can see the details.
The most common explanation is your leo365 is not on port /dev/ttyUSB0. What is minicom configured for?
Todd
Did you try to choose "serial" as mean of installation in the Config menu whereas TFTP?
Hi Todd,
This is the configuration of minicom:
| A - Serial Device : /dev/ttyUSB0 || B - Lockfile Location : /var/lock || C - Callin Program : || D - Callout Program : || E - Bps/Par/Bits : 115200 8N1 || F - Hardware Flow Control : No || G - Software Flow Control : No || || Change which setting? |
In the log file I do not see any useful information. It contains the following lines:
--------------------------------------------------- Sat Jul 24 22:57:52 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:01:38 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:09:04 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:19:36 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:36:22 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:46:15 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:49:31 2010 ------------------------------------------------------------------------------------------------------- Sat Jul 24 23:49:57 2010 ----------------------------------------------------1˙--------------------------------------------------- Sat Jul 24 23:59:30 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 00:14:10 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 00:27:14 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 00:48:01 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 00:49:06 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 00:49:45 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 01:05:45 2010 ----------------------------------------------------1˙--------------------------------------------------- Sun Jul 25 01:06:31 2010 ------------------------------------------------------------------------------------------------------- Sun Jul 25 01:14:13 2010 ----------------------------------------------------
I also entered the command make install VERBOSE=1 and i got this reply:
maniek@maniek-laptop:~/DM365SDK844703$ make install VERBOSE=1 Ridgerun Linux SDK Board configuration: Leopard Board DM365 echo -e "#!/usr/bin/perl" > /home/maniek/DM365SDK844703/installer/u-boot-installer/installerecho -e "#This file is autogenerated by makefile, don't modify\n" >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installerecho "my \$DEVDIR = \"/home/maniek/DM365SDK844703\";" >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installerecho "my \$KERNEL = \"linux-2.6.18\";" >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installerecho "my \$TFTPIMGSUFIX = \".maniek.leopard\";" >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installerecho "my \$TIFLASHUTILSDIR = \"/home/maniek/DM365SDK844703/bootloader/u-boot-2009.11/ti-flash-utils-1.5\";" >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installerperl /home/maniek/DM365SDK844703/installer/u-boot-installer/bspconfigparser.pl \ /home/maniek/DM365SDK844703/bsp/mach/bspconfig \ >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installercat /home/maniek/DM365SDK844703/installer/u-boot-installer/u-boot-installer >> /home/maniek/DM365SDK844703/installer/u-boot-installer/installerchmod +x /home/maniek/DM365SDK844703/installer/u-boot-installer/installerecho -e "\040" Installation system of uboot images over TFTP for host Installation system of uboot images over TFTP for hostecho -e "\040" Please be sure u-boot is running on port "/dev/ttyUSB0" and none process \(like minicom\) is using it Please be sure u-boot is running on port /dev/ttyUSB0 and none process (like minicom) is using itif [ -n "`lsof -t "/dev/ttyUSB0"`" ] ; then \ echo -e "\040" "\033[31mError: u-boot "/dev/ttyUSB0" port in use\033[0m\n"; \ lsof "/dev/ttyUSB0"; \ exit -1; \ else \ echo -e "\040" "u-boot port "/dev/ttyUSB0"\n"; \ fi u-boot port /dev/ttyUSB0cd /home/maniek/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/ttyUSB0 and you have terminal programs like minicom closed.
Hi Aurelie,
I chose "serial" in the Config menu and i got the following reply:
Ethernet PHY: GENERIC @ 0x00 Hit any key to stop autoboot: 0 Leopard 365 :> Leopard 365 :> Leopard 365 :> CTRL-A Z po pomoc |115200 8N1 | NOR | Minicom 2.3 | VT102 | Offline maniek@maniek-laptop:~/DM365SDK844703$ make install Ridgerun Linux SDK Board configuration: Leopard Board DM365 Installation system of uboot images over serial port /dev/ttyUSB0 Please be sure u-boot is running on port /dev/ttyUSB0 and none process (like minicom) is using it u-boot port /dev/ttyUSB0 Performing handshake with u-boot... ERROR: failed to perform handshake with u-boot. Be sure u-boot is active on port /dev/ttyUSB0 and you have terminal programs like minicom closed.
Hello,
I did the entire installation again, and unfortunately I have the same error. How can I check what is wrong? Please some help.
You don't need to use 'make install' You can directly interact with u-boot.
The file $DEVDIR/logs/install/log contains the data exchanged with u-boot. Post the output of the log so we can see where it is getting stuck.
thanks for your reply.
This is the output of install.log:
-------- Mon Aug 2 21:12:00 2010 ---------
-------------------------------------------
-------- Mon Aug 2 21:12:56 2010 ---------
-------- Mon Aug 2 21:15:01 2010 ---------
-------- Mon Aug 2 21:28:47 2010 ---------
-------- Tue Aug 3 17:56:03 2010 ---------
-------- Tue Aug 3 18:01:54 2010 ---------
-------- Tue Aug 3 18:56:22 2010 ---------
Is there no idea why the 'make install' does not work? Can you paste the command to upload the kernel without using 'make install' or post some documentation?
There are several steps that we can check in order to narrow down the error you are getting,
1. Check that in fact the usb to serial adaptor you are using is actually in /dev/ttyUSB0. Unplug the connector, connect it again and run the dmesg command on your console and verify that it matches what you already configured in minicom.
2. Make sure you are using the serial method to communicate with the board. You can follow the next steps:
cd ~/DM365SDK844703$
make config
Go to> Installer configuration->Communication method with the target board and enable Serial Port
That will enable a new option ->Serial port for target communication, which you should modify to /dev/ttyUSB0, or the one that matches what you found out in step 1.
Save the configuration and run make install.
3. Now, when you run the make install command your board needs to be in the uboot prompt, which is the following:
If the board is there, then close minicom and try to execute the make install command again, please make sure that minicom is closed, otherwise, you will continue to get the same error.
Please let me know how it goes.
Cristina Murillo
Embedded Software Engineer, RidgeRun
Hi Cristina,
Thanks for your attention.
1. I unplug the connector and plug it again, next I run the dmesg command:
yUSB0
[ 3637.336606] ch341 3-1:1.0: device disconnected
[ 3641.976076] usb 3-1: new full speed USB device using uhci_hcd and address 4
[ 3642.142322] usb 3-1: configuration #1 chosen from 1 choice
[ 3642.145214] ch341 3-1:1.0: ch341-uart converter detected
[ 3642.158245] usb 3-1: ch341-uart converter now attached to ttyUSB0
2. I run make config commands and I go to Installer configuration->Serial port for target communication and I set /dev/ttyUSB0:
marian@marian:~$ cd DM365SDK844703
marian@marian:~/DM365SDK844703$ make config
Processing toolchain...
Processing kernel...
Processing fs...
Entering host-apps...
Entering apps...
Entering /home/marian/DM365SDK844703/toolchain...
Entering arch...
Entering mach...
Entering proprietary_src...
Entering myapps...
Processing bootloader...
Processing installer...
arch/arm/mach-davinci/Kconfig:44:warning: defaults for choice values not supported
arch/arm/mach-davinci/Kconfig:52:warning: defaults for choice values not supported
*** End of SDK configuration.
I save the configuration and I run 'make install':
marian@marian:~/DM365SDK844703$ make install
Installation system of uboot images over serial port /dev/ttyUSB0
Exit: -1
make: *** [install] Błąd 255
3. I run minicom, reset the board to get uboot promt 'Leopard 365 :>' and I close minicom (by pressing Ctrl+a and next q). Next I run 'make install' command again:
OPCJE: I18n
Skompilowany dnia Jan 25 2010, 06:49:09.
Port /dev/ttyUSB0
Wciśnij CTRL-A Z po pomoc na temat specjalnych klawiszy
T WARN: emac_send_packet: No link
DM36x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
DONE
Jumping to entry point at 0x81080000.
U-Boot 1.3.4-svn21 (Feb 24 2010 - 10:04:27)
I2C: ready
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,)
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
256 MiB
CTRL-A Z po pomoc |115200 8N1 | NOR | Minicom 2.4 | VT102 | Offline
marian@marian:~/DM365SDK844703$
I checked the communication with the Uboot, and I think it is OK, eg:
Leopard 365 :>printenv
bootdelay=4
baudrate=115200
bootcmd=tftp;bootm
serverip=192.168.0.162
bootfile=uImage
nfshost=192.168.0.162
rootpath=/home1/dm365/webcam_15/target/filesys
ipaddr=192.168.0.100
bootargs=console=ttyS0,115200n8 noinitrd rw ip=192.168.0.100 root=/dev/nfs nfsrM
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:0C:0C:A0:02:b5
ver=U-Boot 1.3.4-svn21 (Feb 24 2010 - 10:04:27)
Environment size: 441/262140 bytes
Can you give me what the installer sends to the Uboot to perform handshake? I'll run it in the uboot prompt and we'll see the answer.
Hi,
I use the standard serial cable on another computer which has got serial port and now everything is OK :) So what is the problem with usb to serial adaptor? Is the issue in the RR SDK?
I don't think the problem is in the SDK since we have tested it using a usb to serial adaptor. I can think of two possible issues: the usb to serial connector was not working or the usb-to-serial connector was not enabled on the make config menu.
Hello Cristina,
I am facing exactly the same problem... Can you please guide me from where i can enable the USB to serial support in make config. I have gone through config but i have not found any option to enable it.
Your help will be really appreciated.... Thank you.