Jump to content

how to enable multi boot on original firmware of B860h


Recommended Posts

Posted

my device is using amlogic s905


U-Boot 2015.01-ge1b7b3f-dirty (Jul 22 2017 - 16:51:56)
Linux version 3.14.29-g9b417e7-dirty (wulinkui@A23131934)
 

here is the detail, device has been rooted

 

https://pastebin.com/H7NskL64

 

I have make bootable my sdcard with Armbian_5.89_Aml-s905_Debian_buster_default_5.1.0_desktop_20190617, but maybe original firmware doesn't support multi boot, which one that compatible with my amlogic and how to do that.

I have read 

there is 2 method to make multi boot, toothpick and and  update mode of the standard firmware

 

I have try to dd if=u-boot.bin of=/dev/block/bootloader

it won't run and my box become blank and I check from UART there is no boot log just 

 

set vddee to 1000 mv
~~~~.......................................................................................set vcck to 1120 mv

 

I jumper C125 while put power cable + put USB + power button then refirmware with original firmware to run android.

 

what I want to do is change android to armbian through make first to multiboot, 

CMIIW 

 

thank you and appreciate to response my question.

 

photo_2021-11-30_05-33-53.jpg

photo_2021-11-30_05-33-48.jpg

  • Ryanfab changed the title to how to enable multi boot on original firmware of B860h
Posted

Why are you not using the build linked to in the posted instructions?  Please follow the instructions as listed in the FAQ, starting with a freshly reinstalled working android firmware.  Does your board have a reset button to use the 'toothpick' method?

Posted

appriciate your response @SteeMan. now, I have fresh reinstall firmware and my android box is running and rooted,

but, my box doesn't boot from sdcard,  because I think it doesn't support multi boot,

my question is how to make my box start from sdcard ? 

do I need to change /dev/block/bootloader on my android ?

soo I can follow installation instruction.

FYI, my board doesn't have reset button.  

Posted

There won't be any compatible bootloader for your box so there isn't any boot loader to install.

You need to get multiboot working.  If you don't have a reset button (are you sure?  what is the thing in the upper right corner of your first picture?), then you are going to need to run the update through android.  Have you tried the update app method of installing multiboot?

Posted (edited)

@SteeMan, thanks for your response.

 

I found tool updater from windows command line that I can set uboot param like this

update bulkcmd “setenv -f EnableSelinux permissive”

update bulkcmd “saveenv”

 

I press switch button on upper right corner and put power switch and usb togather

I got this response

 

  Reveal hidden contents

 

 

what u-boot command to make it multiboot?

 

 

then I put sdcard with armbian image with modified extlinux, boot.ini, rename u-boot.ext

I still cann't boot to sdcard. need your guidance.

Edited by TRS-80
put long output inside spoiler
Posted

I'm still not understanding what instructions you are using nor what build you are using.

I want to correct a couple of items in your previous post.  You don't seem to be looking at the correct aml_autoscript as the 20.10_xxx_5.9.0 build doesn't have a line like setenv bootfromnand 0.

You mention modifying boot.ini, but that isn't a step that needs to be done. 

So again, I ask, what build are you using and what instructions are you trying to follow?

Finally, if you have a working console that you can access the u-boot command line from, then you should be able to just enter the commands one by one as they appear in the aml_autoscript file.

Posted (edited)

here my printenv

 

  Reveal hidden contents

 

 

 

Edited by TRS-80
put long output inside spoiler
Posted (edited)

just now I burn image on sdcard and change some file

 

boot.ini changed into this

ODROIDN2-UBOOT-CONFIG

if test "${devtype}" = ""; then setenv devtype "/dtb/amlogic/meson-gxl-s905x-p212.dtb"; fi

if fatload ${devtype} ${devnum} 0x1000000 u-boot.ext; then go 0x1000000; fi;

 

extlinux/extlinux.conf changed into this

 

LABEL Armbian
LINUX /zImage
INITRD /uInitrd

