Amiko Alien 1 stuck on LOAD

[thetempuser]

Hello,

I have an Amiko Alien 1 running Spark and Enigma2. It worked great since I bought it, 3 years ago. But yesturday I stumbled into a problem.
I turn it on as usual and it remains stuck on LOAD. Boot - 3 seconds - LOAD - it stays this way, it won't go further.

I've uploaded Spark Rescue Image (via USB stick), it installs with SUCCESS on the STB, it reboots and remains on LOAD.
I've uploaded Enigma 2 (via USB stick), it installs with SUCCESS on the STB, it reboots and remains on LOAD.
I've tried changing booting from Spark to Enigma, Enigma to Spark, it still gets stuck on LOAD.
Whatever I do, it still gets stuck on LOAD.
Is there any way to revive it ? Any other method? Or all is lost.

I haven't tried the serial yet, RS 232, because i don't have a cable, but I want to try and send these commands via Hyperterminat:
set bootargs console=ttyAS0,115200 rw ramdisk_size=6144 init=/linuxrc root=/dev/ram0 nwhwconf=device:eth0,hwaddr:00:06:37:04:15:00
ip=192.168.40.83:192.168.40.19:192.168.40.1:255.25 5.0.0:lh:e th0ff
stmmaceth=msglvl:0,phyaddr:1,watchdog:5000 bigphysarea=6000
then
nboot.i 0x80000000 0 0x00100000 ;bootm 0x80000000

Do I have to change the wires in Rs232 or can I use it as bought. If anyone knows the diagram for RS232 wiring please share.

Any solutions ?

Thank you

 

[satco123]

yes rs232 is most safer to upgrade the box,opr flash the box,but 1st of all is ur box loader is available to use the rs232 cable,here in pakistan it available in very low price,if u have any sources trhn u can get it,i will also try to find out daigram of rs232 cable.if i get it i will share it here as sooon as

 

[thetempuser]

I bought a cable (Rs232) and the pin configuration for null modem is this:
2-3
3-2
5-5

I've used Putty to connect via Serial:
U-Boot 1.3.1 (Nov 15 2010 - 17:57:53) - stm23_0043 - YW 1.0.018 Rel

DRAM: 128 MiB
NOR: 8 MiB
NAND: 512 MiB
In: serial
Out: serial
Err: serial
IdentID : 09 00 0a 00 00 1f f8
Hit ESC to stop autoboot: 0
## Booting image at a0080000 ...
Image Name: Kernel-Ramdisk-Image
Image Type: SuperH Linux Multi-File Image (gzip compressed)
Data Size: 5867343 Bytes = 5.6 MiB
Load Address: 80800000
Entry Point: 80801000
Contents:
Image 0: 2970211 Bytes = 2.8 MiB
Image 1: 2897119 Bytes = 2.8 MiB
Verifying Checksum ... Bad Data CRC
## Ready for binary (ymodem) download to 0x80000000 at 115200 bps...
CCCCCCCCCCTimed out
xyzModem - Cksum mode, 0(SOH)/0(STX)/0(CAN) packets, 20 retries
## Total Size = 0x00000000 = 0 Bytes


As you can see there is a Verifying Checksum ... Bad Data CRC error so I did a Memory test:

MB618> mtest
Testing 80000000 ... 87d00000 (125 MiB):
Pattern 00000000 Writing... Reading...
Mem error @ 0x876DFA5C: found 87F0BC90, expected 01DB7E97

Mem error @ 0x876DFA60: found 876DFA60, expected 01DB7E98

Mem error @ 0x876DFA64: found 876DFA60, expected 01DB7E99

Mem error @ 0x876DFA68: found 876DFA60, expected 01DB7E9A

Mem error @ 0x876DFA6C: found 01DB7E9A, expected 01DB7E9B
Pattern FFFFFFFF Writing...

So there must be something wrong with the memory, but can I do anything to repair it, format it, maybe replace it it? Is there anything else to try ?

Thanks for your help.