Quantcast
Channel: Linux Device Hacking
Viewing all 47021 articles
Browse latest View live
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 2:07 am
$
0
0
I could not see where is the LAN chip is, does it say 88E1318? if it does, then there is no need for another u-boot sub-version to use the RTL8169.

It looks like we need another build to take care of the 88E1318 PHY. I'll rebuild and upload.
↧
Search

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 2:14 am
↧
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 2:30 am
$
0
0
marlemion Wrote:
-------------------------------------------------------
> This one:
> http://abload.de/img/nsa310_lanbisgx.jpg
>
> I can confirm that this one is on my NSA310. If
> you read EDIT6 here:
>
> http://forum.doozan.com/read.php?3,12381,21223#msg
> -21223
>
> you will see that I mentioned it there, too.

OK. Got it. I think pengu misunderstood what I've asked up there :)). Now I reread what you post and looked at pengu's picture. We've confirmed that it is RTL8111DL. 

EDIT6: Well, the chip is a RTL8111d chip (so reported by linux kernel, the chip itself says RTL8111DL). This chips should be supported by the rtl8169.c driver provided by u-boot. However, I have difficulties to add it to the nsa310 uboot build.

The nsa310 code can be replicated to make a different nsa310 version, i,e. nsa310t (for TDC). It is clear that if we build it correctly to u-boot design standard, we do need either a subversion for the NSA310 (using make option and use ifdefs for the nework chip code), which I think where you ran into problem. Or making it a fully separated nsa310t board, which I think is justifiable since we already have nsa 310, 310s, 320, 320s, and 325.

I'm wondering where are other NSA310 owners who have the version that uses 88E1318 Alaska? ...Is that even true? i.e perhaps the 88E1318 code were wrong in the first place.
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 2:54 am
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 3:08 am
↧
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 3:33 am
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 3:43 am
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 4:04 am
↧
Search

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 5:53 am
$
0
0
both, the "ZyXEL" and the "TDC" brand has a Realtek LAN chip
I haven't seen any NSA310 with Marvell Chip
↧
↧

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 21, 2015, 8:35 am
$
0
0
Many thanks, Bodhi.

It works now!!! That's great!!!

Could you help to show how to update error kernal image in debian?Sorry i am not familar with it. Or is it possible to make original pogoplug system work again?

Thanks!
↧

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 21, 2015, 9:46 am
$
0
0
Hi,

the patches for the DT port of nsa3xx-hwmon are out per email to bodhi,
as this was tested on my NSA320 successfully, just a hint,

when looking through the sources I have found that at least three versions of NSA310 must be around,

an older one with a pcf8563 realtime clock at i2c adress 0x51 which has an mcu
and should be able to use nsa3xx-hwmon driver, this one very similar to NSA320,

than there are two other devices with DT descriptions in kirkwood-nsa310.dts and kirkwood-nsa310a.dts
which have both i2c attached sensor chips, one with an adi,adt7476 and the other a national,lm85
both at adress 0x2e, the latter does not have the red USB Led, that is the only difference, these two
will not work with nsa3xx-hwmon, only the old version which was a clone of the NSA320 in design,

so before anybody starts testing with nsa3xx-hwmon driver on NSA310 first check which variant you
have, with i2detect -l or i2cdetect -y 0 if there is something at adress 0x2e,

best wishes pbg4
↧

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 21, 2015, 11:15 am
$
0
0
pbg4,

Thanks! will try it shortly.
↧

Re: pogoplug E02 prompt "ERROR: can't get kernel image!", please help!

August 21, 2015, 11:20 am
$
0
0
doomgiant,

> Could you help to show how to update error kernal
> image in debian?Sorry i am not familar with it. Or
> is it possible to make original pogoplug system
> work again?

That error was not real. Right now, you can just remove the USB stick and it will boot into orginal Pogo OS. If that does not work, please post the u-boot envs while in Debian: 
fw_printenv
↧
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 11:29 am
$
0
0
pengu Wrote:
-------------------------------------------------------
> both, the "ZyXEL" and the "TDC" brand has a
> Realtek LAN chip
> I haven't seen any NSA310 with Marvell Chip

Do you have the orginal NSA310 dmesg output?

