Debian on TBS2921 MOI+

Hallo everybody,
i have this hardware, from tbs,
named moi+
thank for making it possible to install debian on it
now, being able to run debian from usb,
i would like to try to launch the stock kernel
and to no avail with the new uboot from bodhi
original uboot is gone, and i can|t find it on tbs servers.
i tried it with other u-boots, mainly from openwrt,
also with negative results: also have i no idea about
mtd layout etc could i expect some help from this forum?
thanx, alex



Edited 1 time(s). Last edit at 11/11/2024 03:38AM by ri8.

alex,

> i have this hardware, from tbs,
> named moi+

I'm not familiar with this board. Can you post the specs and/or any info about it.

> thank for making it possible to install debian on
> it
> now, being able to run debian from usb,

Cool! please post the boot log to Debian. If you have serial console connected then post the entire serial log.

> i would like to try to launch the stock kernel
> and to no avail with the new uboot from bodhi

Which u-boot binary did you install from the release thread?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

i've used your latest kwboot for nsa325; i also used one for nsa325 from openwrt in the past,
which were unstable; the hardware seems to be wery close to kirkwood LaCie network router,
but also here i was to able to boot device successfully;
the reason i'd like to try stock is onboard eth and wifi devices, which as in seems
do not have linux support anymore; it is an alaska driver then on 2.6 kernel

https://sourceforge.net/projects/moiplus/files/Files/kernel/MOI%2BKernel-2.6.35.tar.bz2
https://sourceforge.net/projects/moiplus/files/Files/cross_compile_tool/moiplus_corss_compile_tool.zip

managed to compile it, but found no u-boot there.
regards, alex

alex,

> i've used your latest kwboot for nsa325; i also
> used one for nsa325 from openwrt in the past,
> which were unstable; the hardware seems to be wery
> close to kirkwood LaCie network router,
> but also here i was to able to boot device
> successfully;

You did not post the complete boot log. I need to see the kwboot boot log from the kwboot command until the Debian login prompt (or when it stucks).

And you should find the specs for this box. This is not on WikiDevi or TechInfoDepot, so I can't judge if the NSA325 or which boards will be appropriate to use.

> the reason i'd like to try stock is onboard eth
> and wifi devices, which as in seems
> do not have linux support anymore; it is an alaska
> driver then on 2.6 kernel

If it is a Marvell Alaska driver then it should be in the latest kernel.

Also, when you say the hardware is close to LaCie routers, it is a router with 1 WAN and 4 LAN ports? If so, the Ethernet chip is a Marvell switch, i.e. the driver is not a normal Ethernet driver. So the NSA325 DTB is not good enough.

>
> https://sourceforge.net/projects/moiplus/files/Files/kernel/MOI%2BKernel-2.6.35.tar.bz2
> https://sourceforge.net/projects/moiplus/files/Files/cross_compile_tool/moiplus_corss_compile_tool.zip
>
> managed to compile it, but found no u-boot there.

If there is no back up file for mtd0 (where u-boot is), then I think you're almost out of luck. Did you look at other files at that source forge website https://sourceforge.net/projects/moiplus/ ? might be u-boot image is inside one of those files.

There are more board DTBs that you should try, though.

- Recreate the uImage with the kirkwood-ea4500.dtb (in the rootfs /boot/dts/). This Linksys board based on the 6282 SoC, and uses the Marvell mv88e6085 switch chip.
- kwboot with my NSA325 2017.07 u-boot.

====

You can also try these 2 DTBs. These also use the Marvell mv88e6085 switch chip.

kirkwood-l-50.dtsb
kirkwood-qizhitong_501m_v2.dtb

====

Open up the box, and take a look around, you should see the Marvell switch chip marking. Please post this info.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

it is the board named moi2-2923, with those ports:

1 eth -> opposite to chip MV 88E1516
2 USB2.0 > chip opposite to it SKHynix H27U4G8F2DTR BC
1 serial
1 minipci
1 wlan > Realtek RTL8188 EUS
1 sata

4 chips SKHynix H5TQ2G83CFR H9C - accordinly 2 of them on a front/ and a back side, opposite to all ports;
i supposed that all ext. ports are the west, if so, then sata port and minipci port are placed norh of processor, and
those 4 chips are placed east

a. Icant' take off the heat sink from processor without breaking 2 plastic things attaching it to the board
b. The dmesg while booting ( with a sata (5v 1A) 1T Toshiba drive attached to sata port )from usb drive on upper USB port.
c. i can also boot from it , if attached on sata port, but got KP on not finding it after the kernel boots;
d. tried to boot from it if attached as a USB3.0 (in his original casing without extra power supply), fails to initialize, constantly clicking.
e. did't tried another to dtd options jet

