Problems Loading firmware by RS232 in a V7S HD

[xueps]

Using RS232Tool_V7V8SuperGoldenV_2.22.0.0 or the V1.3 can't acces loading firmware.
When click "Start" sometimes writes "RORORORORORORORORORORORORORORORORO...."
and sometimes is doing nothing, just "Please reset the STB!".
Is there anything else to do?.

Serial number starts with V7SA18090.....
thanks

[cpr43]

the flash.bin USB process does not work??

viewtopic.php?f=51&t=7535

[xueps]

the flash.bin USB process does not work??

Nop, when I connect the power is not starting.

[cpr43]

the flash.bin USB process does not work??

viewtopic.php?f=51&t=7535

Also, V 2.22??

viewtopic.php?f=51&t=321

[cpr43]

the flash.bin USB process does not work??

Nop, when I connect the power is not starting.

Did you try a low GB USB 1,2 4gb?

[xueps]

the flash.bin USB process does not work??

Nop, when I connect the power is not starting.

Did you try a low GB USB 1,2 4gb?

I tell you using rs232 cable, I didn't try with the usb cable (I dont have...)
Anyway I try again with a low capacity USBmemory.

[xueps]

Neither working with a fat32 1GB usb stick.
I dont know what more to do.

[cpr43]

Neither working with a fat32 1GB usb stick.
I dont know what more to do.

flash.bin or Flash.bin using old file? Not flash.bin.bin or Flash.bib.bin

[xueps]

Neither working with a fat32 1GB usb stick.
I dont know what more to do.

flash.bin or Flash.bin using old file? Not flash.bin.bin or Flash.bib.bin

Nothing,

[cpr43]

Neither working with a fat32 1GB usb stick.
I dont know what more to do.

flash.bin or Flash.bin using old file? Not flash.bin.bin or Flash.bib.bin

Nothing,

Try this

[xueps]

Try this

The result is this:

"jump=0x80100000, length=0x3d538, staddr=0x80100000, resv=0x80100000
MMM3


U-Boot 2012.04-hg1419-7d7cd9b245ad-dirty (Jan 26 2018 - 14:48:00)

*****************************************
** Board: mips CPU: sym - MIPS 24KEc
** SOC name : 0x800a
** PACKET type : SIP_68S_DDR2
*****************************************
DRAM:
DDR is 64MiBytes
20 MiB
== OTP_VERSION:[hg_NA] Build Time:[Jan 26 2018, 14:48:00]
Using default environment

SPI: ready
Error, invalid system clock.

cpu_secondary_init_r: image file for secondary core should already locate where it should be
current boot media:0...
phy_clk = 405, clk=50
R_SPIN_CH0_BAUD: 40000009
SF: spi flash status register: 0x20, 0x02 ta=0x8141fc28
SPI: Detected W25Q64 with erase size 64 KiB, total 8 MiB
e: 0xBF50001C = 0x0011ff03
0xBF510018 = 0xfffffff9
No ethernet found.
main_loop entered: bootdelay=0

Hit any key to stop autoboot: 0
####### Uboot Fixed Partitions #######
bootinit 0x0~0x10000
uboot 0x10000~0x50000
boot.scr 0x50000~0x60000
####################################
#Eeuig script at 80100000
Wrong image format for "source" command
U-boot# usb start;fatload usb 0 83000000 v7s.bin;sf burn 83000000 0 800000
(Re)start USB...
auto_detect_usb_port --- usb default sel port 1
port_sts0:0x00000803 port_sts1:0x0c000000 next scan port:0
auto_detect_usb_port --- usb sel port 0
USB: usb_debug
need usb0 plug in....
usb0 device connect port status :0x1803
port0 reset down port status :0x8001205
ehci_hcd_init...
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... SB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
reading v7s.bin
HI timed out on TD - token=0x80008d80
EHCI timed out on TD - token=0x80008d80
HItmed out on TD - token=0x80008d80
HItmed out on TD - token=0x80008d80
HItmed out on TD - token=0x80008d80
Error reading cluster

** Unable to read "v7s.bin" from usb 0:1 **
do_spi_flash_uboot_save offset[0] len[800000]
spi0 is already setup!!!
SF: spi flash status register: 0x20, 0x02 ta=0x8141fc28
SPI: Detected W25Q64 with erase size 64 KiB, total 8 MiB
sae uboot to flash
U-boot#



Do you think yhat I have to change the USB stick?

[cpr43]

You need to keep trying all different choices. Change USB, Format style, Bin file etc

[xueps]

GREAT!!!!!!
At last I tried the usb upgrade directly, clicking MENU button on the remote and it works. Not very well at the beginning but then I'd changed de USB stick, probably that was the problem with the ScoomTool.
Thanks for all!!!

[cpr43]

GREAT!!!!!!
At last I tried the usb upgrade directly, clicking MENU button on the remote and it works. Not very well at the beginning but then I'd changed de USB stick, probably that was the problem with the ScoomTool.
Thanks for all!!!

Really glad you could recovered your unit!!!