12 replies to this topic

[alkap]

Hello everyone  

 

Please, if someone could help me, because I don't understand this error 

 

" check boot area failed "

 

 

it connects to HITOOL, it accepts the recovery, but when I restart it, the fastboot disappears in the eMMC

 

so I give it the FastBoot alone with the "Durn Fastboot" option and it starts , and I can access the Fastboot menu via telnet. 

 

Thanks very much

Edited by alkap, 24 February 2022 - 18:49.

[alkap]

the printenv command displays:  

 

 

baudrate=115200

ipaddr=192.168.1.10

serverip=192.168.1.1

netmask=255.255.255.0

bootfile="uImage"

phy_intf=mii,rgmii

use_mdio=0,1

phy_addr=2,1

gmac_debug=0

bootcmd_android=mmc read 0 0x3F000000 0x30000 0x4000; bootm 0x3F000000; mmc read 0 0x1FFFFC0 0x26000 0xA000; bootm 0x1FFFFC0; run bootcmd_fallback

bootargs_1G=mem=937M mmz=ddr,0,0,60M vmalloc=500M

bootargs_2G=mem=1961M mmz=ddr,0,0,60M vmalloc=500M

led_gpio=5_0

led_gpio_level=0

set_gpio=5_2

set_gpio_level=1

modelname=multibox

loadaddress=0x1000000

compareaddress=0x4000000

set_zero=mw.b $(loadaddress) 0x00 1; mw.b $(compareaddress) 0x00 1;

check_nonzero=ncmp.b $(loadaddress) $(compareaddress) 1

check_zero=cmp.b $(loadaddress) $(compareaddress) 1

truncate_once=fatwrite mmc 0:A0001000 $(loadaddress) STARTUP_ONCE 0

loadbootargs_default=fatload mmc 0:A0001000 $(loadaddress) STARTUP

loadbootargs_once=fatload mmc 0:A0001000 $(loadaddress) STARTUP_ONCE

loadbootargs_once_or_default=run set_zero loadbootargs_once check_nonzero truncate_once; run check_zero loadbootargs_default

parsebootargs=parseenv $(loadaddress)

preboot=setenv bootcmd_fallback $(bootcmd); run loadbootargs_once_or_default; run check_nonzero parsebootargs

stdin=serial

stdout=serial

stderr=serial

bootargs_common=console=ttyAMA0,115200 blkdevparts=mmcblk0:1M(fastboot),1M(bootargs),18M(recovery),2M(bootoptions),2M(deviceinfo),4M(baseparam),4M(pqparam),4M(logo),40M(fastplay),20M(kernel),20M(trustedcore),4M(misc),1024M(system),150M(vendor),306M(e2tv),256M(cache),50M(private),8M(securestore),16M(linuxkernel1),16M(linuxkernel2),16M(linuxkernel3),16M(linuxkernel4),-(userdata) hbcomp=/dev/block/mmcblk0p13

ethaddr=00:***************

serialnumber=49***********

ethact=up

bootargs_512M=mem=512M mmz=ddr,0,0,256M

ver=Fastboot 3.3.0 (multibox@builder) (Mar 19 2020 - 17:03:52)

[Dimitrij]

Reinstall recovery emmc

[alkap]

I have reinstalled recovery more than 50 times.
always the same problem

[Frenske]

If I have the time I will try to test it too.

[alkap]

If I have the time I will try to test it too.

thank you so much 

[Frenske]

I just found the time to flash the Multibox with a new 8.1 release and the last Nightly Build. I also flashed the latest recovery image via the recovery menu. As far as I've noticed the recovery image hasn't been changed since a long time. If this isn't needed why should it be changed.

As you can see on the picture, all images are still present and working. Can you starup with the recovery image? Obviously not. Maybee some wierd thing with your USB stick?

Attached Files

•  multibox multiboot.PNG   481.87KB   2 downloads

[alkap]

I just found the time to flash the Multibox with a new 8.1 release and the last Nightly Build. I also flashed the latest recovery image via the recovery menu. As far as I've noticed the recovery image hasn't been changed since a long time. If this isn't needed why should it be changed.

As you can see on the picture, all images are still present and working. Can you starup with the recovery image? Obviously not. Maybee some wierd thing with your USB stick?

I think I need to inject the NVRAM files to it 

 

always the same problem , " check boot area failed "

[40H3X]

Did you try this

 

1) Download https://downloads.op...covery_emmc.zip

 

2) Unzip the file to your desktop. You will have the following files:

'multibox' directory
update_bootargs_multibox.bin

3) Format a USB stick MAX 8GB FAT32.

4) Copy all the files and 'multibox' folder to root of USB stick.

5) Power off the Maxytec multibox.

6) Connect USB stick to left side USB 2.0 port.

7) Carefully insert a paper clip into left side RESET hole and gently hold down the reset button.

8) Insert power cable whilst holding down reset button. Keep holding down the RESET button until front RED LED start flashing on and off.

9) Be patient, once successful the Maxytec Multibox will reboot into the recovery menu.

 

[Pr2]

Just a hint from the PULSe 4K recovery menu only the back USB is recognized to flash image from it. The front USB is not used. So may be try to insert your USB stick in another USB slot if there are several on this box.

[alkap]

maybe you did not understand, the recovery goes very well,

but when i restart multibox, recovery or fastboot erases itself from emmc memory.

and it gives this error  " check boot area failed "    

maybe it's an SDRAM problem 

[Frenske]

In that case I’m afraid your box suffers a hardware issue. 

[alkap]

In that case I’m afraid your box suffers a hardware issue. 

that's what i'm afraid too .  .