21 replies to this topic

[EnoSat]

Hi,

any chance recovery HD51 ?

Actual status:

not display, only on RS232 write

CPU 01
BCM74390012
PRID07251112
v1.7
RR:00000003
BFW
SEC
seclib-1.5
BBL v1.0.1
AVS init...
spare0/rmon_hz=017e7878
spare1/rmon_vt=017e7878
AVS init OK
AVS load:select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: 2a002b00
AVS load_code offset =00051000
AVS: OTP Decrypt 0x00000000, OTP Verify AVS 0x00000000
LOADED

single board
select_image: addr_offset: 00055000 part_offset: 00000000 bootStatus: 3d2b2500
MemsysFW: OTP Decrypt 0x00000000, OTP Secure Boot 0x00000000
SHMOO 01020000 BLD:9695 HW:hpf0_b1p6 V:1.2.0.0
MCB: FIX
AVS start:status=000000ff
STB: Current voltage=000003cd(973)
 temperature=0000b2c4(45764)
 PV=0000037a(890)
 MV=000003ce(974)
AVS FW rev=30333078 [0.3.0.x]
OK
DDR0: *@ ffe0ba98 <= ffe0ba98 MEMSYS-0 @ f1100000 OK
DDR1: -
Sdram Scramble OTP = 0x00000001
Sdram Scramble OK
select_image: addr_offset: 00020000 part_offset: 00000000 bootStatus: 1b25252b
BFW load mode OTP = 0x0000000f
bfw_hash_locked = 0x00000000
BFW key3 OK, CPU 01
BCM74390012
PRID07251112
v1.7
RR:00000403
BSP Debug Info:
0x4204010f
0x00000122
0x00000000
0x0000002a
0x00000030
0x00000000
0x00000100
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
0x00000000
BFW
SEC
seclib-1.5
BBL v1.0.1
AVS init...
spare0/rmon_hz=017e7878
spare1/rmon_vt=017e7878
AVS init OK
AVS load:*** BCHP_BSP_GLB_CONTROL_GLB_DWNLD_ERR is set.
select_image: addr_offset: 00051000 part_offset: 00000000 bootStatus: aa252b2b
AVS load_code offset =00051000
AVS: OTP Decrypt 0x00000000, OTP Verify AVS 0x00000000
LOADED

single board
*** BCHP_BSP_GLB_CONTROL_GLB_DWNLD_ERR is set.
select_image: addr_offset: 00055000 part_offset: 00000000 bootStatus: bd2b252b
MemsysFW: OTP Decrypt 0x00000000, OTP Secure Boot 0x00000000
SHMOO 01020000 BLD:9695 HW:hpf0_b1p6 V:1.2.0.0
MCB: FIX
AVS start:status=000000ff
STB: Current voltage=000003d2(978)
 temperature=0000b2c4(45764)
 PV=0000037d(893)
 MV=000003d2(978)
AVS FW rev=30333078 [0.3.0.x]
OK
DDR0: *@ ffe0ba98 <= ffe0ba98 MEMSYS-0 @ f1100000 OK
DDR1: -
Sdram Scramble OTP = 0x00000001
Sdram Scramble OK
*** BCHP_BSP_GLB_CONTROL_GLB_DWNLD_ERR is set.
BFW:0000002f
FATAL ERROR: Boot 2nd image failed

Edited by Frenske, 25 December 2019 - 22:34.
I moved your request to the English section where it belongs.

[WanWizard]

That looks like the bootloader can't find a rootfs to boot from?

[EnoSat]

any idea for next step ?

or some known dump for external reprograming ?

[WanWizard]

I assume you've already tried to flash it again? The bootloader seems to work fine?

[EnoSat]

bootloader not work fine
USB ignored
with power button

without power button

[betacentauri]

Try to use other USB stick and slot. Is it fat32 formatted? Is anything shown regarding USB stick in the log?

[WanWizard]

Then I hope someone with more technical experience can tell you how to proceed....

[Binsche]

BBL v1.0.1

@Eno, have you ever done the bootloader update, to version v1.0.7r27 (hd51-bolt-v107r27) ?

thats, what i would try first...

[mrvica]

man kann den Bootloader beim Starten mit Ctrl-C unterbrechen, dann vom BOLT Prompt probieren eine Partition zu starten

boot emmcflash0.linuxkernel 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rootsubdir=linuxrootfs1 kernel=/dev/mmcblk0p2 rw rootwait hd51_4.boxmode=1'