It's 12v 2A power supply feeding it ; there is also a twin sat2 minipci card around,
wonder if it will not be to much for this small board, if booting from sata drive

alex,

Quote

1 eth -> opposite to chip MV 88E1516

If there are no LAN port, then it is a bit simpler. It's not a router.

However, this Marvell Alaska chip is usually used in the later SoCs such as Armada 37x or 38x. It's rarely seen in a Kirkwood box.

Boot with NSA325 DTB, and log in with serial console. And do

modprobe mvneta

And then check

dmesg | tail -20
ethtool eth0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hold on! let me revise the post above. It's not enough.

But I also need to see how you boot this at serial console. Please post the log (from u-boot banner until the error).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/27/2024 03:42PM by bodhi.

bodhi,


i've tried,
nsa325 and ea4500 as well
also with the ea4500.dtb, again "no PHY"

with 2 another dtb's your suggested no results, too

one of openwrt builds
initiates eth0, but was compl. unusable because
of unstoppable output on ssh;
thats the reason i've tried LaCie kernel then, since it
has nearly the same chip

Regards,
alex

Yes, here it is

Alex,

What are the u-boot envs you use to boot this box?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Boot with NSA325 DTB in the uImage.

In serial console, add this to your bootargs before booting the kernel.

initcall_blacklist=mv643xx_eth_init_module

And log into Debian in serial console,

modprobe mvneta
dmesg
ethtool eth0
ifconfig -a

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

i found in the stock initramfs
many blacklist files in /etc/modules.d
in one of them watchdog.. something
are 2-3 mv..... drivers with a comment,
they may not be initialized before watchdog is running
Says nothing to me, but, you know..

i had the stock things, as i compiled then the source;
so, my be should i
give a try to stock zImage with , say ea.4500.dtb and stock initramfs;
since i have also their rootfs (about 86mb), and
if i formated usb to ext2, and put that rootfs on,
may be one can expect some results?

Regards, Alex

alex,

That's not how we do it. To add a new parameter to bootargs before booting, you add it to the current bootargs env.

Your boot envs:

bootargs_linux=console=ttyS0,115200 rootdelay=3 loglevel=7 root=/dev/sda1 rw
bootcmd=run bootcmd_linux
bootcmd_linux=setenv bootargs $bootargs_linux; mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $load_uimage_addr /boot/uImage;bootm $load_uimage_addr

So,

setenv bootargs_linux 'console=ttyS0,115200 rootdelay=3 loglevel=7 root=/dev/sda1 rw  initcall_blacklist=mv643xx_eth_init_module'

andn then

boot

An don't use the EA4500 DTB, it is not the right one, use the NSA325 DTB.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

it' second partition of a drive where i put rootfs
if i'm wrong,i i 'll reformat it, and make the test again.

Sorry, forgot to mention;
i have a wifi atheros card (mini-pci),
it's working, 2-3 steps
to configure it, and i can
have all the devel tools on
the box, may be it could be usefull;

> Sorry, forgot to mention;
> i have a wifi atheros card (mini-pci),
> it's working, 2-3 steps
> to configure it, and i can
> have all the devel tools on
> the box, may be it could be usefull;

Yes. It's a good idea to get Wifi working first.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

How about

modprobe mvneta
ifup -a

And then check

dmesg | tail -20
ethtool eth0

Not sure if this is enough to make it work. The problem is we don't know the hardware enough, and cannot log in to stock FW to see the addresses of the Ethernet PHY.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/28/2024 05:30PM by bodhi.

obviously, no wifi network
because of no iw-tools present;
i recall about the previous rootfs you've
posted, which i already tried last
year, it had iw tools onboard- or was it
wifi-supplicant; then, having full i-net
access, i've tried something with debootstrap(forgot the details)
but failed to come forward, lacking debian knowleage and time:
It should be of no big effort to put some debian
packages to usb and install them on the next boot.
deb is not present, but apt-get and dpkg well.
Regards.
Alex

alex,

Another test. This time use the Dell Kace M300 DTB to create uImage.

/boot/dts/kirkwood-m300.dtb

Try kwbooting again with the NSA325 u-boot. This time do not blacklist the mv643xx_eth_init_module

setenv bootargs_linux 'console=ttyS0,115200 rootdelay=3 loglevel=7 root=/dev/sda1 rw  initcall_blacklist=mv643xx_eth_init_module'

