This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM385加载固件有时能成功,有时不能,希望能解答,谢谢

Other Parts Discussed in Thread: DM385

u-boot 和kernel的启动信息

U-Boot 2010.06 (Aug 10 2016 - 14:50:32) DM385_IPNC_3.80.00

DM385-GP rev 1.1

ARM clk: 600MHz
DDR clk: 400MHz
L3 clk: 200MHz
IVA clk: 220MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF

DRAM: 512 MiB
DCACHE: Off
MMC: OMAP SD/MMC: 0, ON-BOARD SDIO: 1
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till DM385_IPNC prompt if 2nd stage is already flashed
Hit any key to stop autoboot: 0
reading u-boot

188132 bytes read
## Starting application at 0x80800000 ...


U-Boot 2010.06 (Aug 10 2016 - 14:51:04) DM385_IPNC_3.80.00

DM385-GP rev 1.1

ARM clk: 600MHz
DDR clk: 400MHz
L3 clk: 200MHz
IVA clk: 220MHz
ISS clk: 400MHz
DSP Default OFF
DSS Default OFF

DRAM: 512 MiB
DCACHE: On
NAND: HW ECC BCH8 Selected
128 MiB
MMC: OMAP SD/MMC: 0, ON-BOARD SDIO: 1
*** Warning - bad CRC or MMC, using default environment

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@ @@
@@ @@
@@ @@
@@ @@
@@ @@@ @. @. @@@@ @@@@ G@@@@@@ @@
@@ @@@@@ L@@ @@@ @@@@@@ @@@@@i @@@@@@ @@
@@ @@ @@@. @@@ @@@ @@ @, @@ :@@ @@
@@ @@ @@ @@@ @@@ @@@@ @@;@@: C@@@@@. @@
@@ @@ @@ @@@.l@L@ G@@@ ,@@@@ @@@ @@ @@
@@ @@ @@ l@ @@@@ @. l@@ @@ L@@ @ G@ @@
@@ @@ @@ @@ @@@@ @@ @@ C@ @@ @@ @@
@@ @@ ,@C @@ @@@ @@ @i @@ C@ @@ @@ @@ @@
@@ @@@@@@@ @@ @@ @@ @@@@@l @@@@@@ L@@@@@ @@
@@ @@@@@ @ @ @ L@@ @@@, ,@@G @@
@@ @@
@@ @@
@@ @@
@@ @@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Net: Ethernet clocking: 0x52
<ethaddr> not set. Reading from E-fuse
Detected MACID:d0:b5:c2:12:7c:c8
cpsw
Hit any key to stop autoboot: 0
reading uImage

2380200 bytes read
reading ramdisk.img.gz