boot emmcflash0.linuxkernel2 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p8 rootsubdir=linuxrootfs2 kernel=/dev/mmcblk0p4 rw rootwait hd51_4.boxmode=1'

boot emmcflash0.linuxkernel3 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p8 rootsubdir=linuxrootfs3 kernel=/dev/mmcblk0p5 rw rootwait hd51_4.boxmode=1'

boot emmcflash0.linuxkernel4 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p8 rootsubdir=linuxrootfs4 kernel=/dev/mmcblk0p6 rw rootwait hd51_4.boxmode=1'

[twol]

man kann den Bootloader beim Starten mit Ctrl-C unterbrechen, dann vom BOLT Prompt probieren eine Partition zu starten

boot emmcflash0.linuxkernel 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p3 rootsubdir=linuxrootfs1 kernel=/dev/mmcblk0p2 rw rootwait hd51_4.boxmode=1'

boot emmcflash0.linuxkernel2 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p8 rootsubdir=linuxrootfs2 kernel=/dev/mmcblk0p4 rw rootwait hd51_4.boxmode=1'

boot emmcflash0.linuxkernel3 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p8 rootsubdir=linuxrootfs3 kernel=/dev/mmcblk0p5 rw rootwait hd51_4.boxmode=1'

boot emmcflash0.linuxkernel4 'brcm_cma=440M@328M brcm_cma=192M@768M root=/dev/mmcblk0p8 rootsubdir=linuxrootfs4 kernel=/dev/mmcblk0p6 rw rootwait hd51_4.boxmode=1'

Never seen that - good information

[EnoSat]

man kann den Bootloader beim Starten mit Ctrl-C unterbrechen, dann vom BOLT Prompt probieren eine Partition zu starten

BOLT not show on display
CTRL-C not accept

[mrvica]

seems boot loader is bad, if the flash is bad, we could still boot from a USB stick, we first need to find out how to do it, possible would be

[mrvica]

let us try to boot HD51 or H7S from a USB stick, just in case someone needs it, my 8 years old box I could start ans Image from a USB pen, on the pen were two partions, one FAT 256 MB and 1GB ext Partition, on the FAT partion were, Start.bat and kernel.bin, Start bat containing the kernel command line, on the ext partition was rootfs, the loader was cfe, slightly different as on BOLT loader we have now, the command line

boot -elf usbdisk0:/mini/kernel.bin 'root=/dev/sda2 rootfstype=ext4 rw bmem=256M@512M bmem=16M'

looks similar as command lines for the HD51, we just need the combination of these two lines for a USB stick, the USB stick is like on the cfe usbdisk0, I had the BOLT in hex editor and extracted the ASCII text regarding flashing from a USB stick with disk.img, could be usefull

usbdisk0
-forceerase
emmcflash0.kernel
boot emmcflash0.kernel 'root=/dev/mmcblk0p2 rw rootwait'
emmcflash0.kernel1
boot emmcflash0.kernel1 'root=/dev/mmcblk0p3 rw rootwait'
emmcflash0.boot
usb init
waitusb
hd51/imageversion
xflash %s usbdisk0:%s %s
flashing
hd51/disk.img
xflash -forceerase usbdisk0:hd51/disk.img emmcflash0
flash usbdisk0:hd51/splash.bin flash0.splash
hd51/hd51-bolt.bin
flash usbdisk0:hd51/hd51-bolt.bin flash0.bolt
completed!
no partitions
hd51/splash.bin
hd51/kernel.bin
hd51/kernel1.bin
hd51/kernel2.bin
emmcflash0.kernel2
hd51/kernel3.bin
emmcflash0.kernel3
hd51/kernel4.bin
emmcflash0.kernel4
hd51/kernel5.bin
emmcflash0.kernel5
hd51/rootfs.bin
emmcflash0.rootfs
hd51/rootfs1.bin
emmcflash0.rootfs1
hd51/rootfs2.bin
emmcflash0.rootfs2
hd51/rootfs3.bin
emmcflash0.rootfs3
hd51/rootfs4.bin
emmcflash0.rootfs4
hd51/rootfs5.bin
emmcflash0.rootfs5

 

someone with RS232 Interface could try to boot form USB out of the BOLT prompt and find the right kernel command line, that would be the first step, the second would be to put the stick in the box and just start the image from it

[EnoSat]

big problem interupt boot process (the whole process takes only 3 sec.), CTRL-C not accept and after write FATAL ERROR: Boot 2nd image failed too no accept any key from keyboard

