hexdump0815/u-boot-misc

notes on building, preparing and installing u-boot for allwinner, rockchip, amlogic, exynos arm socs ...

u-boot-misc

compiling u-boot for allwinner, rockchip, amlogic arm socs ...

work in progress ...

u-boot-misc's Issues

boot_targets priority

strings ~/Downloads/gxl-u-boot.bin | grep boot_targets

boot_targets=romusb mmc0 mmc1 mmc2 usb0 pxe dhcp
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done

sometimes we need to boot from usb (ssd type usb for faster IO), right now i used a hex editor to change it to

boot_targets=usb0 romusb mmc0 mmc1 mmc2 pxe dhcp

which worked as expected.

but when there are 2 usb attached at the same time, the chance that our bootable usb got boot is 50% ... is it possible to define the boot_targets like this:

boot_targets=usb0 usb1 usb2 usb3 romusb mmc0 mmc1 mmc2 pxe dhcp

# and
bootcmd_usb0=devnum=0; run usb_boot # this one is already defined in the binary
bootcmd_usb1=devnum=1; run usb_boot
bootcmd_usb2=devnum=2; run usb_boot
bootcmd_usb3=devnum=3; run usb_boot

s905d here.

rockchip_rk33xx: problems: Help to overwrite boot of my Android on RK3328 A5X Max+

Hi hexdump,

My A5X Max+ is not booting from SD on Android 8.1 that has installed.

I have created a linux VM on My Virtualbox and tested UART, it is working fine, then i can start low level tests.

About your notes on following link:

https://github.com/hexdump0815/u-boot-misc/blob/master/readme.rk3328-no-sd-boot

About the following command on your notes:

dd if=uboot.img of=/dev/sdx seek=16384

Are there here on forum uboot.img to use or do i have to compile it?

That command is to write to /dev/sdx on tv box or on sd card to boot?

If the command is writen to tv box is it writen from UART connection?

About command:

rkdeveloptool wl 0x2000 u-boot-image-for-emmc-h96max-rk3328.img

Are there here on any forum valid img files that i can use of this type or do i have to compile it?

Another way to do it if i do not need to boot from SD, is it possible to write directly to emmc armbian (or other image like coreelec) image with any tool?

Regards

Jps1x2

support for Dram parametres on u-boot-misc

@hexdump0815 is it possible to add support to Dram parameters like below
the version of Das U-Boot" Source Tree and denx works but does not have the patches that you suggested in mainline readme.h616, my box tv need these parameters

CONFIG_DRAM_SUN50I_H616_DX_ODT=0x08080808
CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e
CONFIG_DRAM_SUN50I_H616_CA_DRI=0x0e0e
CONFIG_DRAM_SUN50I_H616_TPR10=0xf83438
CONFIG_MACH_SUN50I_H616=y
CONFIG_SUNXI_DRAM_LPDDR3=y
CONFIG_SUNXI_DRAM_H616_LPDDR3=y

Is there a typo in readme.exy?

Following this guide, i was unable to create a booting EMMC device as U-Boot complained about a CRC error. But when changing a line, it all worked.

In line 14, you copy u-boot.bin but you never use this file later one. Instead you're using u-boot-dtb.bin in line 29 and 33. Doing this, rendered a CRC error for me. Using u-boot.bin it is working as expected. So, i would assume you have a typo.

u-boot for A5X Max - RK3228?

Can I use one of the ready builds for my A5X Max? If so which? And how to flash it?

(Reddwarf)

Do you have plan for RK3566/3568

Dear Hexdump,
Your u-boot works very well on my S905x3 boxes. Do you have plan to release the version for RK3566/3568?

Thanks so much!

rockchip_rk33xx: problems: Help to write Armbian on my HD96Max

hey guys, i've been trying to install armbian onto my HD96 Max RK3318. I tried following; https://forum.armbian.com/topic/26978-csc-armbian-for-rk3318rk3328-tv-box-boards/ But I've run into a problem.

I don't have a working SD card to do that method, so i tried the (flash Emmc method) using the clock pin. in rkdevtool my device was recognized as a loader device, and I soon figured out how to force maskrom mode.

I just now needed to flash armbian onto the emmc using the download image tab, simple i thought... until i ran into errors (can't remember the exact errors but it won't finish downloading. I thought maybe i needed to clear out what was already on the Emmc so clicked the advanced tab and selected EraseLBA and EraseALL.

Now that seems to have cleared the original Firmware (android) and when I plug it into the tv, there's no clock on the system anymore and nothing shows up. Along with a solid red light and in rkdevtool it seems to be forced into maskrom mode without me having to do the clockpin method. which is good, doesn't seem like bricked the board or anything.

Attempted to flash armbian again using the download tab and I'm now having issues switching to storage.
I also checked if i can swap back to Loader mode in the advanced tab, got an error "don't support read or switch on storage"

Im new to this sort of thing so I'm learning as i go. I should also mention that I'm Using MiniLoaderAll.bin for the loader and trying to install Armbian_community_24.2.0-trunk.540_Clockworkpi-a06_bookworm_current_6.6.16 if that helps

h96 Max Plus rk3328 4gb/64gb Brick

I have a problem. Could you help me?
I have h96 Max plus tv box with RK3328 chip 4gb ram and 64gb memory.
I did wrong things and my device turned off, never to be turned on again, the red light is on and there is no display.
The computer does not see the device with the Android tool, batch tool, or factory tool.
As a result of some research, they said that it is necessary to put it in maskroom mode by short-circuiting 2 points on the motherboard with copper wire.
I succeeded, now the computer sees the device in maskroom mode.
When I want to install the software given by the manufacturer to the device, I get an error at the first stage.
I am getting bootloader download fail error.
This error comes up as soon as I start uploading. I cannot install any software on the device, it gives the same error on all of them.
How can i solve this problem. I would be very grateful if you could help me.
Thank you.

DRAM and CPU clocks for Allwinner H616 in OrangePiZero2

Hello!
First of all thanks for your great work. As you know I already managed to fit your kernel (5.11.0rc1-stb616) within my Armbian nightly for OrangePiZero2, and now USB works. :)

Now I'd like to address another issue: the board is quite slow; noticeably slower than with Armbian nightly kernel (5.11.11-sunxi64).
With the legacy OrangePi kernel, the CPU runs at 1512000000 Hz and the DRAM at 720000000 Hz; moreover, microSD does 45 MB/s.
I think with your kernel, clocks are lower by about 30% (and microSD can't past 22-23 MB/s).

jernej hinted about modifying clocks in u-boot, but honestly I don't know which files I should edit within the source tree: do you have a suggestion?
Thank you very much

readme.gxb: U-Boot requires a patch to compile

Hi @hexdump0815

You already know this but I'm posting this for others; postmarketOS had an issue where U-Boot <=2020.10 can't build successfully with the latest toolchain. Eventually I found that the following patch fixes it:

--- a/Makefile
+++ b/Makefile
@@ -970,6 +970,8 @@
 # Avoid 'Not enough room for program headers' error on binutils 2.28 onwards.
 LDFLAGS_u-boot += $(call ld-option, --no-dynamic-linker)
 
+LDFLAGS_u-boot += -z notext $(call ld-option, --apply-dynamic-relocs)
+
 ifeq ($(CONFIG_ARC)$(CONFIG_NIOS2)$(CONFIG_X86)$(CONFIG_XTENSA),)
 LDFLAGS_u-boot += -Ttext $(CONFIG_SYS_TEXT_BASE)
 endif

Maybe you could update your notes to work with newer U-Boot versions? Any of the U-Boot upstream defconfigs should work, or maybe add this patch to your notes?

Cheers.