FDT /dtb/amlogic/meson-gxl-s905x-p212.dtb
APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

 

rename u-boot-s905x2-s912 to u-boot.ext

 

then I push the button to reset then i found it search on reading aml_autoscript

 

finally got this ## Error: "bootfromsd" not defined

 

  Reveal hidden contents

 

need advice about this

 

 

Edited by TRS-80
put long output inside spoiler
Posted

I try to execute start_mmc_autoscript

 

BULKcmd[run start_mmc_autoscript]
card in
[mmc_init] mmc init success
reading s905_autoscript
1765 bytes read in 5 ms (344.7 KiB/s)
## Executing script at 01020000
** Bad device usb 0 **
** Bad device usb 1 **
** Bad device usb 2 **
** Bad device usb 3 **
reading zImage
20537352 bytes read in 1141 ms (17.2 MiB/s)
reading uInitrd
9426258 bytes read in 522 ms (17.2 MiB/s)
reading uEnv.ini
209 bytes read in 7 ms (28.3 KiB/s)
reading /dtb/meson-gxl-s905x-p212.dtb
25911 bytes read in 9 ms (2.7 MiB/s)
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    9426194 Bytes = 9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
use dts in boot.img/recovery.img instead of dts partition.
"Synchronous Abort" handler, esr 0x96000210
ELR:     3fec18b4
LR:      3febcd24
x0 : 0000000000000000 x1 : 0000000000000000
x2 : 000000003fed3c20 x3 : 0000000000000001
x4 : 000000003be9c950 x5 : 0000000000000000
x6 : 00000000ffffffc8 x7 : 0000000000000044
x8 : 0000000000000031 x9 : 0000000000000000
x10: 000000000000000f x11: 000000003ff38e40
x12: 0000000000000000 x13: 0000000000000000
x14: 0000000000000000 x15: 0000000000000000
x16: 0000000000000000 x17: 0000000000000000
x18: 000000003be9ee28 x19: 000000003ff6f4c8
x20: 0000000000000000 x21: 0000000000000003
x22: 000000003beba388 x23: 0000000000000000
x24: 0000000000000000 x25: 000000003ff3f000
x26: 0000000000000000 x27: 000000003beba3b0
x28: 0000000000000000 x29: 000000003be9cbe0

Resetting CPU ...

resetting ...
~~~~....................................................................set vcck to 1070 mv
set vddee to 1070 mv


U-Boot 2015.01-ge1b7b3f-dirty (Aug 24 2017 - 23:11:22)

DRAM:  1 GiB
Relocation Offset is: 3eeaf000

not working

Posted

my image is Armbian_5.88_Aml-s905_Ubuntu_bionic_default_5.1.0_desktop_20190530.img

 

I guess the load address need to revise

 

setenv env_addr "0x10400000"

setenv kernel_addr "0x11000000"

setenv initrd_addr "0x13000000"

 

need suggestion

Posted (edited)

success to execute and running into armbian but from InUsbBurn mode.

 

with this command

 

update bulkcmd "run start_mmc_autoscript;"

 

any suggestion to make run on bootmode=NORM and install to mmc ?

 

  Reveal hidden contents

 

 

Edited by TRS-80
put long output inside spoiler
Posted

If you aren't going to follow the instructions on this site, which would include running the version the instructions point to, then I'm not able to help you.  You are trying to run a version that is different in many ways than the one the instructions are designed for.  Please try again with the correct build if you would like my help.

Posted

OK, now  that you have the latest build, I would recommend that you start over.  Reinstall a fresh android firmware and then try again.  Because you used an old build, that caused you to set uboot variables that are not correct for the latest build.

Also, it looks like you are using either the wrong dtb or the wrong u-boot.ext.  Since the dtb you mentioned above is for an s905x cpu (meson-gxl-s905x-p212.dtb) but you are using the s905x2 uboot.ext (rename u-boot-s905x2-s912 to u-boot.ext)

 

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines