NSA320 Install issues.

Install Arch Linux ARM on other devices.

NSA320 Install issues.

Postby Magnin » Thu Mar 21, 2013 1:23 am

I attempted to install on the NSA320 without a serial cable and now the system won't boot.

I got a serial cable now and can boot the system into UBOOT. When I attempt to let it boot completely I get the following:
Code: Select all

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Mar 23 2011 - 16:09:39) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFEE0

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
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
//---  stateButtonBit = 3, recovery ---//
Kernel address is 0xc80000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0, egiga1 [PRIME]
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: ST3320620AS                              Firm: 3.AAC    Ser#:             3QF05MC0
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)


** Unable to read "/uImage" from ide 0:1 **
## Booting image at 02000000 ...
Bad Magic Number
NSA320>>


When I interrupt the boot process it doesn't seem to see the USB key (I've tried 2 different keys, a 1gb and a 2gb model). Here's the output for the USB subsystem:

Code: Select all
NSA320>> usb tree

Device Tree:
  0  See Interface (12MBit/s, 0mA)
   
NSA320>> usb start
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
NSA320>> usb tree

Device Tree:
  1  Hub (480MBit/s, 0mA)
  |  Marvell EHCI
  |
  +-2  Hub (480MBit/s, 100mA)
        USB2.0 Hub
     
NSA320>>


How do I get the USB device up so I can boot from it to fix my install?
Magnin
 
Posts: 3
Joined: Thu Mar 14, 2013 1:57 am

Re: NSA320 Install issues.

Postby pepedog » Thu Mar 21, 2013 9:28 am

Did you read the directions
Place HDD in left slot, USB key into front USB port, power on the device.

The os is installed on sata
The scripts on the stick show how to partition and format the hard drive.
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK

Re: NSA320 Install issues.

Postby Magnin » Fri Mar 22, 2013 1:00 am

Yes, as indicated by the boot log:

Code: Select all
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
  Device 0 @ 0 0:
Model: ST3320620AS                              Firm: 3.AAC    Ser#:             3QF05MC0
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)

** Unable to read "/uImage" from ide 0:1 **
## Booting image at 02000000 ...
Bad Magic Number


I have a 320GB Segate HDD for Device 0 @ 0 0

The initial boot progressed far enough that it changed the Uboot config so that it no longer boots default from the firmware, but attempts to boot from the HDD. Unfortunatly, it appears that the HDD was not partitioned correctly and updated with the root image.

I had to run "run bootcmd_stock" with the USB device in the front port and it redid the install. Not sure why it failed the 1st time, but it looks like the boot scripts have been updated since my first attempt about 2 weeks ago.
Magnin
 
Posts: 3
Joined: Thu Mar 14, 2013 1:57 am

Re: NSA320 Install issues.

Postby pepedog » Fri Mar 22, 2013 1:08 am

Yes, boot scripts have been modified. Boot args set rootfs as read only before, not good for keygen.
My drive was wonky, had to use parted to fix it
pepedog
Developer
 
Posts: 2431
Joined: Mon Jun 07, 2010 3:30 pm
Location: London UK


Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 0 guests