uBoot flash works, flash-upgrade doesn't
Home › Forums › MultiConnect OCG › uBoot flash works, flash-upgrade doesn't
- This topic has 11 replies, 2 voices, and was last updated 12 years, 4 months ago by Neil McGuire.
-
AuthorPosts
-
November 28, 2011 at 7:16 pm #2688Neil McGuireParticipant
I’m using CoreCDP 1.1.1, and have a jffs2 image, which when flashed from U-Boot as oe_rootfs.jffs2 works fine, but when flashed from the SD card as rootfs.jffs2 causes a kernel panic claiming that no init= was passed with the call to the kernel.
Any ideas as to what would cause it to work from U-Boot but not from the SD card?
November 28, 2011 at 8:29 pm #3560Jesse GillesBlockedHm, no that is odd. You’re certain it’s the same rootfs in both scenarios (check file size, checksum, etc)?
When you do the flashing from SD card, do you see any errors on the debug serial port?
November 29, 2011 at 5:32 pm #3561Neil McGuireParticipantFirst off, Sorry about the long post, but here’s what comes across the serial debug cable from run tftp_kernel through the login prompt
U-Boot>run tftp_kernel
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Using macb0 device
TFTP from server 192.168.2.2; our IP address is 192.168.2.1
Filename 'oe_uImage.bin'.
Load address: 0x21400000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####################################
done
Bytes transferred = 1851888 (1c41f0 hex)
NAND erase: device 0 offset 0xa0000, size 0x760000
Erasing at 0xa0000 -- 1% complete.Erasing at 0xc0000 -- 3% complete.Erasing at 0xe0000 -- 5% complete.Erasing at 0x100000 -- 6% complete.Erasing at 0x120000 -- 8% complete.Erasing at 0x140000 -- 10% complete.Erasing at 0x160000 -- 11% complete.Erasing at 0x180000 -- 13% complete.Erasing at 0x1a0000 -- 15% complete.Erasing at 0x1c0000 -- 16% complete.Erasing at 0x1e0000 -- 18% complete.Erasing at 0x200000 -- 20% complete.Erasing at 0x220000 -- 22% complete.Erasing at 0x240000 -- 23% complete.Erasing at 0x260000 -- 25% complete.Erasing at 0x280000 -- 27% complete.Erasing at 0x2a0000 -- 28% complete.Erasing at 0x2c0000 -- 30% complete.Erasing at 0x2e0000 -- 32% complete.Erasing at 0x300000 -- 33% complete.Erasing at 0x320000 -- 35% complete.Erasing at 0x340000 -- 37% complete.Erasing at 0x360000 -- 38% complete.Erasing at 0x380000 -- 40% complete.Erasing at 0x3a0000 -- 42% complete.Erasing at 0x3c0000 -- 44% complete.Erasing at 0x3e0000 -- 45% complete.Erasing at 0x400000 -- 47% complete.Erasing at 0x420000 -- 49% complete.Erasing at 0x440000 -- 50% complete.Erasing at 0x460000 -- 52% complete.Erasing at 0x480000 -- 54% complete.Erasing at 0x4a0000 -- 55% complete.Erasing at 0x4c0000 -- 57% complete.Erasing at 0x4e0000 -- 59% complete.Erasing at 0x500000 -- 61% complete.Erasing at 0x520000 -- 62% complete.Erasing at 0x540000 -- 64% complete.Erasing at 0x560000 -- 66% complete.Erasing at 0x580000 -- 67% complete.Erasing at 0x5a0000 -- 69% complete.Erasing at 0x5c0000 -- 71% complete.Erasing at 0x5e0000 -- 72% complete.Erasing at 0x600000 -- 74% complete.Erasing at 0x620000 -- 76% complete.Erasing at 0x640000 -- 77% complete.Erasing at 0x660000 -- 79% complete.Erasing at 0x680000 -- 81% complete.Erasing at 0x6a0000 -- 83% complete.Erasing at 0x6c0000 -- 84% complete.Erasing at 0x6e0000 -- 86% complete.Erasing at 0x700000 -- 88% complete.Erasing at 0x720000 -- 89% complete.Erasing at 0x740000 -- 91% complete.Erasing at 0x760000 -- 93% complete.Erasing at 0x780000 -- 94% complete.Erasing at 0x7a0000 -- 96% complete.Erasing at 0x7c0000 -- 98% complete.Erasing at 0x7e0000 -- 100% complete.
OK
NAND write: device 0 offset 0xa0000, size 0x1c41f0
Writing data at 0xa0000 -- 0% complete.Writing data at 0xa4800 -- 1% complete.Writing data at 0xa9000 -- 2% complete.Writing data at 0xad800 -- 3% complete.Writing data at 0xb2000 -- 4% complete.Writing data at 0xb6800 -- 5% complete.Writing data at 0xbb000 -- 6% complete.Writing data at 0xbf800 -- 7% complete.Writing data at 0xc4000 -- 8% complete.Writing data at 0xc8800 -- 9% complete.Writing data at 0xcd000 -- 10% complete.Writing data at 0xd1800 -- 11% complete.Writing data at 0xd6000 -- 12% complete.Writing data at 0xda800 -- 13% complete.Writing data at 0xdf000 -- 14% complete.Writing data at 0xe3800 -- 15% complete.Writing data at 0xe8000 -- 16% complete.Writing data at 0xec800 -- 17% complete.Writing data at 0xf1000 -- 18% complete.Writing data at 0xf5800 -- 19% complete.Writing data at 0xfa000 -- 20% complete.Writing data at 0xfe800 -- 21% complete.Writing data at 0x103000 -- 22% complete.Writing data at 0x107800 -- 23% complete.Writing data at 0x10c800 -- 24% complete.Writing data at 0x111000 -- 25% complete.Writing data at 0x115800 -- 26% complete.Writing data at 0x11a000 -- 27% complete.Writing data at 0x11e800 -- 28% complete.Writing data at 0x123000 -- 29% complete.Writing data at 0x127800 -- 30% complete.Writing data at 0x12c000 -- 31% complete.Writing data at 0x130800 -- 32% complete.Writing data at 0x135000 -- 33% complete.Writing data at 0x139800 -- 34% complete.Writing data at 0x13e000 -- 35% complete.Writing data at 0x142800 -- 36% complete.Writing data at 0x147000 -- 37% complete.Writing data at 0x14b800 -- 38% complete.Writing data at 0x150000 -- 39% complete.Writing data at 0x154800 -- 40% complete.Writing data at 0x159000 -- 41% complete.Writing data at 0x15d800 -- 42% complete.Writing data at 0x162000 -- 43% complete.Writing data at 0x166800 -- 44% complete.Writing data at 0x16b000 -- 45% complete.Writing data at 0x16f800 -- 46% complete.Writing data at 0x174000 -- 47% complete.Writing data at 0x179000 -- 48% complete.Writing data at 0x17d800 -- 49% complete.Writing data at 0x182000 -- 50% complete.Writing data at 0x186800 -- 51% complete.Writing data at 0x18b000 -- 52% complete.Writing data at 0x18f800 -- 53% complete.Writing data at 0x194000 -- 54% complete.Writing data at 0x198800 -- 55% complete.Writing data at 0x19d000 -- 56% complete.Writing data at 0x1a1800 -- 57% complete.Writing data at 0x1a6000 -- 58% complete.Writing data at 0x1aa800 -- 59% complete.Writing data at 0x1af000 -- 60% complete.Writing data at 0x1b3800 -- 61% complete.Writing data at 0x1b8000 -- 62% complete.Writing data at 0x1bc800 -- 63% complete.Writing data at 0x1c1000 -- 64% complete.Writing data at 0x1c5800 -- 65% complete.Writing data at 0x1ca000 -- 66% complete.Writing data at 0x1ce800 -- 67% complete.Writing data at 0x1d3000 -- 68% complete.Writing data at 0x1d7800 -- 69% complete.Writing data at 0x1dc000 -- 70% complete.Writing data at 0x1e1000 -- 71% complete.Writing data at 0x1e5800 -- 72% complete.Writing data at 0x1ea000 -- 73% complete.Writing data at 0x1ee800 -- 74% complete.Writing data at 0x1f3000 -- 75% complete.Writing data at 0x1f7800 -- 76% complete.Writing data at 0x1fc000 -- 77% complete.Writing data at 0x200800 -- 78% complete.Writing data at 0x205000 -- 79% complete.Writing data at 0x209800 -- 80% complete.Writing data at 0x20e000 -- 81% complete.Writing data at 0x212800 -- 82% complete.Writing data at 0x217000 -- 83% complete.Writing data at 0x21b800 -- 84% complete.Writing data at 0x220000 -- 85% complete.Writing data at 0x224800 -- 86% complete.Writing data at 0x229000 -- 87% complete.Writing data at 0x22d800 -- 88% complete.Writing data at 0x232000 -- 89% complete.Writing data at 0x236800 -- 90% complete.Writing data at 0x23b000 -- 91% complete.Writing data at 0x23f800 -- 92% complete.Writing data at 0x244000 -- 93% complete.Writing data at 0x248800 -- 94% complete.Writing data at 0x24d800 -- 95% complete.Writing data at 0x252000 -- 96% complete.Writing data at 0x256800 -- 97% complete.Writing data at 0x25b000 -- 98% complete.Writing data at 0x25f800 -- 99% complete.Writing data at 0x264000 -- 100% complete.
1851888 bytes written: OK
U-Boot> run tftp_rootfs
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Using macb0 device
TFTP from server 192.168.2.2; our IP address is 192.168.2.1
Filename 'oe_rootfs.jffs2'.
Load address: 0x21400000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
######################
done
Bytes transferred = 10092544 (9a0000 hex)
NAND erase: device 0 offset 0x1800000, size 0xe800000
Erasing at 0x1800000 -- 0% complete.Erasing at 0x1a40000 -- 1% complete.Erasing at 0x1ca0000 -- 2% complete.Erasing at 0x1ee0000 -- 3% complete.Erasing at 0x2140000 -- 4% complete.Erasing at 0x2380000 -- 5% complete.Erasing at 0x25e0000 -- 6% complete.Erasing at 0x2820000 -- 7% complete.Erasing at 0x2a80000 -- 8% complete.Skipping bad block at 0x02be0000
Erasing at 0x2ce0000 -- 9% complete.Erasing at 0x2f20000 -- 10% complete.Erasing at 0x3180000 -- 11% complete.Erasing at 0x33c0000 -- 12% complete.Erasing at 0x3620000 -- 13% complete.Erasing at 0x3860000 -- 14% complete.Erasing at 0x3ac0000 -- 15% complete.Erasing at 0x3d00000 -- 16% complete.Erasing at 0x3f60000 -- 17% complete.Erasing at 0x41c0000 -- 18% complete.Erasing at 0x4400000 -- 19% complete.Erasing at 0x4660000 -- 20% complete.Erasing at 0x48a0000 -- 21% complete.Erasing at 0x4b00000 -- 22% complete.Erasing at 0x4d40000 -- 23% complete.Erasing at 0x4fa0000 -- 24% complete.Erasing at 0x51e0000 -- 25% complete.Erasing at 0x5440000 -- 26% complete.Erasing at 0x56a0000 -- 27% complete.Erasing at 0x58e0000 -- 28% complete.Erasing at 0x5b40000 -- 29% complete.Erasing at 0x5d80000 -- 30% complete.Erasing at 0x5fe0000 -- 31% complete.Erasing at 0x6220000 -- 32% complete.Erasing at 0x6480000 -- 33% complete.Erasing at 0x66e0000 -- 34% complete.Erasing at 0x6920000 -- 35% complete.Erasing at 0x6b80000 -- 36% complete.Erasing at 0x6dc0000 -- 37% complete.Erasing at 0x7020000 -- 38% complete.Erasing at 0x7260000 -- 39% complete.Erasing at 0x74c0000 -- 40% complete.Erasing at 0x7700000 -- 41% complete.Erasing at 0x7960000 -- 42% complete.Erasing at 0x7bc0000 -- 43% complete.Erasing at 0x7e00000 -- 44% complete.Erasing at 0x8060000 -- 45% complete.Erasing at 0x82a0000 -- 46% complete.Erasing at 0x8500000 -- 47% complete.Erasing at 0x8740000 -- 48% complete.Erasing at 0x89a0000 -- 49% complete.Skipping bad block at 0x08be0000
Erasing at 0x8c00000 -- 50% complete.Erasing at 0x8e40000 -- 51% complete.Erasing at 0x90a0000 -- 52% complete.Erasing at 0x92e0000 -- 53% complete.Erasing at 0x9540000 -- 54% complete.Erasing at 0x9780000 -- 55% complete.Erasing at 0x99e0000 -- 56% complete.Erasing at 0x9c20000 -- 57% complete.Erasing at 0x9e80000 -- 58% complete.Erasing at 0xa0e0000 -- 59% complete.Erasing at 0xa320000 -- 60% complete.Erasing at 0xa580000 -- 61% complete.Erasing at 0xa7c0000 -- 62% complete.Erasing at 0xaa20000 -- 63% complete.Erasing at 0xac60000 -- 64% complete.Erasing at 0xaec0000 -- 65% complete.Erasing at 0xb100000 -- 66% complete.Erasing at 0xb360000 -- 67% complete.Erasing at 0xb5c0000 -- 68% complete.Erasing at 0xb800000 -- 69% complete.Erasing at 0xba60000 -- 70% complete.Erasing at 0xbca0000 -- 71% complete.Erasing at 0xbf00000 -- 72% complete.Erasing at 0xc140000 -- 73% complete.Erasing at 0xc3a0000 -- 74% complete.Erasing at 0xc5e0000 -- 75% complete.Erasing at 0xc840000 -- 76% complete.Erasing at 0xcaa0000 -- 77% complete.Erasing at 0xcce0000 -- 78% complete.Erasing at 0xcf40000 -- 79% complete.Erasing at 0xd180000 -- 80% complete.Erasing at 0xd3e0000 -- 81% complete.Erasing at 0xd620000 -- 82% complete.Erasing at 0xd880000 -- 83% complete.Erasing at 0xdae0000 -- 84% complete.Erasing at 0xdd20000 -- 85% complete.Erasing at 0xdf80000 -- 86% complete.Erasing at 0xe1c0000 -- 87% complete.Erasing at 0xe420000 -- 88% complete.Erasing at 0xe660000 -- 89% complete.Erasing at 0xe8c0000 -- 90% complete.Erasing at 0xeb00000 -- 91% complete.Erasing at 0xed60000 -- 92% complete.Erasing at 0xefc0000 -- 93% complete.Erasing at 0xf200000 -- 94% complete.Erasing at 0xf460000 -- 95% complete.Erasing at 0xf6a0000 -- 96% complete.Erasing at 0xf900000 -- 97% complete.Erasing at 0xfb40000 -- 98% complete.Erasing at 0xfda0000 -- 99% complete.Erasing at 0xffe0000 -- 100% complete.
OK
NAND write: device 0 offset 0x1800000, size 0x9a0000
Writing data at 0x1800000 -- 0% complete.Writing data at 0x1818800 -- 1% complete.Writing data at 0x1831000 -- 2% complete.Writing data at 0x1849800 -- 3% complete.Writing data at 0x1862800 -- 4% complete.Writing data at 0x187b000 -- 5% complete.Writing data at 0x1893800 -- 6% complete.Writing data at 0x18ac000 -- 7% complete.Writing data at 0x18c5000 -- 8% complete.Writing data at 0x18dd800 -- 9% complete.Writing data at 0x18f6000 -- 10% complete.Writing data at 0x190f000 -- 11% complete.Writing data at 0x1927800 -- 12% complete.Writing data at 0x1940000 -- 13% complete.Writing data at 0x1958800 -- 14% complete.Writing data at 0x1971800 -- 15% complete.Writing data at 0x198a000 -- 16% complete.Writing data at 0x19a2800 -- 17% complete.Writing data at 0x19bb800 -- 18% complete.Writing data at 0x19d4000 -- 19% complete.Writing data at 0x19ec800 -- 20% complete.Writing data at 0x1a05000 -- 21% complete.Writing data at 0x1a1e000 -- 22% complete.Writing data at 0x1a36800 -- 23% complete.Writing data at 0x1a4f000 -- 24% complete.Writing data at 0x1a67800 -- 25% complete.Writing data at 0x1a80800 -- 26% complete.Writing data at 0x1a99000 -- 27% complete.Writing data at 0x1ab1800 -- 28% complete.Writing data at 0x1aca800 -- 29% complete.Writing data at 0x1ae3000 -- 30% complete.Writing data at 0x1afb800 -- 31% complete.Writing data at 0x1b14000 -- 32% complete.Writing data at 0x1b2d000 -- 33% complete.Writing data at 0x1b45800 -- 34% complete.Writing data at 0x1b5e000 -- 35% complete.Writing data at 0x1b77000 -- 36% complete.Writing data at 0x1b8f800 -- 37% complete.Writing data at 0x1ba8000 -- 38% complete.Writing data at 0x1bc0800 -- 39% complete.Writing data at 0x1bd9800 -- 40% complete.Writing data at 0x1bf2000 -- 41% complete.Writing data at 0x1c0a800 -- 42% complete.Writing data at 0x1c23800 -- 43% complete.Writing data at 0x1c3c000 -- 44% complete.Writing data at 0x1c54800 -- 45% complete.Writing data at 0x1c6d000 -- 46% complete.Writing data at 0x1c86000 -- 47% complete.Writing data at 0x1c9e800 -- 48% complete.Writing data at 0x1cb7000 -- 49% complete.Writing data at 0x1ccf800 -- 50% complete.Writing data at 0x1ce8800 -- 51% complete.Writing data at 0x1d01000 -- 52% complete.Writing data at 0x1d19800 -- 53% complete.Writing data at 0x1d32800 -- 54% complete.Writing data at 0x1d4b000 -- 55% complete.Writing data at 0x1d63800 -- 56% complete.Writing data at 0x1d7c000 -- 57% complete.Writing data at 0x1d95000 -- 58% complete.Writing data at 0x1dad800 -- 59% complete.Writing data at 0x1dc6000 -- 60% complete.Writing data at 0x1ddf000 -- 61% complete.Writing data at 0x1df7800 -- 62% complete.Writing data at 0x1e10000 -- 63% complete.Writing data at 0x1e28800 -- 64% complete.Writing data at 0x1e41800 -- 65% complete.Writing data at 0x1e5a000 -- 66% complete.Writing data at 0x1e72800 -- 67% complete.Writing data at 0x1e8b800 -- 68% complete.Writing data at 0x1ea4000 -- 69% complete.Writing data at 0x1ebc800 -- 70% complete.Writing data at 0x1ed5000 -- 71% complete.Writing data at 0x1eee000 -- 72% complete.Writing data at 0x1f06800 -- 73% complete.Writing data at 0x1f1f000 -- 74% complete.Writing data at 0x1f37800 -- 75% complete.Writing data at 0x1f50800 -- 76% complete.Writing data at 0x1f69000 -- 77% complete.Writing data at 0x1f81800 -- 78% complete.Writing data at 0x1f9a800 -- 79% complete.Writing data at 0x1fb3000 -- 80% complete.Writing data at 0x1fcb800 -- 81% complete.Writing data at 0x1fe4000 -- 82% complete.Writing data at 0x1ffd000 -- 83% complete.Writing data at 0x2015800 -- 84% complete.Writing data at 0x202e000 -- 85% complete.Writing data at 0x2047000 -- 86% complete.Writing data at 0x205f800 -- 87% complete.Writing data at 0x2078000 -- 88% complete.Writing data at 0x2090800 -- 89% complete.Writing data at 0x20a9800 -- 90% complete.Writing data at 0x20c2000 -- 91% complete.Writing data at 0x20da800 -- 92% complete.Writing data at 0x20f3800 -- 93% complete.Writing data at 0x210c000 -- 94% complete.Writing data at 0x2124800 -- 95% complete.Writing data at 0x213d000 -- 96% complete.Writing data at 0x2156000 -- 97% complete.Writing data at 0x216e800 -- 98% complete.Writing data at 0x2187000 -- 99% complete.Writing data at 0x219f800 -- 100% complete.
10092544 bytes written: OK
U-Boot> boot
Loading from NAND 256MiB 3,3V 8-bit, offset 0xa0000
Image Name: CoreCDP/2.6.32/mtcdp
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1851824 Bytes = 1.8 MB
Load Address: 20008000
Entry Point: 20008000
## Booting kernel from Legacy Image at 21400000 ...
Image Name: CoreCDP/2.6.32/mtcdp
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1851824 Bytes = 1.8 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux..................................................................................................................... done, booting the kernel.
Linux version 2.6.32.3 (nmcguire@REL-UBU01) (gcc version 4.3.3 (GCC) ) #1 PREEMPT Fri Nov 18 10:19:05 PST 2011
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Atmel AT91SAM9G20-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz
sam9g20: i2c available
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: mem=64M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61108KB available (3292K code, 241K data, 132K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:192
AT91: 96 gpio irqs in 3 banks
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating delay loop... 197.83 BogoMIPS (lpj=989184)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
AT91: Power Management (with slow clock mode)
AT91: Starting after power-restored wakeup
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource tcb_clksrc
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
msgmni has been set to 119
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
atmel_usart.3: ttyS3 at MMIO 0xfffd0000 (irq = 23) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 351 at 0x000002be0000
Bad eraseblock 1119 at 0x000008be0000
Creating 9 MTD partitions on "atmel_nand":
0x000000000000-0x000010000000 : "MTNCG-NANDFlash"
0x000000000000-0x000000020000 : "AT91Bootstrap"
0x000000020000-0x000000060000 : "UBoot"
0x000000060000-0x000000080000 : "UBoot Config"
0x000000080000-0x0000000a0000 : "UBoot Redundant Config"
0x0000000a0000-0x000000800000 : "uImage"
0x000000800000-0x000001000000 : "Config"
0x000001000000-0x000001800000 : "Oem Config"
0x000001800000-0x000010000000 : "Rootfs"
atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffc8000 (irq 12)
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:08:00:87:2d:42)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
usbmon: debugfs is not available
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: AT91 OHCI
usb usb1: Manufacturer: Linux 2.6.32.3 ohci_hcd
usb usb1: SerialNumber: at91
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
IRQ 1/rtc0: IRQF_DISABLED is not guaranteed on shared IRQs
i2c /dev entries driver
at24 0-0056: 512 byte 24c04 EEPROM (writable)
sam9g20: read 512 bytes from id eeprom
i2c-gpio i2c-gpio: using pins 55 (SDA) and 56 (SCL)
AT91SAM9 Watchdog: sorry, watchdog is disabled
at91_wdt: probe of at91_wdt failed with error -5
Registered led device: status
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (955 buckets, 3820 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
rtc-at91sam9 at91_rtt.0: setting system clock to 2011-11-29 17:37:54 UTC (1322588274)
JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
VFS: Mounted root (jffs2 filesystem) readonly on device 31:8.
Freeing init memory: 132K
INIT: version 2.86 booting
Please wait: booting...
mount: sysfs already mounted or /sys busy
mount: according to mtab, sysfs is already mounted on /sys
Starting udev
Remounting root file system...
Caching udev devnodes
Mounting /var/config
JFFS2 notice: (1205) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Creating link to /var/config/network/interfaces
Creating link to /var/config/ppp/options
Creating link to /var/config/ppp/pap-secrets
Creating link to /var/config/ppp/chap-secrets
Creating link to /var/config/ppp/peers
Creating link to /var/config/passwd
Creating link to /var/config/group
root: mount: you must specify the filesystem type
Configuring network interfaces... done.
Setting up IP spoofing protection: rp_filter.
Loading mts-io module
[INFO] mts-io:mts_io_init:1827: init: v0.4.1
[INFO] mts-io:mts_id_eeprom_load:300: sizeof: 512
[INFO] mts-io:mts_id_eeprom_load:301: vendor-id: Multi-Tech Systems
[INFO] mts-io:mts_id_eeprom_load:302: product-id: MTCDP-G2-DK
[INFO] mts-io:mts_id_eeprom_load:303: device-id: 15292153
[INFO] mts-io:mts_id_eeprom_load:304: hw-version: MTCDP-1.0
[INFO] mts-io:mts_id_eeprom_load:311: mac-addr: 00:08:00:87:2D:42
[INFO] mts-io:mts_id_eeprom_load:312: imei: 011998000089393
[INFO] mts-io:mts_id_eeprom_load:313: capa-gps: yes
[INFO] mts-io:mts_id_eeprom_load:314: capa-din: yes
[INFO] mts-io:mts_id_eeprom_load:315: capa-dout: yes
[INFO] mts-io:mts_id_eeprom_load:316: capa-adc: yes
Configuring ppp
Configuring seriallink
Registering serialLink for automatic startup
Registering server in /etc/hosts
Registring with crontab
Configuring ntpdate
adding crontab
Configuring update-modules
eth0: link up (100/Full)
INIT: Entering runlevel: 5
Creating Dropbear SSH server RSA host key.
Will output 1024 bit rsa secret key to '/etc/dropbear/dropbear_rsa_host_key'
Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgwCXjuU04sekPpb+DbxAj+akWlf5pnebMo9iNk9hT4xhC/nN2DuDoqeKqfhE2ycWOhZTW0VhBc8J361uIe9qN20pU6r21X8vIH+7KM6M8Wx4ylGMoUueaX5moe+l1uBV8pMfwbMrIw9DnYTgf59vQNPAP9TZc8NWY90IAgM1/ABsG9aP root@mtcdp
Fingerprint: md5 02:d8:38:e7:7a:d0:67:71:3b:80:02:4f:d2:18:7a:53
Starting Dropbear SSH server: dropbear.
Starting Vixie-cron.
Starting syslogd/klogd: done
Loading [g_serial]
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
Starting tftp daemon: atftpd.
_____ _____ _____ _____
/ ____| / ____| __ | __
| | ___ _ __ ___| | | | | | |__) |
| | / _ | '__/ _ | | | | | ___/
| |____| (_) | | | __/ |____| |__| | |
_____|___/|_| ___|_____|_____/|_|
Multi-Tech Systems CoreCDP Distribution mtcdp ttyS0
CoreCDP 1.1.1 mtcdp ttyS0
mtcdp login:November 29, 2011 at 5:33 pm #3562Neil McGuireParticipantAnd here’s what the SD Card load generates:
#reboot
Broadcast message from root (ttyS0) (Tue Nov 29 11:39:07 2011):
The system is going down for reboot NOW!
INIT: SwitchingINIT: Sending processes the TERM signal
# INIT: Sending proceStopping Dropbear SSH server: stopped /usr/sbin/dropbear (pid 1469)
dropbear.
Stopping Vixie-cron.
Stopping syslogd/klogd: stopped syslogd (pid 1475)
stopped klogd (pid 1477)
done
Deconfiguring network interfaces... done.
Stopping tftp daemon: atftpd.
Sending all processes the TERM signal...
eth0: link down
Sending all processes the KILL signal...
Unmounting remote filesystems...
/var/volatile/flash-upgrade not present, skipping
Flashing /dev/mtd8 (rootfs) with /media/card/flash-upgrade/rootfs.jffs2...
Deactivating swap...
Unmounting local filesystems...
umount2: Device or resource busy
umount: none busy - remounted read-only
Erasing 128 Kibyte @ 13c0000 -- 8 % complete. Cleanmarker written at 13c0000.
Skipping bad block at 0x013e0000
Erasing 128 Kibyte @ 73c0000 -- 49 % complete. Cleanmarker written at 73c0000.
Skipping bad block at 0x073e0000
Erasing 128 Kibyte @ e800000 -- 100 % complete.
Input file is not page-aligned. Use the padding option.
Data was only partially written due to error
: Success
Remember to clean-up /media/card/flash-upgrade after reboot
Rebooting...
Restarting system.
RomBOOT
*** AT91Bootstrap-2.13
NAND id:0x00002CDA
> From: [0x00020000] To: [0x23F00000] Size: [0x00040000]
> SUCCESS
> Start: [0x23F00000]
U-Boot 1.3.4 (Jan 5 2011 - 14:34:55)
DRAM: 64 MB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: macb0
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Hit any key to stop autoboot: 3 2 1 0
Loading from NAND 256MiB 3,3V 8-bit, offset 0xa0000
Image Name: CoreCDP/2.6.32/mtcdp
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1851824 Bytes = 1.8 MB
Load Address: 20008000
Entry Point: 20008000
## Booting kernel from Legacy Image at 21400000 ...
Image Name: CoreCDP/2.6.32/mtcdp
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1851824 Bytes = 1.8 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux..................................................................................................................... done, booting the kernel.
Linux version 2.6.32.3 (nmcguire@REL-UBU01) (gcc version 4.3.3 (GCC) ) #1 PREEMPT Fri Nov 18 10:19:05 PST 2011
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Atmel AT91SAM9G20-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz
sam9g20: i2c available
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: mem=64M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61108KB available (3292K code, 241K data, 132K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:192
AT91: 96 gpio irqs in 3 banks
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating delay loop... 197.83 BogoMIPS (lpj=989184)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
AT91: Power Management (with slow clock mode)
AT91: Starting after software reset
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource tcb_clksrc
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
ROMFS MTD (C) 2007 Red Hat, Inc.
msgmni has been set to 119
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
atmel_usart.3: ttyS3 at MMIO 0xfffd0000 (irq = 23) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 351 at 0x000002be0000
Bad eraseblock 1119 at 0x000008be0000
Creating 9 MTD partitions on "atmel_nand":
0x000000000000-0x000010000000 : "MTNCG-NANDFlash"
0x000000000000-0x000000020000 : "AT91Bootstrap"
0x000000020000-0x000000060000 : "UBoot"
0x000000060000-0x000000080000 : "UBoot Config"
0x000000080000-0x0000000a0000 : "UBoot Redundant Config"
0x0000000a0000-0x000000800000 : "uImage"
0x000000800000-0x000001000000 : "Config"
0x000001000000-0x000001800000 : "Oem Config"
0x000001800000-0x000010000000 : "Rootfs"
atmel_spi atmel_spi.0: Atmel SPI Controller at 0xfffc8000 (irq 12)
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:08:00:87:2d:42)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
usbmon: debugfs is not available
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: AT91 OHCI
usb usb1: Manufacturer: Linux 2.6.32.3 ohci_hcd
usb usb1: SerialNumber: at91
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
IRQ 1/rtc0: IRQF_DISABLED is not guaranteed on shared IRQs
i2c /dev entries driver
at24 0-0056: 512 byte 24c04 EEPROM (writable)
sam9g20: read 512 bytes from id eeprom
i2c-gpio i2c-gpio: using pins 55 (SDA) and 56 (SCL)
AT91SAM9 Watchdog: sorry, watchdog is disabled
at91_wdt: probe of at91_wdt failed with error -5
Registered led device: status
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (955 buckets, 3820 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
rtc-at91sam9 at91_rtt.0: setting system clock to 2011-11-29 17:39:48 UTC (1322588388)
JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
VFS: Mounted root (jffs2 filesystem) readonly on device 31:8.
Freeing init memory: 132K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
[<c002e74c>] (unwind_backtrace+0x0/0xdc) from [<c02aff48>] (panic+0x3c/0x128)
[<c02aff48>] (panic+0x3c/0x128) from [<c0029638>] (init_post+0x13c/0x174)
[<c0029638>] (init_post+0x13c/0x174) from [<c00085cc>] (kernel_init+0xe0/0x114)
[<c00085cc>] (kernel_init+0xe0/0x114) from [<c002a958>] (kernel_thread_exit+0x0/0x8)November 29, 2011 at 5:40 pm #3563Jesse GillesBlockedInput file is not page-aligned. Use the padding option.
Data was only partially written due to errorThat was the error returned from trying to flash from the SD card. There has to be something different between the two files. Did you compare sizes, checksums etc? Seems like the image file on the SD card is bad.
November 29, 2011 at 6:07 pm #3564Neil McGuireParticipantAlright, the size matches, but the checksums don’t match between ubuntu and the cdp, but that doesn’t have me convinced yet. I also ran the following commands, on my Ubuntu dev box and the mtcdp box:
vi test
:wq
md5sum test
So basically, created an empty file, and took its checksum. The checksums didn’t match.
Ubuntu: d41d8cd98f00b204e9800998ecf8427e
cdp: 68b329da9893e34099c7d8ad5cb9c940
I’m going to try using tftp to download it to the SD card rather than ftp, and see if that makes a difference.
November 29, 2011 at 6:10 pm #3565Neil McGuireParticipantOkay, using tftp to donwload it, the checksums now match between Ubuntu and the CDP box. /me crosses fingers
November 29, 2011 at 6:12 pm #3566Jesse GillesBlockedUsing SCP is also reliable for doing file transfers. Or putting the SD card in a card reader attached to your PC.
November 29, 2011 at 6:15 pm #3567Neil McGuireParticipantMy problem with doing that is that my dev box is a virtual machine running under Oracle’s VirtualBox on a windows 7 pc, and getting the networking to like directly scp’ing and such hasn’t made itself clear yet. the ftp and tftp servers I set up on the windows box were accessible from both locations, so I figured that would be the easiest way, as I had thought the ftp would send an exact copy of the file. Guess I was wrong about that.
At the very least, now it’s working, so I have an SD card I can use to flash all the devices in our fleet. Thanks, Jesse.
November 29, 2011 at 6:17 pm #3568Jesse GillesBlockedI think the reason your “md5sum test” test didn’t work was because vi didn’t create an empty file on the MTCDP. When I try it, the file is 1 byte instead of 0 (on my Ubuntu box).
The md5sums should most definitely match or they aren’t the same 🙂
November 29, 2011 at 6:19 pm #3569Jesse GillesBlockedGood deal, glad you got it working.
July 27, 2012 at 10:49 pm #3570Neil McGuireParticipantOkay, so it’s been a while, and I needed to deploy a new image, but for some reason, I can’t get the settings to work to connect to the debug serial port, so I can’t see if it’s the same issue, nor can I try to upgrade from the tftp server.
I also moved to CoreCDP 2, so that might be causing the issue?
But I did verify that the checksum on the dev box matches the checksum on the SD card, so I know that’s not the issue.
Any advice on what to check would be helpful.
-
AuthorPosts
- You must be logged in to reply to this topic.