Welcome! Log In Create A New Profile

Advanced

Dockstar Please check your kernel config and/or bootloader.

Posted by droidbox 
Forum List Message List New Topic
droidbox
Dockstar Please check your kernel config and/or bootloader.
December 20, 2021 10:37AM
Hi.

I found another old Dockstar while cleaning up.
Unfortunately, the dockstar no longer boots.

So I have set up a USB stick with Debian. Unfortunately, there are also problems with the start. 

U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
5435888 bytes read in 1068 ms (4.9 MiB/s)
9671091 bytes read in 1071 ms (8.6 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.13.6-kirkwood-tld-1
   Created:      2021-09-24   0:22:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5435824 Bytes = 5.2 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.13.6-kirkwood-tld-1
   Created:      2021-09-24   1:06:32 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    9671027 Bytes = 9.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
   Loading Ramdisk to 071d6000, end 07b0f173 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Error: invalid dtb and unrecognized/unsupported machine ID
  r1=0x00000bb6, r2=0x00000100
  r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
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.

DockStar> printenv 
arcNumber=2998
bootargs_console=console=ttyS0,115200
bootargs_root=ubi.mtd=1 root=ubi0:root rootfstype=ubifs ro
bootcmd=run bootcmd_usb; bootm 0x00800000 0x01100000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /boot/uImage; ext2load usb 0:1 0x01100000 /boot/uInitrd
bootdelay=2
bootdev=usb
device=0:1
devices=usb
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-dockstar.dtb
ethact=egiga0
ethaddr=00:10:75:1A:B7:CF
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 2743/131068 bytes
Does anyone have a tip for me?
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 20, 2021 04:09PM
droidbox,

> I found another old Dockstar while cleaning up.
> Unfortunately, the dockstar no longer boots.

The u-boot image is the latest, but the envs are messed up! so you need to restore the good version. Here is how to boot with uEnv.txt:

https://forum.doozan.com/read.php?3,116134,116139#msg-116139

Exept that you need to use the Dockstar DTB, so the adjustment for the DTB file name should be: 

dtb_file=/boot/dts/kirkwood-dockstar.dtb

After you can boot correctly, save the envs permanently, either by

- reflashing the envs image in Debian.

OR

- do saveenv in serial console (please post back here after you booted into Debian, and I'll show you how to do it safely).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 03:30AM
Hi bodi.

Your tips above, I have already tried, but made no difference.
Then I found the following while searching.

After that, the system boots properly. But after a reboot it does not work again. 

run bootcmd_uenv

DockStar> run bootcmd_uenv
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

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

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            31250432        1d48cb6e-01     83

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
2774 bytes read in 984 ms (2 KiB/s)
importing envs ...

Warning: egiga0 MAC addresses don't match:
Address in SROM is         52:3b:20:9c:11:51
Address in environment is  00:10:75:1a:b7:cf
 DockStar> boot
How can I save this now?
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 03:39AM
droidbox, 

run bootcmd_uenv

Yes, I forgot to mention that! the 1st boot with the uEnv.txt you have to do that.

>How can I save this now?

Once you can boot reliably a couple times by doing 

run bootcmd_uenv
boot

Come back to u-boot console one more time and do 

run bootcmd_uenv
saveenv
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 03:44AM
bodhi, it rocks perfect. Now I can boot into the Alpine Linux. Great.

One more question ;-)

How can I disable this message at the boot? 
1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'

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

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            31250432        1d48cb6e-01     83

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
2774 bytes read in 984 ms (2 KiB/s)
Unknown command 'ide' - try 'help'
Unknown command 'mmc' - try 'help'
importing envs ...
running scan_disk ...
Scan device usb
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 02:14PM
droidbox,

To make the log less noisy for this box, set these envs (either in serial console with setenv, or in LInux command line with fw_setenv):

There is no MMC or SATA on the Dockstar, so 
setenv devices usb

This is really should not be changed, in case you have more than one USB plugged in. But you can play with the number of drives. Below is 4 drives. 
setenv disks '0 1 2 3'

And this message can not be silenced when u-boot scans the USB port to find the disk with kernel files on it. 
## Unknown partition table type 0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 02:27PM
Thank you very much.

It rocks now perfect for me, with Alpine Linux on the dockstar.

droidbox
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 03:32PM
Hey droidbox,

>
> It rocks now perfect for me, with Alpine Linux on
> the dockstar.

Could you post a short summary like which u-boot version is installed. And u-boot envs (only if you have to change any envs to boot Alpine), or is it just the same as booting Debian

And 
uname -a
cat /etc/os-release

Thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 03:42PM
u-boot
U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700)
uname -a 
Linux dockstar 5.13.6-kirkwood-tld-1 #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021 armv5tel Linux
cat /etc/os-release 
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.11.2
PRETTY_NAME="Alpine Linux v3.11"
HOME_URL="https://alpinelinux.org/";
BUG_REPORT_URL="https://bugs.alpinelinux.org/";
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 21, 2021 06:15PM
Up in the Wiki thread


