Please note that User Registration has been temporarily disabled due to a recent increase in automated registrations. If anyone needs an account, please request one here: RequestAccount. Thanks for your patience!--Wmat (talk)
Please email User:Wmat if you experience any issues with the Request Account form.

Devkit8000 FAQ

From eLinux.org
Revision as of 02:55, 13 June 2011 by Yclinda666 (Talk | contribs)

Jump to: navigation, search

This page mainly summarizes solutions to some main problems during the development of Embest Devkit8000. Hope it would give you some help.

Hardware problem

If you had erased NAND flash, how to boot the system?

Answer: If the Nand Flash has been erased, user can boot the system through SD card. OMAP35x series chips can support booting x-loader from SD card. User can refer to Devkit8000 user manual to update image from SD card.

How to use USB OTG as Host or Device?

Answer: The USB OTG interface can be used as USB Host function with a Mini-A to Standard-A cable, or used as USB Device function with a Mini-B to Standard-A cable.

If using USB OTG interface as USB Host, please follow below steps: 1) Connect Hub power to USB Hub; 2) Connect USB OTG cable to Devkit8000 board; 3) Power on and get into system; 4) Plug in USB Hub to USB OTG through cable; 5) Insert USB mouse or keypad to USB Hub.

How to boot from SD card?

Answer:Press BOOT key and power on, the system will boot from SD card first and then boot from Nand flash.

How to debug DSP and ARM on Devkit8000?

Answer: We suggest two ways:
1. Connect with JTAG Emulator
Embest provide XDS100v2 and TDS560 emulators which can be used for TI's C2000, C5000, C6000 chips and OMAP, DaVinci, ARM7 and ARM9 microprocessors.

2. Dubug in software system
User can refer to the DEMO-DVSDK in product CD. The DVSDK has provided complete video encoding and decoding drivers, user only needs to dubug the DSP algorithms. Please refer to TI's website for details: http://focus.ti.com/docs/toolsw/folders/print/linuxdvsdk-omap3530.html

What's the RTC battery model can be used for Devkit8000?

Answer: The DevKit8000 board is not delivered with RTC battery, user needs to prepare it themselves. The battery model is CR1220.


Linux problem

If the Nand Flash has been erased, how to restore it?

Answer: Please download the linux_WriteToNandflash.rar,and decompress the linux_WriteToNandflash.rar, copy all files to the SD card in the linux_WriteToNandflash.rar, and then boot the image from the SD card.

Warnning:If your NandFlash has OS before, please erase it, enter to the u-boot command mode and input the commands of "nand erase" to erase the NandFlash.

How to open low-lever debug information when developing drivers?

Answer: Please follow below steps:
1. make omap3_devkit8000_defconfig
2. make menucofig
Select “Kernel low-level debugging functions”

Symbol: DEBUG_LL [=y] 
Prompt: Kernel low-level debugging functions
Defined at arch/arm/Kconfig.debug:54
Depends on: DEBUG_KERNEL
Location:
-> Kernel hacking

3. make uImage
User can use the uImage directly after finishing compiling.

How to display switching between LCD and DVI output?

Answer: You need to modify kernel parameter:
4.3" LCD:
OMAP3 DevKit8000 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 4.3inch_LCD

5.6" LCD:
OMAP3 DevKit8000 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode: 5.6inch_LCD

7" LCD:
OMAP3 DevKit8000 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:7inch_LCD

DVI monitor:
OMAP3 DevKit8000 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:720p60

VGA monitor:
OMAP3 DevKit8000 # setenv bootargs console=ttyS2,115200n8 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs video=omapfb:mode:VGA

How to use tftp to update image booting from Nand flash?

Answer: Devkit8000 has 10/100M Ethernet (DM9000) on board, user can update image booting from Nand flash through tftp.
1)x-loader booting image update
OMAP3 DevKit8000 # tftp 80000000 x-load.bin.ift_for_NAND
dm9000 i/o: 0x2c000000, id: 0x90000a46
MAC: aa:bb:cc:dd:ee:ff
operating at 100M full duplex mode
TFTP from server 192.192.192.90; our IP address is 192.192.192.200
Filename 'x-load.bin.ift_for_NAND'.
Load address: 0x80000000
Loading: T #
done
Bytes transferred = 9664 (25c0 hex)
OMAP3 DevKit8000 # nand unlock
device 0 whole chip
nand_unlock: start: 00000000, length: 134217728!
NAND flash successfully unlocked
OMAP3 DevKit8000 # nand ecc hw
OMAP3 DevKit8000 # nand erase 0 80000