Or if marlemion indeed has the orginal 310 then it would clear up the confusion. The current NSA310 u-boot code patch I am using has the 88E1318, so it might have be a mistake, which has led me to assume that it was the right chip :)
↧

Re: (WIP) Linux Kernel 3.18.5 Seagate Business Storage NAS (CNSxxx) package

August 21, 2015, 11:48 am
$
0
0
Thanks luke, have been busy so I will take a look later.
↧
Search

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 21, 2015, 12:52 pm
$
0
0
Hello Guys
I have problems with nsa 325 v2.
I did everything, step by step on the solution but stil have problems , i dont have any more patient for that ..
I try to start linux from USB storage formated to ext2 but i have that information in console : 

U-Boot 2014.07-tld-3 (Mar 06 2015 - 21:30:53)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_??
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     63              15728577        100615b5-01     83 Boot
loading envs from usb 0 ...
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2931288 bytes read in 599 ms (4.7 MiB/s)
6535284 bytes read in 934 ms (6.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.0.0-kirkwood-tld-1
   Created:      2015-08-21  19:28:15 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2931224 Bytes = 2.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.0.0-kirkwood-tld-1
   Created:      2015-08-21  19:31:12 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
Using machid 0x118f from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: unrecognized/unsupported machine ID (r1 = 0x0000118f).

Available machine support:

ID (hex)        NAME
ffffffff        Generic DT based system
ffffffff        Marvell Kirkwood (Flattened Device Tree)

Please check your kernel config and/or bootloader.

Printenv: 
MODEL_ID=4495
arcNumber=4495
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; usb stop; run bootcmd_sata; reset
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=118f
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=nand_mtd:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
partition=nand0,2
preboot=setenv stderr serial; setenv stdin serial; setenv stdout serial; setenv baudrate 115200; setenv console ttyS0,115200; setenv bootdelay 10
rootdelay=10
rootfstype=ext2
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; setenv uenv_loaded 0; for devtype in usb; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if $devtype part $disknum; then run uenv_read; fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 2248/131068 bytes


I trying change kernel from 3.18 to new one but without succesful

Maybe some of You Guys can help me ?

Best Regards!
↧

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 21, 2015, 1:07 pm
$
0
0
hawryszka Wrote:
-------------------------------------------------------
> Hello Guys
> I have problems with nsa 325 v2.
> I did everything, step by step on the solution but
> stil have problems , i dont have any more patient
> for that ..
> I try to start linux from USB storage formated to
> ext2 but i have that information in console :
> 
> Part    Start Sector    Num Sectors     UUID      
>      Type
>   1     63              15728577       
> 100615b5-01     83 Boot
> loading envs from usb 0 ...
> ** File not found /boot/uEnv.txt **
> (Re)start USB...
> USB0:   USB EHCI 1.00
> scanning bus 0 for devices... 3 USB Device(s)
> found
>        scanning usb for storage devices... 1
> Storage Device(s) found
> 2931288 bytes read in 607 ms (4.6 MiB/s)
> 6535284 bytes read in 909 ms (6.9 MiB/s)
> ## Booting kernel from Legacy Image at 00800000
> ...
>    Image Name:   Linux-4.0.0-kirkwood-tld-1
>    Created:      2015-08-21  19:28:15 UTC
>    Image Type:   ARM Linux Kernel Image
> (uncompressed)
>    Data Size:    2931224 Bytes = 2.8 MiB
>    Load Address: 00008000
>    Entry Point:  00008000
>    Verifying Checksum ... OK
> ## Loading init Ramdisk from Legacy Image at
> 01100000 ...
>    Image Name:   initramfs-4.0.0-kirkwood-tld-1
>    Created:      2015-08-21  19:31:12 UTC
>    Image Type:   ARM Linux RAMDisk Image (gzip
> compressed)
>    Data Size:    6535220 Bytes = 6.2 MiB
>    Load Address: 00000000
>    Entry Point:  00000000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> Using machid 0x118f from environment
> 
> Starting kernel ...
> 
> Uncompressing Linux... done, booting the kernel.
> 
> Error: unrecognized/unsupported machine ID (r1 =
> 0x0000118f).
> 
> Available machine support:
> 
> ID (hex)        NAME
> ffffffff        Generic DT based system
> ffffffff        Marvell Kirkwood (Flattened Device
> Tree)
> 
> Please check your kernel config and/or
> bootloader.
>
>
> I trying change kernel from 3.18 to new one but
> without succesful
>
> Maybe some of You Guys can help me ?
>
> Best Regards!


First step: boot with 3.16 rootfs (simpler to setup):
http://forum.doozan.com/read.php?4,23425,23427#msg-23427

And then come back, we'll cover device tree for it.
↧
↧

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 21, 2015, 1:08 pm
$
0
0
hawryszka Wrote:
-------------------------------------------------------

> Using machid 0x118f from environment
> Starting kernel ...
> Uncompressing Linux... done, booting the kernel.
> Error: unrecognized/unsupported machine ID (r1 =
> 0x0000118f).
> Available machine support:
>
> ID (hex) NAME
> ffffffff Generic DT based system
> ffffffff Marvell Kirkwood (Flattened Device
> Tree)

It seems you are missing dtb file?
What's your printenv and uboot version?

Edit: try follow bodhi's advice and start with simpler setup!
↧

Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs

August 21, 2015, 1:25 pm
$
0
0
I have edited my previous post with printenv cmd and add uEnv.txt file.
Thanks for answer asap i try with 3.16 kernel, give me moment (i have hope it will be moment .. ;/ )
↧

Re: Zyxel NSA310 u-boot-2014.07-tld-4 for testing

August 21, 2015, 3:14 pm
$
0
0
nsa310 here, zyxel one.

It does seem to have indeed that realtek chip.

kwbooted and your uboot has no ethernet access.

rebooting into normal uboot, see below

uboot booting, look at last line about eth1 being [PRIME] (whatever that means)
It probably does something fishy and eth0 is either fake or not connected electrically (why?) 

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

U-Boot 1.1.4 (Jun  8 2011 - 18:48:37) 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 Total size 256MB  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)
Kernel address is 0x4640000.

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0, egiga1 [PRIME]

