Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
I've noticed a CRC error on my Shield Sandbox:
.... OCTEON CN7020-AAP pass 1.2, Core clock: 1000 MHz, IO clock: 600 MHz, DDR clock: 667 MHz (1334 Mhz DDR) Base DRAM address used by u-boot: 0x4f000000, size: 0x1000000 DRAM: 1 GiB Clearing DRAM.....Clearing base address: 0x100000, size: 0xff00000, ub_base: 0x4f000000, ub_size: 0x1000000 Stack: 0xc0f71c60 Done clearing memory, ub_base: 0x4f000000 .Clearing base address: 0x20000000, size: 0x30000000, ub_base: 0x4f000000, ub_size: 0x1000000 Stack: 0xc0f71c60 Done clearing memory, ub_base: 0x4f000000 done board_fixup_fdt: Found PCIe GPIO2 .. MMC device not found, initializing Octeon MMC/SD0: 1 *** Warning - bad CRC, using default environment PCIe: Link timeout on port 0, probably the slot is empty PCIe: Port 1 not in PCIe mode, skipping PCIe: Port 2 not in PCIe mode, skipping Net: cvmx_helper_interface: interface 0 cvmx_helper_interface: interface 1 cvmx_helper_interface: interface 4 octeth0, octeth1, octeth2, octeth3 Type the command 'usb start' to scan for USB storage devices. late_board_init .. ITUS: SW1 1 Bridge (INNER) .... and later this unknown partition table: [ 32.951060] rtc-ds1307 0-0068: hctosys: unable to read the hardware clock [ 32.975753] Freeing unused kernel memory: 24128K (ffffffff80930000 - ffffffff820c0000) Waiting for extroot dev : /dev/mmcblk0p4 : 0 Waiting for extroot dev : /dev/mmcblk0p4 : 1 Waiting for extroot dev : /dev/mmcblk0p4 : 2 Waiting for extroot dev : /dev/mmcblk0p4 : 3 Waiting for extroot dev : /dev/mmcblk0p4 : 4 Waiting for extroot dev : /dev/mmcblk0p4 : 5 [ 49.427013] mmc1: BKOPS_EN bit is not set [ 49.447662] mmc1: new high speed DDR MMC card at address 0001 [ 49.466141] mmcblk0: mmc1:0001 P1XXXX 3.60 GiB [ 49.483114] mmcblk0boot0: mmc1:0001 P1XXXX partition 1 2.00 MiB [ 49.501470] mmcblk0boot1: mmc1:0001 P1XXXX partition 2 2.00 MiB [ 49.519824] mmcblk0rpmb: mmc1:0001 P1XXXX partition 3 128 KiB [ 49.541719] mmcblk0: p1 p2 p3 p4 [ 49.562698] mmcblk0boot1: unknown partition table [ 49.584208] mmcblk0boot0: unknown partition table Waiting for extroot dev : /dev/mmcblk0p4 : 16 Found /sys/block/mmcblk0/mmcblk0p4 : 17 Creating /dev/mmcblk0p4 Mounting /dev/mmcblk0p4 on /overlay [ 50.523970] kjournald starting. Commit interval 5 seconds [ 50.542640] EXT3-fs (mmcblk0p4): using internal journal ... For the rest everything seems to work ok. Anyone know how to solve CRC error?
No more: Shield Pro v1, Chaos Calmer, FW 1.51 SP1
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
I have that issue as well, I think it's considered "normal".
|
Loading... |
Reply to author |
Edit post |
Move post |
Delete this post |
Delete this post and replies |
Change post date |
Print post |
Permalink |
Raw mail |
In reply to this post by hans2
Hi Hans
Good to have a dedicated forum back again shame about ITUS but they may do a phoenix rising from the ashes. Right your bad CRC is normal, I have two Shields both with the same warning. I have one shield which refused to boot and so I put my technical head on and started to dig around. The Shield uses a program called uboot which i is coded into the chip, this sets up some very basic but complicated stuff to then load and run Octboot2bin which is located on the shield and can be upgraded ( i think). Then Octoot2bin gives control over to u-boot-octeon_rhin0_itus7x.bin ( this is the name on 1.51 sp1 firmware but is different on rc1 release). It's this programs which loads ITUSRouterImage ( if your in router mode) and i believe that because the memory is clear it flags the warning. Hope this helps. It would be good if we could have sections for beginner and experts. Andy (roadrunnere42) |
Free forum by Nabble | Edit this page |