Minicom will not connect to OMAP-L138 board

Hi Justin,

please ensure the following:

1. Boot switch settings for boot mode appropriate to OMAPL138 Logic PD / Spectrum Digital EVM,
2. port settings like Baudrate, parity, stop, flowcontrol e.t.c.,

Which version of dvsdk being used?

Regards,
Shankari

1. The boot switch settings are (annoyingly) not listed in the Software Developer's Guide, so I basically am guessing. I tried all OFF, and then S7/S8 ON with S1-6 OFF, and neither worked.

2. I mostly used the defaults from setup.sh, except for the port, which was found by running the command "ls -laF /dev/ttyUSB*" which outputs /dev/ttyUSB0 (I am using a usb-rs232 connector)

Serial device: /dev/ttyUSB0

Bps/par/bits: 115200 8N1

Hardware flow control: No

Software flow control: No

3. Version 4, the directory referenced by ${DVSDK} is "~/ti-dvsdk_omapl138-evm_4_01_00_09/"

Hi Justin,

            Kindly let us know the board you are using. Is it OMAP-L138 EVM(LogicPD / Spectrum Digital) or OMAP-L138_LCDK?

If you are using the OMAP-L138 EVM(LogicPD or Spectrum Digital board) refer the following wiki to flash and boot the u-boot and Linux kernel in the evm boards.

http://processors.wiki.ti.com/index.php/GSG:_DA8x/OMAP-L1/AM1x_DVEVM_Additional_Procedures

Note: The switch settings for both booting and flashing are available in the above wiki link for both LogicPD and Spectrum Digital  boards.

If you are using the OMAP-L138 LCDK kit refer the following wiki link

http://processors.wiki.ti.com/index.php/OMAP-L138_LCDK_Linux_Software_Developer%27s_Guide

Note: The boot switch settings for OMAP-L138 LCDK can be referred from the LCDK user guide wiki.

Regards

Iyshwarya

If this answers your question, please click the Verify Answer button below. If not, please reply back with more information.

I am using the EVM (LogicPD).

First I set S0-S6 off and S7/S8 on, as per the "Serial Boot and Flash..." instructions. I ran the following command in windows first:

sfh_OMAP-L138.exe -p COM4 -erase

After the erase was successful, I ran this command:

sfh_OMAP-L138.exe -p COM4 -flash ubl_OMAPL138_SPI_MEM.bin uImage-da850-omapl138-evm.bin

The ubl file was in the ./ubl directory (with respect to the sfh...exe file). The uImage...bin file was found in ${DVSDK}/psp/prebuilt-images/ in linux. I also tried flashing u-boot-da850-omapl138-evm.bin from the prebuilt-images/ folder with the same ubl.

Either way, I went into linux and ran {DVSDK}/setup.sh again, just to be sure things were setup correctly. Ethernet & serial port (/dev/ttyUSB0) were connected. When the minicom script runs, I turn off then on the EVM (s0-s7 is all off) and minicom freezes. I close the terminal, and try "minicom -w" in a new terminal, then power-cycle the EVM again. Nothing happens, and it says 'offline' in the bottom-right. Upon checking serial port configuration, everything looks correct (/dev/ttyUSB0, 115200 8N1).

Hi Justin,

            Kindly follow the following wiki link to flash the u-boot in your LOGICPD OMAP-L138 EVM.

http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138#Restoring_the_OMAP-L138_EVM_SPI_Flash

Ensure that you need to flash the ubl and u-boot binary only through the serial flasher utility and the uImage has to be flashed using u-boot.

The switch settings needed to both flashing and booting u-boot can be referred from the above wiki link itself.

As you are using Serial flasher utility in windows, ensure whether the u-boot prompt is obtained in the Teraterm/HyperTerminal in windows.

If u-boot prompt is obtained in windows then use the following wiki link to boot linux in your board.

http://processors.wiki.ti.com/index.php/Booting_Linux_kernel_using_U-Boot

Regards

Iyshwarya

If this answers your question, please click the Verify Answer button below. If not, please reply back with more information.

Justin,

Before you run the setup.sh script, you need to ensure that your ubl and uboot have been flashed correctly. The way to verify this is after flashing the ubl and uboot on the EVM through SFH set the boot pins to SPI FLash boot mode using the wiki that Iyshwarya has provided and see if you see the uboot prompt in minicom.