NAND erase: device 0 offset 0x0, size 0x80000
Erasing at 0x60000 -- 100% complete.
OK
OMAP3 DevKit8000 # nand write.i 80000000 0 80000

NAND write: device 0 offset 0x0, size 0x80000

Writing data at 0x7f800 -- 100% complete.
524288 bytes written: OK

2)u-boot booting image update
OMAP3 DevKit8000 # tftp 80000000 flash-uboot.bin
dm9000 i/o: 0x2c000000, id: 0x90000a46
MAC: aa:bb:cc:dd:ee:ff
operating at 100M full duplex mode
TFTP from server 192.192.192.90; our IP address is 192.192.192.200
Filename 'flash-uboot.bin'.
Load address: 0x80000000
Loading: T #################################################################
done
Bytes transferred = 1085536 (109060 hex)
OMAP3 DevKit8000 # nand unlock
device 0 whole chip
nand_unlock: start: 00000000, length: 134217728!
NAND flash successfully unlocked
OMAP3 DevKit8000 # nand ecc sw
OMAP3 DevKit8000 # nand erase 80000 160000

NAND erase: device 0 offset 0x80000, size 0x160000
Erasing at 0x1c0000 -- 100% complete.
OK
OMAP3 DevKit8000 # nand write.i 80000000 80000 160000

NAND write: device 0 offset 0x80000, size 0x160000

Writing data at 0x1df800 -- 100% complete.
1441792 bytes written: OK

3)Kernel image update
OMAP3 DevKit8000 # tftp 80000000 uImage
dm9000 i/o: 0x2c000000, id: 0x90000a46
MAC: aa:bb:cc:dd:ee:ff
operating at 100M full duplex mode
TFTP from server 192.192.192.90; our IP address is 192.192.192.200
Filename 'uImage'.
Load address: 0x80000000
Loading: T #################################################################
done
Bytes transferred = 1991900 (1e64dc hex)
OMAP3 DevKit8000 # nand unlock
device 0 whole chip
nand_unlock: start: 00000000, length: 268435456!
NAND flash successfully unlocked
OMAP3 DevKit8000 # nand ecc sw
OMAP3 DevKit8000 # nand erase 280000 200000

NAND erase: device 0 offset 0x280000, size 0x200000
Erasing at 0x460000 -- 100% complete.
OK
OMAP3 DevKit8000 # nand write.i 80000000 280000 200000

NAND write: device 0 offset 0x280000, size 0x200000

Writing data at 0x47f800 -- 100% complete.
2097152 bytes written: OK

4)File system image update
OMAP3 DevKit8000 # tftp 80000000 ubi.img
dm9000 i/o: 0x2c000000, id: 0x90000a46
MAC: aa:bb:cc:dd:ee:ff
operating at 100M full duplex mode
TFTP from server 192.192.192.90; our IP address is 192.192.192.200
Filename 'ubi.img'.
Load address: 0x80000000
Loading: T #################################################################
done
Bytes transferred = 12845056 (c40000 hex)
OMAP3 DevKit8000 # nand unlock
device 0 whole chip
nand_unlock: start: 00000000, length: 268435456!
NAND flash successfully unlocked
OMAP3 DevKit8000 # nand ecc sw
OMAP3 DevKit8000 # nand erase 680000 7980000

NAND erase: device 0 offset 0x680000, size 0x7980000
Erasing at 0x7fe0000 -- 100% complete.
OK
OMAP3 DevKit8000 # nand write.i 80000000 680000 $(filesize)

NAND write: device 0 offset 0x680000, size 0xc40000

Writing data at 0x12bf800 -- 100% complete.
12845056 bytes written: OK

How to install linux cross compile tool?

Please follow below steps:
1.Download cross compile tool from website
http://www.codesourcery.com/sgpp/lite/arm/portal/package1787/public/arm-none-linux-gnueabi/arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
2.Decompress software
sudo tar xvf arm-2007q3-51-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 -C /home/

3.Tool installation
mkdir /home/embest/tools
cp /media/cdrom/linux/tools/mkimage /home/embest/tools
cp /media/cdrom/linux/tools/signGP /home/embest/tools
cp /media/cdrom/linux/tools/mkfs.ubifs /home/embest/tools
cp /media/cdrom/linux/tools/ubinize /home/embest/tools
cp /media/cdrom/linux/tools/ ubinize.cfg /home/embest/tools

4.Set environment variables
export PATH=/home/arm-2007q3/bin/:/home/embest/tools:$PATH

USB OTG used as Host

