Dm8148 development record 1

Source: Internet
Author: User

Http://processors.wiki.ti.com/index.php/Category:DaVinci

Http://processors.wiki.ti.com/index.php/Category:DaVinci_Linux

Http://processors.wiki.ti.com/index.php/Category:EZSDK

Http://processors.wiki.ti.com/index.php/Category:DVSDK

Http://processors.wiki.ti.com/index.php/Category:OMX

First, when the collection program is enabled, this problem occurs: dm8148 vpss_grpx: Please open Fb1 node first

Burning mode:

Nand Boot Mode
Switch S1, S1[5:1] ==> 10010 , other pins should be 0 (i.e. OFF). This sets BTM[4:0] in NAND boot modeSwitch SW2---->NAND ON
SPI Boot Mode
Switch S1, S1[5:1] ==> 10110 , other pins should be 0 (i.e. OFF). This sets BTM[4:0] in SPI boot modeSwitch SW2---->SPI ON
UART Boot Mode
Switch S1, S1[5:1] ==> 00001 , other pins should be 0 (i.e. OFF). This sets BTM[4:0] in UART boot modeSwitch SW2---->NAND ON
SD Boot Mode
Switch S1, S1[5:1] ==> 10111 , other pins should be 0 (i.e. OFF). This sets BTM[4:0] in SD boot modeSwitch SW2----> Depending on where ENV storage is required enable the appropriate switch.
Nor Boot Mode
Switch S1, S1 [5] ==> 10000, S1 [8] ==> 1, other pins shoshould be 0 (I. e. off ). this sets BTM [] In nor boot modeswitch sw2 ----> NAND off, SPI off example: I also encountered this problem

/** Flashing first boot loader into NAND **/

Ti8148_evm # MMC rescan 0

Ti8148_evm # fatls MMC 0

Ti8148_evm # mW. B 0x81000000 0xff 0x20000

Ti8148_evm $ fatload MMC 0 0x81000000 MLO

Ti8148_evm # nandecc HW 2

Ti8148_evm # NAND erase 0x0 0x20000

Ti8148_evm # NAND write. I 0x81000000 0x0 0x20000

Ti8148_evm # nandecc HW 0

/** Flashing U-boot into NAND **/

Ti8148_evm # MMC rescan 0

Ti8148_evm # fatls MMC 0

Ti8148_evm # mW. B 0x81000000 0xff 0x20000

Ti8148_evm $ fatload MMC 0 0x81000000 u-boot.bin

Ti8148_evm # nandecc HW 0

Ti8148_evm # NAND erase 0x20000 0x60000

Ti8148_evm # NAND write. I 0x81000000 0x20000 0x60000

2. From userland (after root prompt up) using MTD utils

Root @ ti814x :~ #

Root @ ti814x :~ # Flash_erase/dev/mtd0 0 0

Erasing 128 kibyte @ 0 -- 100% complete

Root @ ti814x :~ # Flash_erase/dev/mtd1 0 0

Erasing 128 kibyte @ 1e0000 -- 100% complete

Root @ ti814x :~ # Flash_erase/dev/mtd4 0 0

Erasing 128 kibyte @ 3e0000 -- 100% complete

Root @ ti814x :~ # Nandwrite-P/dev/mtd0/Media/upload_mmc/MLO

Writing data to Block 0 at offset 0x0

Root @ ti814x :~ # Nandwrite-P/dev/mtd1/Media/upload_mmc/u-boot.bin

Writing data to Block 0 at offset 0x0

Writing data to block 1 at offset 0x20000

Root @ ti814x :~ # Nandwrite-P/dev/mtd4/Media/upload_mmc/uimage

Writing data to Block 0 at offset 0x0

Writing data to block 1 at offset 0x20000

Writing data to block 2 at offset 0x40000

.....

.....

Writing data to block 21 at offset 0x2a0000

After reebooting .....

Board is not booting. Just it get struck giving CCC in minicom window ..

Ccccccccccccccccc (here I get struck)

Now I switched to SD card Boot Mode and flashed only first boot loader ..

1. At U-boot level (using SD boot ..)

Ti8148_evm # MMC rescan 0

Ti8148_evm # mW. B 0x81000000 0xff 0x20000

Ti8148_evm # fatload MMC 0 0x81000000 MLO

Reading MLO

70544 bytes read

Ti8148_evm # nandecc HW 2

Hw ecc bch8 selected

Ti8148_evm # NAND erase 0x0 0x20000

Nand erase: device 0 offset 0x0, size 0x20000

Erasing at 0x0 -- 100% complete.

OK

Ti8148_evm # NAND write. I 0x81000000 0x0 0x20000

Nand write: device 0 offset 0x0, size 0x20000

131072 bytes written: OK

Ti8148_evm # nandecc HW 0

Hw ecc Hamming Code selected

Switch to NAND Boot Mode... reset the board ..

U-boot 2010.06 (May 13 2012-10:13:17)

TI8148-GP rev 2.1

Arm CLK: 600 MHz

Ddr clk: 400 MHz

I2C: Ready

DRAM: 2 Gib

Nand: hw ecc Hamming Code selected

256 MIB

* ** Warning-bad CRC or nand, using default environment

MMC: omap sd/MMC: 0

Net: <ethaddr> not set. Reading from e-Fuse

