omap3530dcbc MMC issue

Maxim Podbereznyy

Other Parts Discussed in Thread: OMAP3530

Hi everybody!

This is my first post here.

I've designed a SODIMM module based on and now have a manufactured sample of it.
The design of the module was cloned from BeagleBoard obviously omitting connectors and other optional stuff.

I have EBVBeagle full set and there is SD card there with X-loader and other necessary stuff on it. So, I have a Baseboard for my module with 90% compatibility with BeagleBoard. Now I insert SD card from EBVBeagle and expect to see u-boot prompt but instead of that I can see only a bunch of crap spat to Hyperterminal and all.

So I began investigations:
1) 3V is alive for VMMC1

2) 32KCLKOUT is 32kHz (measured with oscilloscope)
3) HFCLKOUT is 26MHz
4) on Reset I can see a huge number of impulses on MMC1_CLKO line
5) MMC1_CMD also has impulses
6) None of MMC1_DATx has changes during activity on CLK line
7) pressing USER1 button does not change the picture on oscilloscope

other conditions:
if I connect usb-cable to mini-usb connector - WinXP finds OMAP3430 device but I can't find a driver for it.

I know that both CPU and pop-memory are different for Beagle and my module (packages are different). Are these differences affect the MLO and x-loader files?

What additional electrical signal should monitor to find the issue?

Any advice is appreciated!

Best regards,

Max

over 15 years ago

0 Jason Kridner over 15 years ago

TI__Intellectual 1660 points

I'm aware of two solutions to utilize the USB firmware in the ROM:

Because the version of u-boot-v2 using with omap3_usbload above can fit in the internal memory, that might be very useful for you to play with. I also recommend getting JTAG emulation hardware.

Yes, x-loader is impacted by memory module changes. You can pull the MLO/x-load sources using http://elinux.org/BeagleBoard#X-Loader (http://gitorious.org/x-load-omap3). MLO and x-loader are the same root programs. One is just renamed for placement on the SD card. Partitioning, formatting and file installation onto the SD card is very particular for the ROM to pick it up. Look through the sources on the pin muxing and DRAM configuration.

Sorry to not give you a direct pin to monitor. Perhaps someone else could chime in with an answer for that, but I would recommend looking at the BeagleBoard System Reference Manual and looking at the list of probe points there.

0 Maxim Podbereznyy over 15 years ago in reply to Jason Kridner

Intellectual 860 points

Dear Jason,

thank you for reply!

I've tried USB recovery tool from Elinux, but with no success. The problem appears in Linux: a CPU is correctly found but immidiately disconnects. Here is a dmesg prints:

usb 1-2: new high speed USB device using ehci_hcd and address 9
usb 1-2: configuration #1 chosen from 1 choice
usb 1-2: New USB device found, idVendor=0451, idProduct=d009
usb 1-2: New USB device strings: Mfr=33, Product=37, SerialNumber=0
usb 1-2: Product: OMAP3430
usb 1-2: Manufacturer: Texas Instruments
usb 1-2: USB disconnect, address 9

I've tried FC7 and FC10, the result is the same.

So, when I use the utility it fast stops:

TI OMAP3 USB boot ROM tool, version 0.1
(c) 2008 Martin Mueller <martinmm@pfump.org>

.......................

found device!
could not set configuration

BTW, can you confirm that I need to change x-loader for the memory installed on me module? I thought it differed only in package

0 Maxim Podbereznyy over 15 years ago in reply to Maxim Podbereznyy

Intellectual 860 points

further attempts to boot cpu:

as USB recover procedure does not work - I tried to perform "UART recovery" described at eLinux:

pserial seems to work fine:

Waiting For Device ASIC ID: Press Ctrl+C to stop
ASIC ID Detected.
Sending 2ndFile:
Downloading file: 100.000% completed(12700/12700 bytes)
File download completed.

But ukermit stops without messaged and nothing happens. I'm trying to insert debug messages into ukermit sources to locate an obstacle for the code download.
sudo ./ukermit -p /dev/ttyUSB0 -f u-boot.bin
^C

if power off the board and then power on during ukermit executes:
[maxx@sonja boot_omap3_serial]$ sudo ./ukermit -p /dev/ttyUSB0 -f u-boot.bin 
Failed after 4 retries in sequence 0 - success send = 0 bytes
Data transmit failed

0 suyuxuan su over 14 years ago in reply to Maxim Podbereznyy

Prodigy 145 points

if power off the board and then power on during ukermit executes:
[maxx@sonja boot_omap3_serial]$ sudo ./ukermit -p /dev/ttyUSB0 -f u-boot.bin 
Failed after 4 retries in sequence 0 - success send = 0 bytes
Data transmit failed

I met and you are same question, excuse me you solved?