3524840 bytes read
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.37_DM385_IPNC_3.80.00
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2380136 Bytes = 2.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Linux version 2.6.37_DM385_IPNC_3.80.00 (sangws@EmbedServer) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #9 Wed Aug 3 18:13:50 CST 2016
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: dmipc385hdsdi
ti81xx_reserve: ### Reserved DDR region @84f00000
reserved size = 4194304 at 0x0
FB: Reserving 4194304 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is DM385 1.0
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 19040
Kernel command line: mem=80M@0x80000000 console=ttyO0,115200n8 initrd=0x81300000,0x800000 root=/dev/ram init=/init notifyk.vpssm3_sva=0x9FD00000 cmemk.phys_start=0x85000000 cmemk.phys_end=0x89000000 cmemk.allowOverlap=1 ip=192.168.168.81:192.168.168.91:192.168.168.1:255.255.255.0:eth0:off eth=d0:b5:c2:12:7c:c8
cpsw: kernel boot params Ethernet address: d0:b5:c2:12:7c:c8
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: 74MB 1MB = 75MB total
Memory: 62700k/62700k available, 19220k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc5800000 - 0xf8000000 ( 808 MB)
lowmem : 0xc0000000 - 0xc5000000 ( 80 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003d000 ( 212 kB)
.text : 0xc003d000 - 0xc0488000 (4396 kB)
.data : 0xc0488000 - 0xc04c6640 ( 250 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:375
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ368
Trying to install interrupt handler for IRQ369
Trying to install interrupt handler for IRQ370
Trying to install interrupt handler for IRQ371
Trying to install interrupt handler for IRQ372
Trying to install interrupt handler for IRQ373
Trying to install interrupt handler for IRQ374
Trying to install type control for IRQ375
Trying to set irq flags for IRQ375
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
TI81XX: Map 0x84f00000 to 0xfe500000 for dram barrier
TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
ti81xx_register_mcasp: platform not supported
_omap_mux_init_gpio: Could not set gpio36
omap2_mcspi2_init 684=========>
Cannot clk_get ck_32
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
bio: create slab <bio-0> at 0
SCSI subsystem initialized
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 8192K
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
msgmni has been set to 138
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
CMEMK module: built on Jul 11 2016 at 17:06:39
Reference Linux version 2.6.37
File /home/sangws/385/Source/ti_tools/linuxutils_3_23_00_01/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
allocated heap buffer 0xc7000000 of size 0x4000000
cmemk initialized
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
brd: module loaded
loop: module loaded
omap2-nand driver initializing
ONFI param page 0 valid
ONFI flash detected
NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
omap2-nand: detected x8 NAND flash
Creating 9 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000040000 : "ubl"
0x000000040000-0x0000000c0000 : "u-boot"
0x0000000c0000-0x0000000e0000 : "env"
0x000000100000-0x000000400000 : "Kernel"
0x000000400000-0x000000c00000 : "rootfs"
0x000000c00000-0x000001000000 : "conf"
0x000001000000-0x000001700000 : "log"
0x000001700000-0x000004700000 : "apps"
0x000004700000-0x000008000000 : "buffer"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff8
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver Micrel KS8041
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver Micrel KS8041
davinci_mdio davinci_mdio.0: phy[2]: device 0:02, driver Micrel KS8041
mice: PS/2 mouse device common for all mice
rtc-pcf8563 1-0051: chip found, driver version 0.4.3
rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
notify_shm_drv: no DSP present (MULTIPROC_INVALIDID)
notify_init : notify drivercreated for remote proc id 1 at physical Address 0x9fd00000
cm: Module associated with clock hdmi_i2s_fck didn't enable in 100000 tries
ALSA device list:
No soundcards found.
nf_conntrack version 0.5.0 (1107 buckets, 4428 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
Bridge firewalling registered
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=d0:b5:c2:12:7c:c8
Detected MACID=d0:b5:c2:12:7c:c9
rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
rtc-pcf8563 1-0051: setting system clock to 2016-08-11 17:51:23 UTC (1470937883)
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
devtmpfs: mounted
Freeing init memory: 212K
Failed to execute /init. Attempting defaults...
Root filesystem version: V0.1.0-RC1
Mounting filesystems...
Mounting tmpfs...
udevd (70): /proc/70/oom_adj is deprecated, please use /proc/70/oom_score_adj instead.
Mounting apps...
UBI: attaching mtd7 to ubi7
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 1664
UBI: attached mtd7 to ubi7
UBI: MTD device name: "apps"
UBI: MTD device size: 48 MiB
UBI: number of good PEBs: 384
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 384
UBI: number of PEBs reserved for bad PEB handling: 3
UBI: max/mean erase counter: 7/4
UBI: image sequence number: -460817701
UBI: background thread "ubi_bgt7d" started, PID 80
UBI device number 7, total 384 LEBs (48758784 bytes, 46.5 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 7, volume 0, name "apps"
UBIFS: file system size: 46727168 bytes (45632 KiB, 44 MiB, 368 LEBs)
UBIFS: journal size: 2285568 bytes (2232 KiB, 2 MiB, 18 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 2207039 bytes (2155 KiB)
Mounting configs...
UBI: attaching mtd5 to ubi5
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 523
UBI: attached mtd5 to ubi5
UBI: MTD device name: "conf"
UBI: MTD device size: 4 MiB
UBI: number of good PEBs: 32
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 32
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 33/17
UBI: image sequence number: -1861104621
UBI: background thread "ubi_bgt5d" started, PID 94
UBI device number 5, total 32 LEBs (4063232 bytes, 3.9 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 5, volume 0, name "conf"
UBIFS: file system size: 2158592 bytes (2108 KiB, 2 MiB, 17 LEBs)
UBIFS: journal size: 1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 101955 bytes (99 KiB)
Mounting logs...
UBI: attaching mtd6 to ubi6
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 189
UBI: attached mtd6 to ubi6
UBI: MTD device name: "log"
UBI: MTD device size: 7 MiB
UBI: number of good PEBs: 56
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 56
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 5/4
UBI: image sequence number: -127332487
UBI: background thread "ubi_bgt6d" started, PID 107
UBI device number 6, total 56 LEBs (7110656 bytes, 6.8 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 6, volume 0, name "log"
UBIFS: file system size: 5206016 bytes (5084 KiB, 4 MiB, 41 LEBs)
UBIFS: journal size: 1015809 bytes (992 KiB, 0 MiB, 6 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 245892 bytes (240 KiB)
Mounting buffer...
UBI: attaching mtd8 to ubi8
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 189
UBI: attached mtd8 to ubi8
UBI: MTD device name: "buffer"
UBI: MTD device size: 57 MiB
UBI: number of good PEBs: 456
UBI: number of bad PEBs: 0
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 456
UBI: number of PEBs reserved for bad PEB handling: 4
UBI: max/mean erase counter: 2/1
UBI: image sequence number: -1432780803
UBI: background thread "ubi_bgt8d" started, PID 119
UBI device number 8, total 456 LEBs (57901056 bytes, 55.2 MiB), available 0 LEBs (0 bytes), LEB size 126976 bytes (124.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 8, volume 0, name "buffer"
UBIFS: file system size: 55742464 bytes (54436 KiB, 53 MiB, 439 LEBs)
UBIFS: journal size: 2793472 bytes (2728 KiB, 2 MiB, 22 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 2632854 bytes (2571 KiB)
Config ethernet setting...
ip= 192.168.168.232

CPSW phy found : id is : 0x221513
Prepare files for vsftpd...
Warning: MTD partition named "apps" not initialed!!!
/etc/init.d/rcS: line 390: ./server.bin: not found
/etc/init.d/rcS: line 400: ./autorun.sh1: not found
rcS done!

DM368 login: PHY: 0:01 - Link is Up - 100/Full

DM368 login:
DM368 login:

M3固件编译条件为

IPNC_DEVICE    := DM385

IPNC_CONFIG := LOW_POWER

TEARDOWN_LOAD_UNLOAD := YES

/opt/ipnc/init.sh初始化信息为

chmod +x *.sh
chmod +x ./bin/*.out
chmod +x ./scripts/*.sh

rmmod ./kermod/syslink.ko 2> /dev/null
rmmod ./kermod/osa_kermod.ko 2> /dev/null
rmmod ./kermod/TI81xx_hdmi.ko 2> /dev/null
rmmod ./kermod/cmemk.ko 2> /dev/null

killall ./bin/fw_load.out 2> /dev/null
killall ./bin/remote_debug_client.out 2> /dev/null

sleep 1

./bin/remote_debug_client.out 0x9ff00000 &

insmod ./kermod/syslink.ko TRACE=1 TRACEFAILURE=1 2> /dev/null
sleep 1

./linux_prcm_ipcam r

#
# Format of the system priority setting utility for setting bandwidth regulator
#
# ./bin/sys_pri.out --L3-bw-reg-set <L3-bw-reg-initiator-name> <L3-pressure-High> <L3-pressure-Low> <L3-Bandwidth> <L3-Watermark-cycles>
#
# "L3-bw-reg-initiator-name" can be HDVICP0 or HDVICP1 or HDVICP2 or other initiators
# "L3-pressure-High" can be 0 (low), 1 (medium), 3 (high)
# "L3-pressure-Low" can be 0 (low), 1 (medium), 3 (high)
# "L3-Bandwidth" is in MB/s
# "L3-Watermark-cycles" is in bytes
#
# See also ./bin/sys_pri.out --help for more details
#
# IVA-HD BW requlator programing.
# TODO. THIS IS CURRENTLY HARDCODED.
# THIS SHOULD CALCULATED FROM EXPECTED IVA BANDWIDTH USAGE
#
# IVA-HD0, IVA-HD1, IVA-HD2
./bin/sys_pri.out --L3-bw-reg-set HDVICP0 0 0 900 2500&
./bin/sys_pri.out --L3-bw-reg-set ISS 3 3 400 2500&
./bin/sys_pri.out --dmm-pri-set ISS 0&
./bin/sys_pri.out --dmm-pri-set HDVICP0 1&

./scripts/load_vpss.sh &
./scripts/load_video.sh &
./scripts/wait_cmd.sh s m3vpss
./scripts/wait_cmd.sh s m3video
./scripts/osa_kermod_load.sh&

执行init.sh后日志信息如下

root$ ./init.sh
[c6xdsp ] Remote Debug Shared Memory @ 0x9ff00000
[m3video] Remote Debug Shared Memory @ 0x9ff05020
[m3vpss ] Remote Debug Shared Memory @ 0x9ff0a040
SysLink version : 2.21.02.10
SysLink module created on Date:Aug 11 2016 Time:17:03:01
Trace enabled
Trace SetFailureReason enabled
/dev/mem opened.
Phy Addr : 0x48181560 Data : 0x00000002
Phy Addr : 0x48180f10 Data : 0x00000000
Phy Addr : 0x48180508 Data : 0x00000302
Phy Addr : 0x48180520 Data : 0x00000002
Phy Addr : 0x48180524 Data : 0x00000002
Phy Addr : 0x48180528 Data : 0x00000002
Phy Addr : 0x4c0000e4 Data : 0x0000000c
Phy Addr : 0x4c0000e4 Data : 0x0010000c
DDR IOs RX is shutdown
Phy Addr : 0x48180a04 Data : 0x00000000
Phy Addr : 0x48180e00 Data : 0x00030000
Phy Addr : 0x48180e10 Data : 0x00000007
Phy Addr : 0x48180e04 Data : 0x00000000
Phy Addr : 0x48180e14 Data : 0x00000000
Phy Addr : 0x48180800 Data : 0x00000001
Phy Addr : 0x48180820 Data : 0x00070000
Phy Addr : 0x48180824 Data : 0x00030002
Phy Addr : 0x48180e04 Data : 0x00000000
Phy Addr : 0x48180e00 Data : 0x00030000
Phy Addr : 0x48180e10 Data : 0x00000007
Phy Addr : 0x48180e04 Data : 0x00000000
Phy Addr : 0x48180e14 Data : 0x00000000
Phy Addr : 0x48180800 Data : 0x00000001
Phy Addr : 0x48180820 Data : 0x00070000
Phy Addr : 0x48180824 Data : 0x00030002

[host] Setting L3 bandwidth regulator for [ISS ] to [press=[3,3] BW=400, WM Cycles=2500]

[host] Setting DMM priority for [ISS ] to [0] ( 0x4e000634 = 0x00080000 )

[host] Attached to slave procId 1.

[host] Setting DMM priority for [HDVICP0 ] to [1] ( 0x4e000634 = 0x00000009 )

[host] Setting L3 bandwidth regulator for [HDVICP0 ] to [press=[0,0] BW=900, WM Cycles=2500]
[c6xdsp ] Remote Debug Shared Memory @ 0x9ff00000
[m3video] Remote Debug Shared Memory @ 0x9ff05020
[m3vpss ] Remote Debug Shared Memory @ 0x9ff0a040

[host] Loaded file ./firmware/ipnc_rdk_fw_m3vpss.xem3 on slave procId 1.

[host] Started slave procId 1.

[host] After Ipc_loadcallback status [0x00000000]

[host] Attached to slave procId 0.
[m3vpss ] ***** SYSTEM : Frequency <ORG> - 200000000, <NEW> - 200000000
[m3vpss ] notify_attach rtnVal 0
[m3vpss ] initProxyServer rtnVal 0
[m3vpss ]
[m3vpss ] *** UTILS: CPU KHz = 400000 Khz ***
[m3vpss ]
[m3vpss ] 70: SYSTEM :ENTER System Common Init in progress-------> !!!
[m3vpss ] 70: SYSTEM: IPC init in progress !!!
[m3vpss ] 70: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 120: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 170: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 220: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 270: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 320: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 370: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 420: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 470: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 520: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 570: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 620: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 670: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 720: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 770: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 820: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 870: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 920: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 970: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1020: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1070: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1120: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1170: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1220: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1270: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1320: SYSTEM: Attaching to [HOST] ...

[host] Loaded file ./firmware/ipnc_rdk_fw_m3video.xem3 on slave procId 0.

[host] Started slave procId 0.

[host] After Ipc_loadcallback status [0x00000000]

[host] After Ipc_startcallback status [0x00000000]
[m3vpss ] 1420: SYSTEM: Attaching to [HOST] ...
[m3video] ***** SYSTEM : Frequency <ORG> - 200000000, <NEW> - 200000000
[m3video]
[m3video] *** UTILS: CPU KHz = 400000 Khz ***
[m3video]
[m3video] 1398: SYSTEM :ENTER System Common Init in progress-------> !!!
[m3video] 1398: SYSTEM: IPC init in progress !!!
[m3video] 1398: SYSTEM: Attaching to [HOST] ...
[m3video] 1448: SYSTEM: Attaching to [HOST] ...
[m3vpss ] 1448: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
[m3vpss ] 1448: SYSTEM: Attaching to [VIDEO-M3] ...

[host] After Ipc_startcallback status [0x00000000]
[m3vpss ] 1498: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1548: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1598: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1648: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1698: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1748: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1798: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1848: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1898: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1948: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 1998: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2048: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2098: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2148: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2198: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2248: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2298: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2348: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2398: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2448: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2498: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2548: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2598: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2648: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2698: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2748: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2798: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2848: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2898: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2948: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 2998: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3048: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3098: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3148: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3198: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3248: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3298: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3348: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3398: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3448: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3498: SYSTEM: Attaching to [VIDEO-M3] ...
[m3vpss ] 3548: SYSTEM: Attaching to [VIDEO-M3] ...
^Z[1]+ Stopped ./init.sh
root$

实在不知道这是什么原因了,启动十次,可能只有一次能成功,希望能给解答这个问题,谢谢!

  • 你好;

            你在程序里面是把 m3 固件加载了2次吧;

            在 init.sh 里面加载了一次;

            在ti_mcfw_ipnc_main.c 里面又加载了一次

  • Hi,

    I'm sorry to hijack your post but i need your help. As i was going through your log. It shows that you are using x8 bit NAND.

    对不起,劫持你的帖子,但我需要你的帮助。当我正在通过你的日志。它表明您正在使用x8位NAND。
    实际上我使用DM385 + IPNC RDK3.8 + Micron x8位NAND。
     我们从SD卡启动,但我们要检测x8 NAND在uboot以及在内核,但两方面我们得到错误的地址值。
    使用x16位NAND,我们不会面临任何问题。
    我需要一点帮助你可以你只是告诉我,你对你的uboot和内核检测NAND的变化是什么。 如果可能,你可以发送我的源代码与源代码链接。你必须做git pull。



    I'm not a chinese above is google translator. sorry if i made mistake.

    Actually i'm using DM385 + IPNC RDK3.8 + Micron x8 bit NAND. 

    We are booting from SD card but we want to detect x8 NAND  in uboot as well in kernel but both the side we are getting wrong address values. With x16 bit NAND we are not facing any issue.

    I need little help of yours can you just tell me what are the changes you made to your uboot and kernel to detect NAND.

    If possible can you send me diff of your source code with below source code link.  you have to do git pull.

    UBOOT  -> http://arago-project.org/git/projects/?p=u-boot-ipnc-rdk-dm81xx.git;a=summary
    KERNEL -> http://arago-project.org/git/projects/?p=linux-ipnc-rdk-dm81xx.git;a=summary

    Sorry once again.

    Thanks & regards,

    Ganesh