I have two SDK-OMAP3530-20 Zoom Development Kits. I've been trying to just get something to load on both boards.
My first attempt was to follow the instructions in the Quick Start Guide (1014938C_Torpedo_DevKit_QSG.pdf) for getting the Demo Windows CE
up and running. So I connected the SOM, connected the battery, connected the LED screen, inserted the provided Windows CE SD card into the
primary slot, and attached the 5V power supply. I then switch the Power On and .. *drum roll* .. nothing. The guide says "After a few moments,
you will see the graphical user interface (GUI) of the pre-built OS image appear on the 4.3” WQVGA LCD". After waiting a lot longer than a few
moments, there appears to be nothing happening. The LED1 and LED2 lights toggle back and forth, but no other activity is noticeable.
So I start digging through other manuals, and I find Section 3: Sample Pre-Built Images in the OMAP35x WinCD6 BSP UM
(1016591B_OMAP35x_WinCE6_BSP_UM.pdf). This section provides some instructions for manually loading the bin files from the SD card into RAM.
Sounds promising. So I do the following from within losh prompt:
Quote:
losh> mount fatfs /dev/sdmmc0a /sd
sdmmc_update_clk_rate: want 200000
div -> 30720
sdmmc_update_clk_rate: want 25000000
div -> 256
losh> cd /sd
losh> ls
: LOGIC_welcome_video.wmv 2276657
: CEPLAY.EXE 205312
: NK_release.bin 20275871
: LOGICPD.BMP 391734
: JUMP.BMP 391734
: autoexec.losh 343
: LBOOT.CFG 131072
: LBOOT.ELF 321520
: MLO 22148
losh> load bin NK_release.bin
loading from NK_release.bin:
R
................................................................................................................................................................................
image launch addr: 0x8120a2a0
Verifying checksums: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Checksums good.
file loaded
losh> exec
Windows CE Kernel for ARM (Thumb Enabled) Built on Jan 21 2009 at 18:02:34
-----------------------------------------
LPD_OMAP35X_SOM Clock Information
.......................................
DPLL1: MPU_CLK/ARM_FCLK : 600MHz
DPLL2: CLK_OUT : 215MHz
CLK_OUT_x2 : 430MHz
IVA2_CLK : 215MHz
DPLL3: FCLK_OUT : 332MHz
FCLK_OUT_x2 : 664MHz
FCORE_CLK : 332MHz
L3_ICLK : 166MHz
L4_ICLK : 83MHz
DPLL4: FCLK_OUT : 432MHz
FCLK_OUT_x2 : 864MHz
FCORE_CLK : 48MHz
-----------------------------------------
--------------------------------------------
PMIC Battery Charging Setup for Torpedo Kit
(Should be done in Battery Driver)
TWL_BB_CFG: 19
TWL_BCICTL1: 2b
TWL_BCICTL2: 00
TWL_BCIVREF1: cd
TWL_BCIVREF2: 02
TWL_BCIIREF1: 68
TWL_BCIIREF2: 03
--------------------------------------------
Cold-boot: erasing object store
Profiler Enabled - Frequecy: 13000000 hz
-----------------------------------------
LogicPD OMAP35X SOM Revision Information
.......................................
BSP Revision : 1.1.x UNRELEASED
Built for Hardware : OMAP35x TORPEDO
-----------------------------------------
LogicPD OMAP35X SOM CoProc Information
.......................................
L1 Cache : Enabled
L2 Cache : Enabled
Branch Prediction : Enabled
-----------------------------------------
LogicPD OMAP35X SOM Processor Information
.......................................
Processor Revision : 3.1
Silicon ID Code Reg : 0x4b7ae02f
CPU Main ID Register : 0x411fc083
Architecture ID : 0x0000000f
ARM Ver : ARMv6 or greater
-----------------------------------------
OEM Initialization Done.
Starting Kernel...
The manual says "Immediately, the kit LCD should turn on. In Tera Term, you will see a message stating Starting Kernel... and then other output
messages." The screen does turn white, and I see the "Starting Kernel..." message. But I see no more messages and nothing else seems to
happen. The SOM light is now on and its seems to be glowing: starts dim, slowly fades to bright, then back to dim. It does this twice quickly,
pauses, then repeats. I found a note in the "Known Issues" section of the
logic_som_omap35x_source_2_0_1/logic_som_omap35x_source_readme.txt that states:
+ Intermittent issue with white screen and no Windows shell at boot
When booting and loading image from SD, after running "exec" the LCD
sometimes remains at the white screen. Wait for the system to suspend
(6 minutes) and then bring the system out of suspend by either touching the
LCD screen or pressing the resume button (S2) to display the Windows shell.
(Jira # OMAP3WCE600-357)
This seems to be part of my issues. The screen is white and seems to hold there. And if I wait for about 6 minutes, the screen does turn off.
However, pressing the S2 button has no effect. If I touch the LCD screen, the white screen comes back, but I do not see any other change.
I decided to then see if the there was a new Windows CE Demo available. I downloaded 1013029A_OMAP35x_Torpedo_WinCE_SD_Image.zip from
logicpd, and after doing a binary compare, I can see the files are identical to what is on the provided SD demo card.
Since Windows CE is not our intended target, I then decided to try the linux demo image. Following the instructions in Section 2 of the OMAP35x
Linux BSP User Manual (OMAP35x Linux BSP User Manual), I did the following in the losh prompt:
Quote:
losh> mount fatfs /dev/sdmmc0a /sd
sdmmc_update_clk_rate: want 200000
div -> 30720
sdmmc_update_clk_rate: want 25000000
div -> 256
losh> cd /sd
losh> ls
: 1016980_release-notes.txt 14990
: 1016980_linux-demo-omap35x-2.1-yaffs2.elf 2763275
: 1016980_linux-demo-omap35x-2.1-ramdisk.elf 14910327
: 1016980_x-load.bin.ift 20684
: 1016980_uImage 2500648
: 1016980_u-boot.bin 217228
: 1016980_u-boot 852644
: 1016980_rootfs.yaffs2 31699008
: 1016980_rootfs.ext2.gz.uboot 12124484
losh> load elf 1016980_linux-demo-omap35x-2.1-ramdisk.elf
loading from 1016980_linux-demo-omap35x-2.1-ramdisk.elf:
...................................................................................................................................................................................
ELF section 0: download address: 0x80208000 load address: 0x80e80000
ELF section 1: download address: 0x80240000 load address: 0x81000000
ELF section 2: download address: 0x804a8000 load address: 0x81300000
warning: guessing combined program header size as 12124484
warning: guessing combined program header size as 14625132
loaded 14842360 @ 0x80e80000 Ram
file loaded
losh> exec
U-Boot 2009.08-rc2/bsp-2.1 (Oct 07 2010 - 08:35:07)
OMAP3530-GP ES3.1, CPU-OPP2 L3-165MHz
OMAP3 Logic + LPDDR/NAND
DRAM: 128 MB
NAND: 256 MiB
NAND: HW ECC selected
*** Warning - bad CRC or NAND, using default environment
Read production data: done
Board: Torpedo
Die ID #7ecc000400000000040140790d00b004
Part Number : 1013994
Model Name : SOMOMAP3530-20-1670AGCR-A
Serial Number: 4009M00198
Net: smc911x-0
Warning: smc911x-0 MAC addresses don't match:
Address in SROM is 00:08:ee:03:78:6a
Address in environment is 41:00:30:30:30:30
======================NOTICE============================
This is the first time that you boot up this board. You are
required to set a valid display for your LCD panel.
Enter the display number of the LCD panel(none for no LCD panel)
Pick one of:
2 == LQ121S1DG31 TFT SVGA (12.1) Sharp
3 == LQ036Q1DA01 TFT QVGA (3.6) Sharp w/ASIC
5 == LQ064D343 TFT VGA (6.4) Sharp
7 == LQ10D368 TFT VGA (10.4) Sharp
15 == LQ043T1DG01 TFT WQVGA (4.3) Sharp
MAKE SURE YOUR DISPLAY IS CORRECTLY ENTERED!
Please enter your LCD display number:15
display=15
Saving Environment to NAND...
Erasing Nand...
Erasing at 0xffe0000 -- 100% complete.
Writing to Nand... done
Hit any key to stop autoboot: 0
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.32-bsp-2.1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2500584 Bytes = 2.4 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81300000 ...
Image Name: uboot ext2 ramdisk rootfs
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 12124420 Bytes = 11.6 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux.........
At this point, the board appears to stop responding. The Linux Penguin never shows up on the screen - nor does it appear the screen has even
turned on. The SOM LED is on bright, and steady. I noticed the ethernet address is incorrect. So I started over and modified this value manually
in uboot. The end result being the same.
Thanks for any information you can provide me on what I need to do to get this working.