Detected macid: 90: D7: EB: C6: 3D: 66

Cpsw

Hit any key to stop autoboot: 0

Device 0 offset 0x240000, size 0x4

Nand read: device 0 offset 0x260000, size 0x400000

4194304 bytes read: OK

Booting from NAND

# Booting kernel from legacy image at 81000000...

Image name: montavista automotive technology

Image Type: ARM Linux kernel image (uncompressed)

Data size: 2814088 bytes = 2.7 MIB

Load address: 80008000

Entry Point: 80008000

Verifying checksum... OK

Loading kernel image... OK

OK

Starting kernel...

Uncompressing Linux... Done, booting the kernel.

Linux version 2.6.37.6.ps-110721-ti-jacstm5 (mallikarjuna @ mallikarjuna-desktop) (GCC version 4.4.1 (montavista Linux g ++ 4.4-111220) #7 preempt Thu May 17 11:48:07 ist 2012

CPU: armv7 processor [413fc082] Revision 2 (armv7), Cr = 10c53c7f

CPU: vipt nonaliasing data cache, vipt aliasing Instruction Cache

MACHINE: ti8148evm

VRAM size = 52428800 at 0x0

Reserved size = 52428800 at 0x0

FB: reserving 52428800 bytes SDRAM for VRAM

Memory Policy: ECC disabled, data cache writeback

OMAP chip is ti8148 2.0

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 30126

Kernel command line: Console = ttyo0, 115200 rootfstype = jffs2 root =/dev/mtdblock5 rootwait rw ip = :::: eth0: Off mem = 169 m notifyk. vpssm3_sva = 0xbf900000 VRAM = 50 m ti814xfb. VRAM = 0: 16 m, 1: 16 m, 2: 6 m

PID hash table entries: 512 (Order:-1, 2048 bytes)

Dentry cache hash table entries: 16384 (Order: 4, 65536 bytes)

Inode-Cache hash table entries: 8192 (Order: 3, 32768 bytes)

Memory: 119 MB = 119 MB total

Its booging and got the root prompt ..

Ti814x login: Root

Root @ ti814x :~ # L

.

Regards,

Mallikarjuna Reddy

Reference website

Http://processors.wiki.ti.com/index.php/TI81XX_PSP_U-Boot#EVM_Switch_Settings

Error # lnkv5t bin/ti_platforms_evmti814x/app_remote.xv5t... rm-F package/CFG/bin/ti_platforms_evmti814x/ app_remote.xv5t.map/opt/dm8148/arm-2009q1/bin/ARM-None-Linux-gnueabi-gcc-wl, -- GC-sections-O bin/samples/app_remote.xv5t package/CFG/bin/samples/app_remote_pv5t.ov5t package/CFG/bin/ti_platforms_evmti814x/app_remote/app. ov5t package/CFG/bin/ti_platforms_evmti814x/app_remote/main_native.ov5t-wl,-T, package/CFG/bin/logs/app_remote_pv5t.xdl-wl, -Map = package/CFG // bin/ti_platforms_evmti814x/app_remote.xv5t.map-L/opt/dm8148/arm-2009q1/ARM-None-Linux-gnueabi/lib-lpthread-LRT-LDL/opt/ dm8148/ezsdk/component-sources/codec_engine_3_22_01_06/packages/Ti/SDO/CE/osal/Linux/lib/release/osal_linux_470.av5t (loader_linux.ov5t): In function 'loader _ loadlibrary ': loader_linux.c :(. text. loader_loadlibrary + 0x68): Warning: using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking/opt/dm8148/arm-2009q1/ARM-None-Linux-gnueabi/lib/libdl. A (dlclose. o): In function 'dlclose': dlclose. c :(. text + 0x0): Undefined reference to '_ dlclose' collect2: LD returned 1 exit statusgmake [1]: *** [bin/ti_platforms_evmti814x/app_remote.xv5t] Error 1 gmake: * ** [/opt/dm8148/ezsdk/component-sources/codec_engine_3_22_01_06/examples/Ti/SDO/CE/examples/apps/video_copy,.exe cutables] Error 2 make: * ** [all] Error 2root @ Ubuntu: /opt/dm8148/ezsdk/component-sources/codec_engine_3_22_01_06/examples/Ti/SDO/CE/examples/apps/video_copy # solves cmemk. ko Loading Problem # setenv bootargs 'console = ttyo0, 115200n8 rootwait root =/dev/mmcblk0p2 RW mem = 120 m mem = 364m @ 0x80000000 mem = 320m @ 0x9fc00000 mem = 120 m vmalloc = 500 m notifyk yk. vpssm3_sva = 0xbf900000 IP = off noinitrd 'setenv bootargs 'console = ttyo0, 115200n8 root =/dev/mmcblk0p2 mem = 120 m rootwait vmalloc = 500 m notifyk yk. vpssm3_sva = 0xbf900000 IP = off noinitrd'

But I still don't quite understand

mem=364M@0x80000000 mem=320M@0x9FC00000

Meaning

Qt Problems

Root @ dm814x-evm :~ # Export tslib_tsdevice =/dev/input/event0
Root @ dm814x-evm :~ # Export qws_mouse_proto = "tslib:/dev/input/event0 Auto:/dev/indium
Ut/mice"
Root @ dm814x-evm :~ #

If the PIN is set, you can burn it from flash.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.