The last few step of setup.sh script tries to write the uboot environment based on the setup you have described but if it doesn`t detect a uboot environment will terminate so it is essential that you are able to see the uboot come up from flash.

Regards,

Rahul

In Tera Term, I get this successful response upon power cycling! :

OMAP-L138 initialization passed!
Booting TI User Boot Loader
UBL Version: 1.65
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.

U-Boot 2009.11 (Nov 09 2010 - 18:48:43)

I2C: ready
DRAM: 64 MB
MMC: davinci: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
Invalid MAC address read.
Net: Ethernet PHY: GENERIC @ 0x00

Hit any key to stop autoboot: 0
Card did not respond to voltage select!
8192 KiB M25P64 at 0:0 is now current device
Wrong Image Format for bootm command
ERROR: can't get kernel image!
U-Boot >

However, in linux using minicom, I get no response. Any ideas? The port is COM4 in windows, but /dev/ttyUSB0 in linux. I checked all of the settings: 115200, 8N1, no hardware/software flow, etc. 

Justin,

This seems to be an issue with your serial-to-USB driver on your Linux machine/ Virtual Box rather than an issue with the hardware. I would recommend posting this on the Linux forums to see if someone can provide you any inputs there.

Regards,

Rahul

#######The following commands were run on host to set its ip address and to verify the correct files are in /tftpboot. 192.168.1.5 was chosen arbitrarily

host$ ls /tftpboot/
arago-base-image-arago.ext2.gz
arago-base-image-glibc-ipk-2009.11-arago.rootfs.ext2
uImage-da850-omapl138-evm.bin
uImage-da850-omapl138-evm.bin.02072013_17.24
uImage-da850-omapl138-evm.bin.02072013_17.27
host$ sudo /sbin/ifconfig eth0 192.168.1.5 netmask 255.255.255.0 up
host$ /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr bc:ae:c5:e0:13:43
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::beae:c5ff:fee0:1343/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:127 errors:0 dropped:0 overruns:0 frame:0
TX packets:108 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19506 (19.5 KB) TX bytes:16671 (16.6 KB)
Interrupt:27 Base address:0x6000

#######upon running minicom -w (ttyF0) and power cycling (now using ubuntu on my desktop with a real serial port card & working drivers):

OMAP-L138 initialization passed!
Booting TI User Boot Loader
UBL Version: 1.65
UBL Flashtype: SPI
Starting SPI Memory Copy...
Valid magicnum, 0x55424CBB, found at offset 0x00010000.
DONE
Jumping to entry point at 0xC1080000.

#the following commands

U-Boot 2009.11 (Nov 09 2010 - 18:48:43)

I2C: ready
DRAM: 64 MB
MMC: davinci: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
Invalid MAC address read.
Net: Ethernet PHY: GENERIC @ 0x00

Hit any key to stop autoboot: 0
Card did not respond to voltage select!
8192 KiB M25P64 at 0:0 is now current device
Wrong Image Format for bootm command
ERROR: can't get kernel image!
U-Boot > setenv autoload no
U-Boot > setenv ipaddr 192.168.1.6
U-Boot > setenv serverip 192.168.1.5
U-Boot > setenv bootfile uImage-da850-omapl138-evm.bin
U-Boot > setenv ethaddr bc:ae:c5:e0:13:43
U-Boot > printenv
bootargs=mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off
bootcmd=if mmc rescan 0; then if fatload mmc 0 0xc0600000 boot.scr; then source
0xc0600000; else fatload mmc 0 0xc0700000 uImage; bootm c0700000; fi; else sf pr
obe 0; sf read 0xc0700000 0x80000 0x220000; bootm 0xc0700000; fi
bootdelay=3
baudrate=115200
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.11 (Nov 09 2010 - 18:48:43)
autoload=no
ipaddr=192.168.1.6
serverip=192.168.1.5
bootfile=uImage-da850-omapl138-evm.bin 
ethaddr=bc:ae:c5:e0:13:43
U-Boot > sf probe 0
U-Boot > 8192 KiB M25P64 at 0:0 is now current device
U-Boot > tftp 0xc0700000 uImage-da850-omapl138-evm.bin
Using device
TFTP from server 192.168.1.5; our IP address is 192.168.1.6
Filename 'uImage-da850-omapl138-evm.bin'.
Load address: 0xc0700000
Loading: T T T T T T T T T T T T T T T T T T T T
Retry count exceeded; starting again
Using device
TFTP from server 192.168.1.5; our IP address is 192.168.1.6
Filename 'uImage-da850-omapl138-evm.bin'.
Load address: 0xc0700000
Loading: T T T T T T T T T T T T T T T T T T

#######I also tried the names uImage and uImage-da850-omapl138-evm (without .bin extension) and I get the same problem.
#######I then tried changing the bootargs/bootcmd before running "U-Boot > tftp 0xc0700000 uImage-da850-omapl138-evm.bin"
U-Boot > setenv bootargs mem=32M console=ttyS2,115200n8 root=/dev/ram0 rw initrd=0xc1180000,4M ip=dhcp eth=${ethaddr}
U-Boot > setenv bootcmd 'tftp 0xc0700000 uImage-da850-omapl138-evm; tftp 0xc1180000 arago-base-image-glibc-ipk-2009.11-arago.rootfs.ext2; bootm 0xc0700000'
#######but the same problem occurs

Thanks again for all the help, I feel like I'm getting closer to the solution.