Quote

Booting Other Linux Distros on Pogoplug

How to boot recent Arch Linux ARM rootfs with bodhi's released u-boot (with separate DTB)
How to boot older Arch Linux ARM rootfs with bodhi's released u-boot (with embedded DTB)
How to boot Void Linux with bodhi's released u-boot
How to boot Alpine Linux with bodhi's released u-boot and kernel

Thanks!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 02:04AM
Hi bodhi.

I have find an old dockstar on ebay for anly 5€.
When I get the dockstar I will write a tutorial on how to get an Alpine installed.
Reply Quote
davidalfa
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 03:00AM
What's the benefit of Alpine Linux over standard Debian?
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 03:13AM
For me, booting ist faster and and the rootfs is only 200MB
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 03:37AM
> What's the benefit of Alpine Linux over standard
> Debian?

Whatever rocks your boat! every distro has pros and cons.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 05:13AM
Hi bodi.

This morming, a collegue ou me bring me his bricked dockstar.
I install a fresh USB stick with "Linux Kernel 5.15.5 Kirkwood package and Debian rootfs" and put it in the dockstar.
It comes the same error as above 
Uncompressing Linux... done, booting the kernel.

Error: invalid dtb and unrecognized/unsupported machine ID
  r1=0x00000bb6, r2=0x00000100
  r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
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.

So I run 
 run bootcmd_uenv
bit it comes with a new message for me
Unknown command 'for' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'for' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'if' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'fi' - try 'help'

The dockstar boot message is 
U-Boot 2014.10+dfsg1-5 (Apr 07 2015 - 21:52:11)
Seagate FreeAgent DockStar

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Warning: Your board does not use generic board. Please read
doc/README.generic-board and take action. Boards not
upgraded by the late 2014 may break or be removed.
How can I fix the error? 
DockStar> printenv 
baudrate=115200
bootargs=console=ttyS0,115200
bootargs_console=console=ttyS0,115200
bootargs_root=ubi.mtd=1 root=ubi0:root rootfstype=ubifs ro
bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; bootm 0x00800000 0x01100000
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /boot/uImage; ext2load usb 0:1 0x01100000 /boot/uInitrd
bootdelay=3
ethact=egiga0
ethaddr=00:10:75:1a:bf:90
init_ide="ide reset"
init_mmc="mmc rescan"
init_usb="usb start"
initrd=/boot/uInitrd
kernel=/boot/uImage
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1m(uboot),-(root)
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 1459/131068 bytes



Edited 1 time(s). Last edit at 12/22/2021 05:13AM by droidbox.
Reply Quote
daviddyer
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 09:54AM
This uboot is older. (U-Boot 2014.10+dfsg1-5). It doesn't support bootcmd_uenv command.

Solution:
1 build a debian usb disk with embeded dtb file.
2 boot with that usb.
3 update uboot to 2017 then you can copy your experience.
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 10:01AM
If you read my last command, I install a fresh usb stick with a new "Linux Kernel 5.15.5 Kirkwood package and Debian rootfs".
I look on the stick and the /boot/dts/kirkwood-dockstar.dtb is present.
Reply Quote
daviddyer
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 11:38AM
you need to combine the kernel with the dtb into one file.