this is the first mention of eth, boots marvell driver then realtek one. 

[    1.897609] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.904949] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[    1.913257] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.918935] pci 0000:00:01.0: enabling device (0140 -> 0143)
[    1.925466] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd0912000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[    1.935135] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]


then I get multiple errors of marvell driver like below, suspectging the dts is wrong, it maybe says there is a marvell eth when there is none. I am using dts booting with dts in uimage (or zimage), kernel 3.17. dts nsa310, not nsa310a. 

[    2.990508] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral


then complains about firmware but eth0 works fine and gets IP from my router shortly afterwards on eth0.
Probably because it is not rtl816d but the rtl8111D like it detects above. 

[   18.227450] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168d-2.fw failed with error -2
[   18.236645] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168d-2.fw (-2)
[   18.264769] r8169 0000:01:00.0 eth0: link down
[   18.269244] r8169 0000:01:00.0 eth0: link down
[   18.273787] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready


the same marvell driver keeps erroring 5 times or so with the same line as above.

only eth I can detect with scans is the realtek one, no marvell ethernet.

there seems to be some significant confusion somehwere, I can assure you that this is NOT a nsa325, yet lshw tells me this 

description: Computer
    product: ZyXEL NSA325
    width: 32 bits
  *-core
       description: Motherboard
       physical id: 0
       capabilities: zyxel_nsa325 marvell_kirkwood-88f6282 marvell_kirkwood
     *-cpu
          description: CPU
          product: cpu
          physical id: 0
          bus info: cpu@0
     *-memory
          description: System memory
          physical id: 2
          size: 245MiB
     *-pci
          physical id: 1
          bus info: pci@0000:00:01.0
          version: 03
          width: 32 bits
          clock: 33MHz
          capabilities: pci bus_master
          resources: ioport:10000(size=4096) memory:e0000000-e00fffff
        *-network
             description: Ethernet interface
             physical id: 0
             bus info: pci@0000:01:00.0
             logical name: eth0
             version: 03
             serial: 00:00:00:00:00:30
             size: 100Mbit/s
             capacity: 1Gbit/s
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
             configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=10.42.0.58 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
             resources: irq:83 ioport:10000(size=256) memory:e0014000-e0014fff memory:e0010000-e0013fff memory:e0000000-e000ffff
In case you were wondering, yes it is connected to a crappy router, 100Mbit/s is normal.
↧
Viewing all 47021 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>