And do not modprobe mvneta

modprobe mvneta

Just check dmesg and ethernet to see it'd make any difference.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi,

miraculously, in worked!
but, this unstoppable echo,
wich i already had on some openwrt
install :-(
device get full inet access, managed to apt-get update
apt-get install wireles-tools, but
- dumb mistake - systemd get installed,
and now can't get rid of it because of
constantly loosing route on eth0

Regards, alex

alex,

Cool! So the PHY addr 0 was correct for this MOI+ board.

Another test. Here is the new M300 u-boot installation.

Debian on Dell Kace M300
https://forum.doozan.com/read.php?2,61344,131916#msg-131916

Download the tarball uboot.2022.04-tld-1.m300.bodhi.tar.

- Use uboot.2022.04-tld-1.m300.mtd0.kwb to kwboot (the same way described above).
- Use a new rootfs since yours was messed up by systemd. Create the uImage with the M300 DTB appended.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/30/2024 02:21PM by bodhi.

No way to boot it with kwboot,
breaks very early
have i to write it directly to mtd ?

alex,

> have i to write it directly to mtd ?

No it won't work. The M300 u-boot is for SPI flash. Yours is NAND flash.

> No way to boot it with kwboot,
> breaks very early

How did you run it? Please post the entire log (from kwboot command until it stops)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Here it is;
as i said, breaks very early,
had to launch immediatly
picocom again, in order
to stop ibooting to debian

Looks like the kwboot binary you used is old. See here for my latest binary:

https://forum.doozan.com/read.php?3,27280

The binary kwboot_static_2024.04-rc3 can be run on any ARM box.

And for old kwboot (e.g. in some Linux distros), the parameter -p is needed (it's deprecated in latest kwboot, but does not hurt)

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2022.04-tld-1.m300.mtd0.kwb -p

When you kwboot and don't want it to boot into Debian, don't attach the USB rootfs. It will error out and stop at the prompt.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I' using amd64 cpu comp as linux host;
the binaries placed on the link you posted
are the all ARM binary;

>>'The binary kwboot_static_2024.04-rc3 can be run on any ARM box.'


with the flag -p kwboot runs nicely with m300 u-boot,
(3 tmes tried)
but crushes at 98%

95 % [......................................................................]
98 % [..............................................................]
[Type Ctrl-\ + c to quit]


U-Boot 2022.04-tld-1 (Mar 20 2022 - 18:15:15 -0700)
Dell KACE M300

SoC: Kirkwood 88F6282_A1
Model: Dell KACE M300
DRAM:


Regards.
alex

Ah OK. It stopped because the M300 has 2GB RAM.

So let's try the Goflex Home u-boot. It has the 6281 SoC, but usually it will boot a 6282 box to the u-boot prompt. This is just to see if the NSA325 u-boot messed up the Ethernet too badly for the MOI+.

U-boot release thread:

Quote

Download U-Boot images at Dropbox:
....
uboot.2017.07-tld-1.goflexhome.bodhi.tar or
https://www.dropbox.com/s/klksl0vawkhie9r/uboot.2017.07-tld-1.goflexhome.bodhi.tar

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.goflexhome.mtd0.kwb -p
Sending boot message. Please reboot the target...\
.... 97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]

I remember now, i tried (m.b. year ago)
many kwb from all possible sites,
and only 2 of them -(nsa325 and maybe LaCie)
booted completely ; usb/sata worked only on that for nsa235
right know had i found on my hd a python script, that uploads binary on
uboot without working usb; somehow, i forgot about it, and not tried
at that time with the other one

alex

Alex,

Quote

> obviously, no wifi network
> because of no iw-tools present;
> i recall about the previous rootfs you've
> posted, which i already tried last
> year, it had iw tools onboard- or was it
> wifi-supplicant; then, having full i-net
> access,

You can chroot into the rootfs from Linux PC or VM to install the iw-tools.

Quote

I remember now, i tried (m.b. year ago)
many kwb from all possible sites,
and only 2 of them -(nsa325 and maybe LaCie)

Yeah. I thought it's worth a try.

Let me think what the next easiest step to do.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Alex,

Please try this new MOI+ DTB. I've removed a lot of stuff from the M300 DTS and made a new DTS for the MOI+.

Create new uImage with this kirkwood-moi-plus.dtb. Boot and capture the serial boot log (I need to see a complete log since there are activities that we cannot see with dmesg).

Also do

ethtool eth0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)