this is required for old u-boot to boot new kernel.

something like this 


cd /boot
mv uImage uImage.orig
mv uInitrd uInitrd.orig
cp -a zImage-5.15.5-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-dockstar.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.15.5-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.15.5-kirkwood-tld-1 -d initrd.img-5.15.5-kirkwood-tld-1 uInitrd



Edited 1 time(s). Last edit at 12/22/2021 11:39AM by daviddyer.
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 22, 2021 03:08PM
droidbox,

Please post the entire serial console log. It is hard to see the problem with excerpts.

But David is probably correct. This u-boot might not have FDT capabilty so loading the DTB separately might not work.

Quote

Warning: Your board does not use generic board. Please read
doc/README.generic-board and take action. Boards not
upgraded by the late 2014 may break or be removed.
How can I fix the error?

The above is not an error, just a warning. You can safely ignore it. 

DockStar> printenv 
baudrate=115200
bootargs=console=ttyS0,115200
bootargs_console=console=ttyS0,115200
bootargs_root=ubi.mtd=1 root=ubi0:root rootfstype=ubifs ro
bootcmd=setenv bootargs ${bootargs_console}; run bootcmd_usb; bootm 0x00800000 0x01100000

So you (or somebody) did populate the envs with the new set coming from my u-boot builds. That's not the right thing to do. We should use the envs that came with this u-boot. And then after it booted, install new u-boot.

But anyway, best to see the entire log before I'll recommend the next step.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 01:03PM
Hey.

I have entered the commands. Unfortunately, it still gets stuck in a kernel error.

Then I copied the "u-boot.kwb" to the USB stick and entered the following commands: 

DockStar> fatload usb 0:1 0x0800000 u-boot.kwb
DockStar> nand erase 0x0 0x80000
DockStar> nand write 0x0800000 0x0 0x80000
DockStar> reset

Now, unfortunately, nothing happens, and no LED flashes anymore.
Have I now bricked it?
Reply Quote
davidalfa
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 02:47PM
If you feel brave enough, you can directly upgrade u-boot from uboot itself.
Download uboot.2017.07-tld-1.dockstar.bodhi.tar from here:
Extract it, rename the kwb file to "uboot.kwb", copy it to a usb drive, plug it into the Dockstar and boot into u-boot: 

usb start
ls usb 0
If you see the files of the usb root folder including "uboot.kwb", proceed with next step. 
load usb 0 0x800000 uboot.kwb
It should load the file to the memory and show "524288 bytes read in xx ms".
Danger! Next step will wipe existing u-boot and store the new one.
A power failure would brick it, requiring jtag recovery!
If any command fails, don't turn it off, ask here! 
nand erase 0x0 0xA0000
nand write 0x800000 0 0x80000
And it'll be done. Reboot and enjoy.



