Flash DNS-323 A1 w/ Alt-F on Serial Port

336 views
Skip to first unread message

Lui Massango

unread,
Apr 6, 2016, 2:17:32 AM4/6/16
to Alt-F
Greetins everybody

I was wondering if i could get some help on this,
recently i got my dns323 a1, bricked, i don´t know how, suddenly the blue power light started blinking repeatedly,
i tried to recovery it, flashing the firmware 1.03 which is the stock firmware, following the steps on this tutorial: http://dns323.kood.org/howto:reflash_from_windows,
but although the process apparently finished successfully, it did´nt resolve the problem,

Did some reading and found about alt-f, i find it great and i would really like the box to be running something like this,
so i downloaded the firmware, splitted it with dn323-fw as instructed, but when i try to flash it i get the error: Ramdisk Size = 6412746 error,Ramdisk size > 005e0000 byes

Question: it´s there a workaround to get alt-f flashed to this box via serial port?

PLEASE HELP, i´m really desperate to get this box alive,

below its how my boot log looks, in case it could be helpful,

thanks in advance

U-Boot 1.1.1 (Nov 13 2006 - 14:01:34) Marvell version: 1.4.2

DRAM CS[0] base 0x00000000   size  64MB
DRAM Total size  64MB
[8192kB@ff800000] Flash:  8 MB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
*** Warning - bad CRC, using default environment


Soc: MV88F5181 Rev 3
CPU: ARM926 (Rev 0) running @ 500Mhz
SysClock = 166Mhz , TClock = 166Mhz


 Init usb device.
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Hit any key to stop autoboot:  0
## Booting image at ff820000 ...
   Image Name:   Linux-2.6.12.6-arm1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1426456 Bytes =  1.4 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at ff9a0000 ...
   Image Name:   Ramdisk
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5966305 Bytes =  5.7 MB
   Load Address: 00800000
   Entry Point:  00800000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux........................................................................................                                                 ....... done, booting the kernel.
Linux version 2.6.12.6-arm1 (jack@SWTEST2) (gcc version 3.3.3) #32 Tue Jan 23 17:11:52 CST 2007
CPU: ARM926EJ-Sid(wb) [41069260] revision 0 (ARMv5TEJ)
CPU0: D VIVT write-back cache
CPU0: I cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
CPU0: D cache: 32768 bytes, associativity 1, 32 byte lines, 1024 sets
Machine: MV-88fxx81
Using UBoot passing parameters structure
Sys Clk = 166000000, Tclk = 166000000


- Warning - This LSP release was tested only with U-Boot release 1.7.3

Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists
Kernel command line: root=/dev/ram console=ttyS0,115200 :::DB88FXX81:egiga0:none
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB 0MB 0MB 0MB = 64MB total
Memory: 55936KB available (2466K code, 454K data, 112K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 5826K
NET: Registered protocol family 16

  Marvell Development Board (LSP Version 1.7.6_NAS)-- RD-88F5181-88SX7042-2xSATA

 Detected Tclk 166000000 and SysClk 166000000
Marvell USB EHCI Host controller #0: c03ab980
pexBarOverlapDetect: winNum 2 overlap current 0
mvPexInit:Warning :Bar 2 size is illigal
it will be disabled
please check Pex and CPU windows configuration
PCI: bus0: Fast back to back transfers disabled
PCI: bus1: Fast back to back transfers enabled
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
cesadev_init(c0012498)
Fast Floating Point Emulator V0.9 (c) Peter Teichmann.
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
Serial: 8250/16550 driver $Revision: 1.1.1.1 $ 4 ports, IRQ sharing disabled
ttyS0 at MMIO 0x0 (irq = 3) is a 16550A
io scheduler noop registered
io scheduler deadline registered
RAMDISK driver initialized: 16 RAM disks of 10240K size 1024 blocksize
loop: loaded (max 8 devices)
Marvell Gigabit Ethernet Driver 'egiga':
  o Ethernet descriptors in DRAM
  o DRAM SW cache-coherency
  o Checksum offload enabled
  o Loading network interface 'egiga0'
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
physmap flash device: 800000 at ff800000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
cmdlinepart partition parsing not available
RedBoot partition parsing not available
Using physmap partition definition
Creating 5 MTD partitions on "phys_mapped_flash":
0x00000000-0x00010000 : "MTD1"
0x00010000-0x00020000 : "MTD2"
0x00020000-0x001a0000 : "Linux Kernel"
0x001a0000-0x007d0000 : "File System"
0x007d0000-0x00800000 : "u-boot"
ehci_platform ehci_platform.20865: EHCI Host Controller
ehci_platform ehci_platform.20865: new USB bus registered, assigned bus number 1
ehci_platform ehci_platform.20865: irq 17, io mem 0x00000000
ehci_platform ehci_platform.20865: park 0
ehci_platform ehci_platform.20865: USB 0.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
mice: PS/2 mouse device common for all mice
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-d...@redhat.com
NET: Registered protocol family 2
IP: routing cache hash table of 512 buckets, 4Kbytes
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)
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: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 112K
init started:  BusyBox v1.00-pre1 (2006.07.17-10:17+0000) multi-call binary
init started:  BusyBox v1.00-pre1 (2006.07.17-10:17+0000) multi-call binary
Starting pid 218, console /dev/ttyS0: '/etc/rc.sh'
Check MTD block device V2.01.05162006
        MTDC: Mount MTD1 done.
        MTDC: Mount MTD2 done.
        MTDC: No need to copy file.
