Mity CPU Platforms » MityDSP-L138 (ARM9 Based Platforms)

Hi David -

I'll let the technical team address the hang. But just wanted to let you know that modules are shipped without a kernel or file system installed. This is a customer configuration step since our customers run a variety of operating systems and configurations. Sorry if this has caused any confusion.

Thanks,
Tom

Hi Dave,

Can you please post the complete text of the boot attempt, from the start of power up to the hang?

Also, can you please type "factoryconfig" as well as "config" and dump the results from u-Boot?

Thanks.

-Mike

Mike,

Thanks for your fast response. The requested information is listed below.

Dave

1. Complete Boot Sequence <<<<<<<<<<<<<<

OMAP-L138/AM-1808/AM-1810 initialization passed!
Configuring 128MB mDDR
Booting TI User Boot Loader
UBL Version: 1.65:2.28.1 BuiltJul 11 2011 12:49:53
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 (Mar 31 2011 - 19:39:18)

I2C: ready
DRAM: 128 MB
NAND: 256 MiB
MMC: davinci: 0
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
EMIFA CLock : 100000000 Hz
DSP Clock : 300000000 Hz
ASYNC3 Clock : 150000000 Hz
Enet config : 2
MMC 0 Enable : 0
Resetting ethernet phy
Net: Ethernet PHY: GENERIC @ 0x03 [0x8]

1. Booting kernel from Legacy Image at c0700000 ...
   Image Name: Linux-2.6.34-rc1-07430-g2e70fb6
   Image Type: ARM Linux Kernel Image (uncompressed)
   Data Size: 1818012 Bytes = 1.7 MB
   Load Address: c0008000
   Entry Point: c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
   OK

Starting kernel ...

(No further text is displayed at this point)

2. u-boot factoryconfig settings <<<<<<<<<<<<<<

U-Boot > factoryconfig
Factory Configuration:
Config Version : 1.1
MAC Address : 00:50:C2:BF:8D:E5
Serial Number : 110382
FPGA Type : 2 [XC6SLX16]
Part Number : L138-DG-225-RI
U-Boot >

3. u-boot config settings <<<<<<<<<<<<<<

U-Boot > config
MityDSP-L138 Configuration:
Config Version : 1.0
Config Size : 264
Manufacturer : Critical Link
Ethernet Config : 2
Ethernet Name : GENERIC @ 0x03
Ethernet PHYMask: 8
LCD Config : 0
MMC0 Config : 0
MMC1 Config : 0
U-Boot >

Hi Dave,

I think you might want to use the uImage located in the release_2011-08-01.run file under MDK_2011-08-01/images/uImage. There are several bug fixes from the May 2010 release that may be causing the hang.

If that doesn't help, here are a couple more questions that I would have:

1) Have you tried more than one recent MityDSP module into the same host board? You get the same behavior?

2) Are you plugging this into an Industrial I/O host board or a custom host board? If a custom host board, would you be willing to (offline, of course) share the schematic for the board or discuss what peripherals you have hooked to the unit?

Thanks.

-Mike

Mike,

The new boards boot with the 2011-08-01 uImage. I still need to check if this image is backwards compatible with the older MityDSP boards.

Thanks,
Dave

Mike,
Can you elaborate on the significance of the lines in the config response that read:
MMC0 Config : 0
MMC1 Config : 0

I just brought up a couple of our carrier boards with mity-omapl138s using the 08-01-11 kernel
and once the boot sequence completes, there are no MMC devices available on the system.
I'm wondering if this is a configuration issue.

-Rich

Hi Rich,

So in the u-Boot, the config block is read on start-up in order to tell u-Boot whether or not it should configure the MMC pins and enable the device.

Right now, we only support MMC0 configuration, and the prompts for the detect pins and the write protect pins are pretty much ignore (you can check all this out, if you are interested, in the u-boot source code).

We did this because we didn't want the stock u-Boot to enable the MMC pins, etc., for folks who had baseboards that used those pins for other purposes and wanted to avoid contention on u-Boot. The same applies for the ethernet configuration (MII, RMII, or none).

You might check the configuration for the 08-01-11 kernel (cat /proc/config.gz | gzip -d) and ensure that the MMC drivers are enabled. The default kernel should configure the pix mux for the Industrial I/O boards and install the drivers regardless of the config setting in u-Boot. Are you using the stock kernel image?

-Mike

Ok, I'll go check the config.gz settings and let you know what I find out.

HI Mike,
I'm attaching a file that contains the results of the check of the config.gz file filtering by MMC
both your and our configuration report the same info.

THere is a difference at the point in the boot sequences where udev starts where your configuration
mounts the MMC device and ours doesn't. Is there something in the setup of udev that we might have
missed to have it load the MMC device?

THanks for your assistance!
Rich

Hi Mike,
No need to dig into the file I sent.
I downloaded the 12-05-2011 MDK and rebuilt the kernel
using that configuration after running menuconfig to
check that the mmc drivers were enabled. I didn't make
any changes to the configuration other than to take a peek
at the configuration reported by menuconfig.

Anyway, after rebuilding the kernel and loading uImage the
mmc card is now mounted as desired with that kernel build
running on our system.

-Rich