Edited 1 time(s). Last edit at 12/28/2021 03:16PM by davidalfa.
Reply Quote
droidbox
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 02:57PM
I have made this commands all, but now no LEDs blinking :(

What is a jtag recovery?



Edited 1 time(s). Last edit at 12/28/2021 02:57PM by droidbox.
Reply Quote
davidalfa
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 03:15PM
Edit: Oh, it was already bricked. I didn't read the last message before writing that! Phew...
Was exactly what you already did, looks good shouldn't have bricked it...
Was the kwb for the dockstar? Strange... I've done that few times without any problem...

JTAG... I'll help you in what I can.
It's easy, but not as simple as you'd probably wish, requiring soldering some wires and something to interface the jtag.
Do you have any Raspberry Pi, STM32 Blue Pill...?
Cheapest Blue Pill I found- Normal shipping, they charge 3x for 10-day delivery, which might actually be the same thing.
Here's my JTAG writeup using a stm32 bluepill.

You don't need the ST-Link, STM32s have a bootloader that allows programming through the serial port, so you only need the serial port adapter you're using for the Dockstar.



Edited 17 time(s). Last edit at 12/28/2021 05:24PM by davidalfa.
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 03:56PM
droidbox & David,

> I have made this commands all, but now no LEDs
> blinking :(

Yeah, it was bricked!

> What is a jtag recovery?

See the Wiki thread (you will need to solder the JTAG header):

https://forum.doozan.com/read.php?2,23630

Quote

Unbricking with Serial Console & JTAG console

How to unbrick your box using serial console with kwboot
Repair Pogo E02 with Raspberry PI (JTAG) and OpenOCD
Serial Port connector - what are people using to make it work
Serial Console hookup - GoFlex Net (external link)
Serial Console hookup - Pogoplug E02 and Pogoplug Pro V3 (external link)
OSX Serial/Net Console
Use Phone Jack - Phone Jack Serial Console Pics
Adding serial connector to Pogoplug Mobile (external link)
WD Mycloud EX2100/4100 Serial Console pic1, also pic2, pic3
Dreamplug Serial Console
kwboot on Mac OSX 10
Unbrick a Pogoplug Pro v3 OXNAS by flashing u-boot in serial console
Unbricking Synology Diskstation DS414 - See also the working thread for this unbricking session
Restore Netgear Stora FW
Unbricking Netgear Stora using chainload method
Unbricking the Netgear Ready NAS Duo v2
Unbricking (Restore Factory Firmware) Netgear ReadyNAS RN102/104

Yes, the danger with doing things in serial console is that you cannot copy/paste the instruction (for Linux shell) so sometime a typo would brick the box. That's why I did not provide serial console instruction for general usage, only when somebody asks for it.

And this box does not have UART booting, so the next step is JTAG to unbrick.

This SoC also has USB boot (put the u-boot image on USB flash so the BootROM can find it when NAND failed), but I have not tried.

Perhaps David can play with the USB boot mode? Let me check the Function Specs.

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



Edited 2 time(s). Last edit at 12/28/2021 04:52PM by bodhi.
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 03:59PM
David,

Quote

Not surprising Bodhi didn't suggest this. It's too easy to mess something up. Stupid me. Never going to suggest this again.

I think it's OK in some circumtances, but with a big red warning :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 05:02PM
> This SoC also has USB boot (put the u-boot image
> on USB flash so the BootROM can find it when NAND
> failed), but I have not tried.
>
> Perhaps David can play with the USB boot mode? Let
> me check the Function Specs.

I did not remember correctly! there is no USB boot mode for this SoC. Only SATA, SPI, PCIe, and UART.

So JTAG is the next step to unbrick for the Dockstar.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
davidalfa
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 05:17PM
Sadly, no USB boot for this SOC. UART booting doesn't work with this soc version(A0). Later revisions(A1) do work.
Anyways, the bootrom doesn't automatically test every boot source, it's the bootstrap resistors which config this, they would need to be modified to change the boot source, like I did to boot from sata.

droidbox, if you're getting a stm32 board, ensure it's not a CH32F103 clone, these have a lot of compatibility issues.
It must be a STM32F103C8, or CB, but not a C6.
(C6=32KB flash, C8=64KB, CB=128KB). The Versaloon firmware requires 64KB.

Then it's pretty simple, all it takes is soldering 6 wires.



Edited 5 time(s). Last edit at 12/28/2021 05:29PM by davidalfa.
Reply Quote
bodhi
Re: Dockstar Please check your kernel config and/or bootloader.
December 28, 2021 10:01PM
This SoC does have UART booting and all boot modes are tried. But the problem is with the BootROM version on Dockstar.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
daviddyer
Re: Dockstar Please check your kernel config and/or bootloader.
December 29, 2021 01:01PM
http://www.yourwarrantyisvoid.com/2010/09/08/dead-dockstar-resurrected-with-jtag/

You don't need to make a perfect cable like the guy in the article. Just solder a few pins... and do it...


I followed that instruction and revived my dockstar about 10 (?) years ago.
Reply Quote
davidalfa
Re: Dockstar Please check your kernel config and/or bootloader.
December 31, 2021 07:20AM
You can get te usb blaster for 3€:
https://a.aliexpress.com/_veAQPj
Reply Quote
Page 1 of 2    Pages: 12Next
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: