IX4-200d - no boot - i think no HDD power February 24, 2020 07:05PM |
Registered: 4 years ago Posts: 1 |
__ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** uboot_ver:v1.1.1 ** ** MARVELL BOARD: IX4-110 LE U-Boot 1.1.4 (Mar 10 2011 - 15:01:57) Marvell version: 3.4.18 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CF600 Soc: 88F6281 A1 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM CS[1] base 0x10000000 size 256MB DRAM Total size 512MB 16bit width Found 0x20 i2c device Set Power State as Always On Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:32 MB Found ADT7473, program LED ...(led_volt=90) OK Found ADT7473, program thermal/Fan ...(pwm_min=0) (pwm_max=130) (therm=67) (temp_min=60) OK Marvell Serial ATA Adapter Integrated Sata device found CPU : Marvell Feroceon (Rev 1) Found initrd at 0x2d8000 Streaming disabled Write allocate disabled Module 0 is RGMII Module 1 is RGMII USB 0: host mode PEX 0: PCI Express Root Complex Interface PEX interface detected Link X1 SCSI: AHCI 0001.0000 32 slots 3 ports 3 Gbps 0x7 impl IDE mode flags: 64bit ncq stag led pmp slum part scanning bus for devices... Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 NAND read: device 0 offset 0xb0000, size 0x228000 Reading data from 0x2d7e00 -- 100% complete. 2260992 bytes read: OK NAND read: device 0 offset 0x2d8000, size 0x300000 Reading data from 0x5b9400 -- 96% complete.reading NAND page at offset 0x5c0000 failed 3145728 bytes read: ERROR ## Booting image at 02000000 ... Image Name: Linux-2.6.22.18 Created: 2012-01-05 18:29:43 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1910204 Bytes = 1.8 MB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 12000000 ... Image Name: Created: 2012-05-02 20:38:45 UTC Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 1831340 Bytes = 1.7 MB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... Uncompressing Linux.......................................................................................................................... done, booting the kernel. Linux version 2.6.22.18 (soho@bsoho149.lss.emc.com) (gcc version 4.3.2 (crosstool-NG-1.3.1) ) #1 Thu Jan 5 13:29:36 EST 2012 CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053977 Machine: Feroceon-KW Using UBoot passing parameters structure Memory policy: ECC disabled, Data cache writeback CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets Built 1 zonelists. Total pages: 130048 Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0x0(uboot),0x10000@0xa0000(env),0x228000@0xb0000(zImage),0x300000@0x2d8000(initrd),32m@0x0(flash) PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour dummy device 80x30 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 256MB 256MB 0MB 0MB = 512MB total Memory: 513920KB available (3520K code, 283K data, 120K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 CPU Interface ------------- SDRAM_CS0 ....base 00000000, size 256MB SDRAM_CS1 ....base 10000000, size 256MB SDRAM_CS2 ....disable SDRAM_CS3 ....disable PEX0_MEM ....base e8000000, size 128MB PEX0_IO ....base f2000000, size 1MB INTER_REGS ....base f1000000, size 1MB NFLASH_CS ....base fa000000, size 2MB SPI_CS ....base f4000000, size 16MB BOOT_ROM_CS ....no such DEV_BOOTCS ....no such CRYPT_ENG ....base f0000000, size 2MB Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21)-- IX4-110 Soc: 88F6281 A1 LE Detected Tclk 200000000 and SysClk 400000000 MV Buttons Device Load Marvell USB EHCI Host controller #0: c0876600 PEX0 interface detected Link X1 PCI: bus0: Fast back to back transfers disabled SCSI Scattered Spinup: SCSI Scattered Spinup Feature Status: Enabled SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb NET: Registered protocol family 2 Time: kw_clocksource clocksource has been installed. IP route cache hash table entries: 16384 (order: 4, 65536 bytes) TCP established hash table entries: 65536 (order: 7, 524288 bytes) TCP bind hash table entries: 65536 (order: 6, 262144 bytes) TCP: Hash tables configured (established 65536 bind 65536) TCP reno registered checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 1788K RTC registered Use the XOR engines (acceleration) for enhancing the following functions: o RAID 5 Xor calculation o kernel memcpy o kenrel memzero Number of XOR engines to use: 4 cesadev_init(c0011e28) mvCesaInit: sessions=640, queue=64, pSram=f0000000 MV Buttons Driver Load Registering unionfs 2.5.1 (for 2.6.22.19) Installing knfsd (copyright (C) 1996 okir@monad.swb.de). io scheduler noop registered io scheduler anticipatory registered (default) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A serial8250.0: ttyS1 at MMIO 0xf1012100 (irq = 34) is a 16550A RAMDISK driver initialized: 16 RAM disks of 5120K size 1024 blocksize loop: module loaded Loading Marvell Ethernet Driver: o Cached descriptors in DRAM o DRAM SW cache-coherency o Single RX Queue support - ETH_DEF_RXQ=0 o Single TX Queue support - ETH_DEF_TXQ=0 o TCP segmentation offload enabled o Receive checksum offload enabled o Transmit checksum offload enabled o Network Fast Processing (Routing) supported o Driver ERROR statistics enabled o Driver INFO statistics enabled o Proc tool API enabled o Rx descripors: q0=128 o Tx descripors: q0=532 o Loading network interface(s): o eth0, ifindex = 1, GbE port = 0 o eth1, ifindex = 2, GbE port = 1 mvFpRuleDb (c0ac0000): 16384 entries, 65536 bytes e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI e100: Copyright(c) 1999-2006 Intel Corporation Marvell Storage Controller is found, using IRQ 9. scsi0 : Marvell Storage Controller Integrated Sata device found scsi1 : Marvell SCSI to SATA adapter scsi2 : Marvell SCSI to SATA adapter NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $ NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND 32MiB 3,3V 8-bit) Scanning device for bad blocks 5 cmdlinepart partitions found on MTD device nand_mtd Using command line partition definition Creating 5 MTD partitions on "nand_mtd": 0x00000000-0x000a0000 : "uboot" 0x000a0000-0x000b0000 : "env" 0x000b0000-0x002d8000 : "zImage" 0x002d8000-0x005d8000 : "initrd" 0x00000000-0x02000000 : "flash" ehci_marvell ehci_marvell.70059: Marvell Orion EHCI ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1 ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100 ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected USB Universal Host Controller Interface driver v3.0 usb 1-1: new high speed USB device using ehci_marvell and address 2 usb 1-1: configuration #1 chosen from 1 choice hub 1-1:1.0: USB hub found hub 1-1:1.0: 4 ports detected usbcore: registered new interface driver usblp drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. mice: PS/2 mouse device common for all mice i2c /dev entries driver attach_adapter.... adt7473_detect.... adt7473 0-002e: adt7473 chip found md: linear personality registered for level -1 md: raid0 personality registered for level 0 md: raid1 personality registered for level 1 md: raid10 personality registered for level 10 raid6: int32x1 92 MB/s raid6: int32x2 118 MB/s raid6: int32x4 130 MB/s raid6: int32x8 98 MB/s raid6: using algorithm int32x4 (130 MB/s) md: raid6 personality registered for level 6 md: raid5 personality registered for level 5 md: raid4 personality registered for level 4 raid5: measuring checksumming speed arm4regs : 1087.200 MB/sec 8regs : 806.000 MB/sec 32regs : 881.200 MB/sec raid5: using function: arm4regs (1087.200 MB/sec) device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com dm_crypt using the OCF package. wix gpio_init wix_lcm: WIX LCM driver version 0.1 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 EXT2-fs warning: checktime reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). cat: can't open '/sys/block/sda/removable': No such file or directory cat: can't open '/sys/block/sdb/removable': No such file or directory cat: can't open '/sys/block/sdc/removable': No such file or directory cat: can't open '/sys/block/sdd/removable': No such file or directory mdadm: No devices to examine cat: can't open '/sys/block///size': No such file or directory mdadm: No devices to examine cat: can't open '/sys/block///size': No such file or directory mdadm: No devices to examine cat: can't open '/sys/block///size': No such file or directory mdadm: No devices to examine cat: can't open '/sys/block///size': No such file or directory Sys UUID is :0 Valid Disk 1 in md0: Valid Disk 2 in md0: Valid Disk 3 in md0: Valid Disk 4 in md0: USB Device node is /dev/sda1 Trying to see the if the reset button is pressed or not Started /dev/btns file does not exist creating it Opened /dev/btns with fd 3 Reset Key Status: Button Id = 29 Push Count = 0 Release Count = 0 Checking for valid image in hard drives mdadm: /dev/md0 not identified in config file. e2fsck 1.41.3 (12-Oct-2008) ext2fs_check_if_mouEXT2-fs: unable to read superblock nt: No such fileFAT: unable to read boot sector or directory while determining whether /dev/md0 is mounted. e2fsck: Invalid argument while trying to open /dev/md0 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> mount: mounting /dev/md0 on sysroot/boot failed: Input/output error Checking if there is an attached EMC Imager mount: mounting /dev/sda1 on /usb_drive failed: No such device or address Going in to Network Imaging Mode umount: cannot umount /dev/md0: Invalid argument umount: cannot umount /usb_drive: Invalid argument eth0: started udhcpc (v1.9.2) started Sending discover... Sending discover... Sending discover... Sending discover... Sending discover... Sending discover... Sending discover... Sending discover... Sending discover... Sending discover... No lease, failing Device Model- ix4-200d Device: Socket Listening on: 2081 Mac address = 00:50:43:d2:12:36 Send: Network is unreachable Mounting config image... mount: mounting /sysroot/boot/images/config on /sysroot/boot/etc failed: No such file or directory umount: cannot umount /sysroot/boot/etc: Invalid argument umount: cannot umount /dev/md0: Invalid argument Constructing root filesystem... cp: cannot stat '/sysroot/mnt/apps/ram': No such file or directory Bootstrapping ... Initialization complete. Freeing init memory: 120K init started: BusyBox v1.9.2 (2012-01-05 15:00:07 EST) starting pid 425, tty '': '/etc/init.d/rcS' starting pid 428, tty '': 'umount' BusyBox v1.9.2 (2012-01-05 15:00:07 EST) multi-call binary Usage: umount [flags] FILESYSTEM|DIRECTORY Unmount file systems Options: -r Try to remount devices as read-only if mount is busy -l Lazy umount (detach filesystem) -f Force umount (i.e., unreachable NFS server) -D Do not free loop device (if a loop device has been used) The system is going down NOW! Sending SIGTERM to all processes Sending SIGKILL to all processes Requesting system reboot md: stopping all md devices. Restarting system. Reseting !!
Required Software: • Winrar or compatible software • Putty • TFTPD server - tftpd64.450.rar • Recovery package - ix4-200d-recovery-2.1.42.18967.rar • Recovery files - files.rar • Firmware package - ix4-200d-2.1.48.30125.tgz Required Hardware: • Iomega IX4-200d with HDD's • TTL to USB cable • USB thumb drive • Spare network cable USB Thumb drive preparation: 1) Format a USB thumb drive with fat32 2) Decompress "ix4-200d-recovery-2.1.42.18967.rar" 3) Copy the emctools folder (and subfolders) to USB drive. Target hard drive preparation: 1) Delete all partitions (If any exists) (I Used GParted Live CD) Iomega IX4-200d preparation: 1) Put target hard drive into slot 1 (Other slots empty) 2) Attach TTL cable to three header pins (See pinout.jpg) a. Ground wire to Ground pin b. TX wire to RX pin c. RX wire to TX pin d. Don’t connect the red (power) wire 3) Insert USB thumb drive prepared earlier in the back of the Iomega IX4-200d PC preparations: 1) Attach Ethernet cable between PC and Iomega IX4-200d 2) Install drivers for TTL cable before connecting cable a. Attach TTL cable to PC – Wait for driver to load b. Write down the COM port (Usually COM3) 3) Decompress "files.rar" 4) Copy zImage and initrd files to folder containing the TFTPD64.EXE server 5) Disable any TFTP servers on system if any exist 6) Set the following static IP address - 10.4.50.5 7) Turn off Windows Firewall 8) Start the server program TFTPD64.EXE 9) Start putty a. Select connection type serial b. Set speed to 115200 c. Set serial line to the Com port assigned to the TTL cable e. Select “serial” category on left f. Ensure data bits 8, stop bits 1, Parity None, Flow XON/XOFF g. Set the values accordingly if necessary 10) Open the session (“Open” button at bottom) Starting the recovery process: 1) Turn on the Iomega IX4-200d and watch boot process in putty window. a. If nothing appears in the putty window i. Check the TTL wiring on the Iomega IX4-200d ii. Double check the port setting in putty 2) Press any key after the boot process starts a. "press any key to interrupt the autoboot..." message for 1 second b. marvell>> 3) Retry 1 and 2 until you get to the marvell>> prompt 4) Copy and paste the following commands at the prompt, one at a time and press enter key: resetenv tftpboot 0x2000000 zImage tftpboot 0x12000000 initrd nand erase 0x2d8000 0x2e4047 nand erase 0xb0000 0x1fb1d8 nand write.e 0x12000000 0x2d8000 0x2e4047 nand write.e 0x2000000 0x0b0000 0x1fb1d8 reset 5) The NAS will reboot, create the boot partitions on hard drive, populate them, and power off. 6) Remove the USB stick from the Iomega IX4-200d. 7) Connect Iomega IX4-200d back to router/switch 8) Put additional prepared hard drives into Iomega IX4-200d (if you wish) in sequence 9) Turn the PC firewall back on 10) Reset PC network adapter settings and connect PC to router/switch 11) Shut down TFPTD server on PC 12) Power on the Iomega IX4-200d Final Steps: 1) Wait for Iomega IX4-200d to fully boot up (100%) 2) The front display will include the IP address assigned to the Iomega IX4-200d-200d 3) Open your browser and navigate to the Iomega IX4-200d IP address 4) Upgrade to the lattest firmware v2.1.48.30125 by installing the "ix4-200d-2.1.48.30125.tgz" 5) Configure the device to meet your requirements 6) It will take many hours for the Iomega IX4-200d to reconfigure the disks for use but you're all set.
Marvell>> printenv bootdelay=1 baudrate=115200 loads_echo=0 ipaddr=10.4.50.165 serverip=10.4.50.5 rootpath=/mnt/ARM_FS/ netmask=255.255.255.0 run_diag=yes CASset=min MALLOC_len=1 ethprime=egiga0 bootargs_root=root=/dev/nfs rw bootargs_end=:::DB88FXX81:eth0:none image_name=uImage console=console=ttyS0,115200 mtdparts=nand_mtd:0xa0000@0x0(uboot),0x00010000@0x000a0000(param),32m@0x0(flash) uboot_start=0x0 uboot_size=0xa0000 env_start=0xa0000 env_size=0x10000 kernel_start=0xb0000 kernel_size=0x228000 initrd_size=0x300000 make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:$(uboot_size)@$(uboot_start)(uboot),$(env_size)@$(env_start)(env),$(kernel_size)@$(kernel_start)(zImage),$(initrd_size)@$(initrd_start)(initrd),32m@0x0(flash); flash_load=run make_boot_args;nand read.e 0x2000000 $(kernel_start) $(kernel_size);nand read.e 0x12000000 $(initrd_start) $(initrd_size);bootm 0x2000000 0x12000000; bootcmd=run flash_load; standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end); bootm 0x2000000; ethaddr=00:50:43:d2:12:36 ethmtu=1500 mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host nandEcc=1bit netretry=no rcvrip=169.254.100.100 loadaddr=0x02000000 autoload=no uboot_ver=v1.1.1 stdin=serial stdout=serial stderr=serial mainlineLinux=no enaMonExt=no enaCpuStream=no enaWrAllo=no pexMode=RC disL2Cache=no setL2CacheWT=yes disL2Prefetch=yes enaICPref=yes enaDCPref=yes sata_dma_mode=yes netbsd_en=no vxworks_en=no initrd_start=0x2d8000 disaMvPnp=no eth1addr=00:50:43:d2:12:37 enaAutoRecovery=yes pcieTune=no ethact=egiga0 Environment size: 1627/16380 bytes
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 08:07PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:$(uboot_size)@$(uboot_start)(uboot),$(env_size)@$(env_start)(env),$(kernel_size)@$(kernel_start)(zImage),$(initrd_size)@$(initrd_start)(initrd),32m@0x0(flash);
flash_load=run make_boot_args;nand read.e 0x2000000 $(kernel_start) $(kernel_size);nand read.e 0x12000000 $(initrd_start) $(initrd_size);bootm 0x2000000 0x12000000;
bootcmd=run flash_load;
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 08:11PM |
Registered: 5 years ago Posts: 255 |
[ 13.267197] 8<--- cut here --- [ 13.270366] Unable to handle kernel paging request at virtual address e0ee6028 [ 13.277646] pgd = dac2d30a [ 13.280366] [e0ee6028] *pgd=1e689811, *pte=00000000, *ppte=00000000 [ 13.286697] Internal error: Oops: 807 [#1] ARM [ 13.291160] Modules linked in: sata_mv(+) libahci mvmdio(+) mv643xx_eth(+) libata des_generic(+) adt7475(+) hwmon_vid hwmon orion_w dt watchdog aes_generic orion_nand(+) nand nand_ecc bch nandcore gpio_74x164 m25p80 spi_nor mtdblock mtd_blkdevs mtd ip_tables x_table s sha256_generic hmac ipv6 nf_defrag_ipv6 autofs4 ext4 crc16 mbcache jbd2 sd_mod uas usb_storage scsi_mod raid10 raid456 libcrc32c crc 32c_generic async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq raid1 raid0 multipath linear md_mod ehci_orion ehc i_hcd usbcore nls_base usb_common rtc_mv [ 13.341690] CPU: 0 PID: 236 Comm: systemd-udevd Not tainted 5.3.9 #2 [ 13.348067] Hardware name: Marvell Kirkwood (Flattened Device Tree) [ 13.354390] PC is at mv_stop_edma_engine+0x14/0x5c [sata_mv] [ 13.360094] LR is at mv_reset_channel+0x3c/0xd8 [sata_mv] [ 13.365517] pc : [<bf5251a4>] lr : [<bf526510>] psr: 20000013 [ 13.371803] sp : de561c70 ip : 00000105 fp : fffffffe [ 13.377045] r10: 00000800 r9 : 0000101f r8 : de780ce0 [ 13.382286] r7 : e0ee6028 r6 : de780ce0 r5 : e0ec0000 r4 : e0ee6000 [ 13.388835] r3 : 00000002 r2 : 00000002 r1 : e0ec0000 r0 : e0ee6000 [ 13.395385] Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none [ 13.402551] Control: 0005397f Table: 1e564000 DAC: 00000051 [ 13.408316] Process systemd-udevd (pid: 236, stack limit = 0x570e1121) [ 13.414872] Stack: (0xde561c70 to 0xde562000) [ 13.419244] 1c60: e0ee6000 e0ec0000 de780ce0 00000002 [ 13.427461] 1c80: de780ce0 bf526510 00026000 00000000 e0ec0000 00000002 de780ce0 bf52661c [ 13.435675] 1ca0: de780ce0 00000004 deb4cf00 e0ec0000 00000001 00000007 00000021 bf526bbc [ 13.443889] 1cc0: 00000013 de780ce0 df50ca10 df50ca00 ffff0000 deb4cf00 00000000 00000021 [ 13.452104] 1ce0: fffffffe bf5272c8 00000000 de759c60 c05bf028 de782160 00000004 bf5293ac [ 13.460318] 1d00: 00000000 74726f70 de750033 df50ec60 00000001 795b3a6f de561f44 df50ca10 [ 13.468532] 1d20: bf52a20c bf52a20c 00000000 c0647c74 0000000e c007cc64 de561f44 c02b9f94 --More-- 13.657520] [<bf5251a4>] (mv_stop_edma_engine [sata_mv]) from [<bf526510>] (mv_reset_channel+0x3c/0xd8 [sata_mv]) [ 13.667862] [<bf526510>] (mv_reset_channel [sata_mv]) from [<bf52661c>] (mv_soc_reset_hc+0x70/0xb4 [sata_mv]) [ 13.677853] [<bf52661c>] (mv_soc_reset_hc [sata_mv]) from [<bf526bbc>] (mv_init_host+0x10c/0x540 [sata_mv]) [ 13.687672] [<bf526bbc>] (mv_init_host [sata_mv]) from [<bf5272c8>] (mv_platform_probe+0x2d8/0x528 [sata_mv]) [ 13.697656] [<bf5272c8>] (mv_platform_probe [sata_mv]) from [<c02b9f94>] (platform_drv_probe+0x40/0x74) [ 13.707097] [<c02b9f94>] (platform_drv_probe) from [<c02b82c8>] (really_probe+0x238/0x3c8) [ 13.715405] [<c02b82c8>] (really_probe) from [<c02b8944>] (device_driver_attach+0x4c/0x64) [ 13.723706] [<c02b8944>] (device_driver_attach) from [<c02b8a68>] (__driver_attach+0x10c/0x12c) [ 13.732447] [<c02b8a68>] (__driver_attach) from [<c02b645c>] (bus_for_each_dev+0x5c/0x80) [ 13.740669] [<c02b645c>] (bus_for_each_dev) from [<c02b75ac>] (bus_add_driver+0x17c/0x1e4) [ 13.748968] [<c02b75ac>] (bus_add_driver) from [<c02b8ff0>] (driver_register+0xb4/0xf8) [ 13.757027] [<c02b8ff0>] (driver_register) from [<bf52d030>] (mv_init+0x30/0x1000 [sata_mv]) [ 13.765530] [<bf52d030>] (mv_init [sata_mv]) from [<c000ab30>] (do_one_initcall+0x60/0x19c) [ 13.773929] [<c000ab30>] (do_one_initcall) from [<c007e170>] (do_init_module+0x60/0x208) [ 13.782064] [<c007e170>] (do_init_module) from [<c00804b8>] (load_module.constprop.14+0x20e0/0x218c) [ 13.791245] [<c00804b8>] (load_module.constprop.14) from [<c0080794>] (sys_finit_module+0xb0/0xc4) [ 13.800251] [<c0080794>] (sys_finit_module) from [<c00091c4>] (__sys_trace_return+0x0/0x1c) [ 13.808632] Exception stack(0xde561fa8 to 0xde561ff0) [ 13.813703] 1fa0: b4577400 00000000 0000000f b6dd6b14 00000000 b6dd7628 [ 13.821918] 1fc0: b4577400 00000000 00000000 0000017b 01afdf88 004837ac 01b04f38 00000000 [ 13.830129] 1fe0: bec81168 bec81158 b6dcda44 b6ec1a00 [ 13.835209] Code: e52de004 e8bd4000 e3a03002 e2807028 (e
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 08:35PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 09:00PM |
Registered: 5 years ago Posts: 255 |
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 09:15PM |
Admin Registered: 13 years ago Posts: 18,821 |
KW_GPIO0_BASE = 0xF1010100 KW_GPIO1_BASE = 0xF1010140
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 09:59PM |
Registered: 5 years ago Posts: 255 |
root@ix4:~# lspci 00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC (rev 02) 01:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II / PATA Controller (rev b2)
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 10:29PM |
Admin Registered: 13 years ago Posts: 18,821 |
md 0xF1010100 md 0xF1010140
mw 0xF1010100 0 (A & 1<<14)
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 10:43PM |
Registered: 5 years ago Posts: 255 |
scsi scan
Re: IX4-200d - no boot - i think no HDD power February 24, 2020 11:46PM |
Admin Registered: 13 years ago Posts: 18,821 |
> scsi scan >>
Re: IX4-200d - no boot - i think no HDD power February 25, 2020 07:42PM |
Registered: 5 years ago Posts: 255 |
f1010100: 1000d080 efff0f7f 00000000 00000000 ................ f1010110: 3001d080 b401ff94 00000000 00000000 ...0............ f1010120: 00000000 00000000 00000000 00000000 ................ f1010130: 00000000 00000000 00000000 00000000 ................ f1010140: 0001000c fffec003 00000000 00000000 ................ f1010150: 0003000c 0003affc 00000000 00000000 ................
f1010100: 1000d080 efff0f7f 00000000 00000000 ................ f1010110: 3001d080 b401ff94 00000000 00000000 ...0............ f1010120: 00000000 00000000 00000000 00000000 ................ f1010130: 00000000 00000000 00000000 00000000 ................ f1010140: 0001000c fffec003 00000000 00000000 ................ f1010150: 0003800c 0003affc 00000000 00000000 ................
Re: IX4-200d - no boot - i think no HDD power February 25, 2020 08:04PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: IX4-200d - no boot - i think no HDD power February 25, 2020 09:46PM |
Registered: 5 years ago Posts: 255 |
Re: IX4-200d - no boot - i think no HDD power February 25, 2020 11:57PM |
Admin Registered: 13 years ago Posts: 18,821 |
Re: IX4-200d - no boot - i think no HDD power March 25, 2020 11:22PM |
Admin Registered: 13 years ago Posts: 18,821 |
Quote
I just started playing with this. I dumped 0xF1010150 and then did again with a button pressed which corresponds to mpp47.
Re: IX4-200d - no boot - i think no HDD power March 26, 2020 04:28PM |
Registered: 5 years ago Posts: 255 |
Re: IX4-200d - no boot - i think no HDD power March 26, 2020 09:52PM |
Admin Registered: 13 years ago Posts: 18,821 |