Answer: If using USB OTG interface as USB Host, please follow below steps:
1) Connect Hub power to USB Hub;
2) Connect USB OTG cable to Devkit8000 board;
3) Power on and get into system;
4) Plug in USB Hub to USB OTG through cable;
5) Insert USB mouse or keypad to USB Hub.

If user uses your own USB cable, please pay attention to USB OTG (Mini-AB) wire map:
1: VB
2: D-
3: D+
4: ID
5: GND
User needs only to short circuited 4 and 5.

Is there any solution to solve inaccurate touch screen problem?

Answer: Please modify the file arch/arm/mach-omap2/board-omap3devkit8000.c
struct ads7846_platform_data ads7846_conf = {

       .x_max                  = 0x0fff,
.y_max = 0x0fff,
//.x_plate_ohms = 180,
//.pressure_max = 255,
.debounce_max = 10,
.debounce_tol = 5,
.debounce_rep = 1,
.get_pendown_state = ads7846_get_pendown_state,
.keep_vref_on = 1,
.settle_delay_usecs = 150,

};

How to set NFS server on Devkit8000 board?

Answer: Please follow below steps:
1. Please make sure your PC OS is set the NFS server. 2. Connect the net cable between PC and Devkit8000 board. 3. Power on the Devkit8000 board, and enter to U-boot command line,input the following command:

 setenv bootargs console=ttyS2,115200n8 root=/dev/nfs nfsroot=192.192.192.117:/home/lijr/work/nfsroot/rootfs ip=192.192.192.200:192.192.192.117:192.192.192.101:255.255.255.0:devkit8000:eth0:off

Note:
192.192.192.200 is IP of board;
192.192.192.117 is IP of PC;
192.192.192.117:/home/lijr/work/nfsroot/rootfs is the mounted rootfs on PC;
192.192.192.101 is IP of gateway;
255.255.255.0 is subnet mask;
devkit8000 is name (can be modified);

How to settle VGA display for a while and then closed problem in Linux?

Answer: Please modify the file /etc/init.d/rcS in file system, adding below contents:

  1. ---------------------------------------------
  2. Disable power management
  3. (Requires sysfs support in the kernel)
  4. ---------------------------------------------

echo -n " Disabling Power mgmt  : "
echo -n "1" > /sys/power/cpuidle_deepest_state
status $? 1

  1. ---------------------------------------------
  2. Turn off LCD after 1 hour of inactivity
  3. (Requires sysfs support in the kernel)
  4. ---------------------------------------------

echo -n " Turn off LCD after 1 hour  : "
echo -n "0" > /sys/power/fb_timeout_value
status $? 1

How to use S-Video output?

Answer: Please select below in kernel configuration:
Multimedia devices --->

     [*] Video capture adapters  --->
VID1 Overlay manager (Use TV Managaer) --->
(X) Use TV Manager

And then recompile and put the created uImage in SD card and boot system.
After recompiling, you need to download testing tool video_test and video example foreman_vga_422.yuv from http://code.google.com/p/devkit8000/downloads/list

Input below after getting into kernel:
Copy video_test and foreman_vga_422.yuv files to board and run as below:
video_test /foreman_vga_422.yuv

How to set excuting command automatically after booting up system?

Answer: Modify /etc/init.d/rcS file of file system and add your commands. Then you can execute command automatically after booting up system. Add & after commands can implement backstage excecuting command automatically after booting up.

How to configurate for reusing GPIO?

Answer: Please configurate board/omap3devkit8000/omap3devkit8000.c in MUX_DEFAULT_ES2, refer to the Seventh Chapter "System Control Module" for detailed configuration way.

Wince Problems

How to update WinCE image to Nand Flash?

Answer: Please follow below steps:
(1)Run the software of HP Disk Storage Format Tool and format the SD card for FAT or FAT32 filesystem.
(2) Copy the image file(MLO, EBOOTNAND.nb0, NK.bin, ADevKit8000.exe) from CD:\wince_6\image\ lcd480X272 to SD card, then change the name from EBOOTNAND.nb0 to EBOOTSD.nb0 in the SD card.
(3) Insert the SD card to the board, press the BOOT button and then power on the board again; HyperTerminal will start printing the output information, at the same time press [SPACE] to enter the EBOOT menu.
(4) Press [5] to enter the Flash manage menu.
(5) Press [a], [b], [c] separately to write the image(XLDR, EBOOT, NK) to flash.
(6) Press [0] to return to the main menu, and press [2], [4], [7], [7] to change the boot device.
(7) Power on the system again, and then the board will boot from the NAND flash.