Edited by EnoSat, 27 December 2019 - 16:23.

[betacentauri]

Press ctrl+c immediately after power on several times.
I don’t know whether it works with bolt bootloaders. I think I never tried it. With old cfe bootloaders it worked.
Maybe WTE can help you and have an idea how to fix your box.

[twol]

let us try to boot HD51 or H7S from a USB stick, just in case someone needs it, my 8 years old box I could start ans Image from a USB pen, on the pen were two partions, one FAT 256 MB and 1GB ext Partition, on the FAT partion were, Start.bat and kernel.bin, Start bat containing the kernel command line, on the ext partition was rootfs, the loader was cfe, slightly different as on BOLT loader we have now, the command line

boot -elf usbdisk0:/mini/kernel.bin 'root=/dev/sda2 rootfstype=ext4 rw bmem=256M@512M bmem=16M'

looks similar as command lines for the HD51, we just need the combination of these two lines for a USB stick, the USB stick is like on the cfe usbdisk0, I had the BOLT in hex editor and extracted the ASCII text regarding flashing from a USB stick with disk.img, could be usefull

usbdisk0
-forceerase
emmcflash0.kernel
boot emmcflash0.kernel 'root=/dev/mmcblk0p2 rw rootwait'
emmcflash0.kernel1
boot emmcflash0.kernel1 'root=/dev/mmcblk0p3 rw rootwait'
emmcflash0.boot
usb init
waitusb
hd51/imageversion
xflash %s usbdisk0:%s %s
flashing
hd51/disk.img
xflash -forceerase usbdisk0:hd51/disk.img emmcflash0
flash usbdisk0:hd51/splash.bin flash0.splash
hd51/hd51-bolt.bin
flash usbdisk0:hd51/hd51-bolt.bin flash0.bolt
completed!
no partitions
hd51/splash.bin
hd51/kernel.bin
hd51/kernel1.bin
hd51/kernel2.bin
emmcflash0.kernel2
hd51/kernel3.bin
emmcflash0.kernel3
hd51/kernel4.bin
emmcflash0.kernel4
hd51/kernel5.bin
emmcflash0.kernel5
hd51/rootfs.bin
emmcflash0.rootfs
hd51/rootfs1.bin
emmcflash0.rootfs1
hd51/rootfs2.bin
emmcflash0.rootfs2
hd51/rootfs3.bin
emmcflash0.rootfs3
hd51/rootfs4.bin
emmcflash0.rootfs4
hd51/rootfs5.bin
emmcflash0.rootfs5

 

someone with RS232 Interface could try to boot form USB out of the BOLT prompt and find the right kernel command line, that would be the first step, the second would be to put the stick in the box and just start the image from it

So to set up the the 2nd usb partition you would  have to format ext4 and then diskcopy a root from an existing eMMC parttition (to create the root disk) or is it the root file from the image zip??

[mrvica]

that is a minor problem, I used rsync for the old box

rsync -axv / /media/usb

/media/usb may vary, depends on image and how the USB stick is mounted (media/sda...)

[WTE]

Press ctrl+c immediately after power on several times.
I don’t know whether it works with bolt bootloaders. I think I never tried it. With old cfe bootloaders it worked.
Maybe WTE can help you and have an idea how to fix your box.

 

It should first been known what really happen. I can say this person tried to load an own bootloader or a loader from a non HD51 model.

This cannot easily been proven without readout of the BOLT bootloader but when this is done then the only solution is to rewrite the BOLT loader by BBS. On the board there are bbs pins which need to been connect.

I cannot imaging it will fail on secondstage loader without temper it. Never say it's not possible but other reason is that spi nor flash is damaged which I actually never seen. Hope the issue can been fixed and never happen again:

 

You should have this parts to write BOLT back into the box.

 

BBS tool (google on cy7c68013a)

Broadband Studio for 7439

BOLT bootloader HD51

Probably only Windows XP or windows 7 for broadcom driver

Edited by WTE, 28 December 2019 - 12:44.

[ims]

 

Hi,

any chance recovery HD51 ?

Actual status:

not display, only on RS232 write

 

 

Has it classic rs232 pin out on board or must be used ttl converter ? I need investigate my vs1500 (same hw)

Edited by ims, 17 February 2020 - 19:11.

[mrvica]

must be TTL to RS232 converter, I made it for my Zgemma H7, it is rebranded HD51, I took it from a defect VUplus, just added 4pin connector, works

 

Attached Files

•  RS232_H7.jpg   96.79KB   13 downloads