** Mounting /etc/fstab
umount: proc: not mounted
umount: proc: not mounted
umount: /image.cfs: not mounted
umount: /image.cfs: not mounted
** check raid Config version
Don't Update raidtab2web
** copy mtd1 files
cp: /sys/mtd1/upnpav.conf: No such file or directory
cp: /sys/mtd1/firmwareupdate: No such file or directory
cp: /sys/mtd1/ftpaccess: No such file or directory
cp: /sys/mtd1/ftp_tbl: No such file or directory
cp: /sys/mtd1/hd_magic_num: No such file or directory
cp: /sys/mtd1/upnp_serialnum.conf: No such file or directory
cp: /sys/mtd1/onedisk: No such file or directory
cp: /sys/mtd1/onedisk: No such file or directory
mv: /sys/mtd1/firmwareupdate: No such file or directory
mv: /sys/mtd1/restore: No such file or directory
mv: /sys/mtd1/format_ok: No such file or directory
mv: /sys/mtd1/pls_sync: No such file or directory
mv: /sys/mtd1/pls_chmod_a2: No such file or directory
mv: /sys/mtd1/pls_chmod_b2: No such file or directory
cp: /sys/mtd1/ftpgroup: No such file or directory
mv: unable to rename `/tmp/hd_magic_num': No such file or directory
** link lib **
** link web **
** link /usr/bin **
** link /usr/sbin **
** link /usr/local/LPRng **
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
<rtc>: getRTC time= 120/0/0 0:40:40
<rtc>Wrong rtc date format
Sat Jan  1 00:00:00 UTC 2005
System time: 200TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
5/1/1 Sat 0:0:0
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
set default time to 2005/1/1 saturday 00:00:00
<fan script start>
TWSI: mvTwsiStartBitSet ERROR - Start Clear bit TimeOut .
** set loopback interface
MAC = 00:19:5B:EE:DD:A5
egiga0: mac address changed
** Activate Gigabit Interface
<reboot now>
The system is going down NOW !!
Sending SIGTERM to all processes.
Sending SIGKILL to all processes.
Please stand by while rebooting the system.
md: stopping all md devices.
md: md0 switched to read-only mode.
Restarting system.
Reseting !!
 ** LOADER **
 ** MARVELL BOARD: RD-88F5181-POS-NAS LE

João Cardoso

unread,
Apr 6, 2016, 11:49:37 AM4/6/16
to Alt-F


On Wednesday, 6 April 2016 07:17:32 UTC+1, Lui Massango wrote:
Greetins everybody

I was wondering if i could get some help on this,
recently i got my dns323 a1, bricked, i don´t know how, suddenly the blue power light started blinking repeatedly,
i tried to recovery it, flashing the firmware 1.03 which is the stock firmware, following the steps on this tutorial: http://dns323.kood.org/howto:reflash_from_windows,
but although the process apparently finished successfully, it did´nt resolve the problem,

Did some reading and found about alt-f, i find it great and i would really like the box to be running something like this,
so i downloaded the firmware, splitted it with dn323-fw as instructed, but when i try to flash it i get the error: Ramdisk Size = 6412746 error,Ramdisk size > 005e0000 byes

Yes, marvell u-boot has a maximum limit on the kernel and rootfs size that it can load/flash, and Alt-F uses almost all flash memory size available. I.e., Alt-F kernel and rootfs are too big for marvell u-boot to handle. I think to remember that even some later D-Link kernel/rootfs versions are too big to be being flashed from u-boot.
Flashing from the webUI poses no such problems, but you don't have it.
You might try to flash other kernel/rootfs, such as the ones from Debian, which are also small.



Question: it´s there a workaround to get alt-f flashed to this box via serial port?

Can you post your box available u-boot commands? Usually typing just a a '?' or 'h' show them; try also 'printenv' and post the results.

On some boxes, u-boot has commands to load a kernel and a rootfs into memory, and start booting/executing them from there, instead of flashing them.
On some boxes those "load into memory commands" uses fixed memory address, so after loading the kernel one has to copy it to another existing memory area, them load the rootfs, them boot them.
There are some old example on that on the "custom firmware" dns323.kood.org DNS-323 sub-forum




PLEASE HELP, i´m really desperate to get this box alive,

below its how my boot log looks, in case it could be helpful,

thanks in advance

I see nothing wrong with the boot log, except from the " TWSI: mvTwsiStartBitSet" errors, but those errors also appear on bootlogs from people that succeeds booting, so that must not the source of the failure.
From your boot log the boot succeeds, but after everything being started OK the system reboots itself. Try booting without hard disks plugged, they are not needed and might contain a faulty ffp or other script that causes the reboot.
You might also boot without the network cable attached, as the reboot seems to happens right after the network interface being initialized.

Luis Massango

unread,
Apr 6, 2016, 4:47:17 PM4/6/16
to al...@googlegroups.com
Thanks for the great tips Jcard, it was related to the network cable, i unplugged it, 
and booted to dlink fw103, and then managed to inject alt-f from webgui

thanks a lot

Reply all
Reply to author
Forward
0 new messages