Has your card been detected before by the flasher? Did you used the package that Hanson has posted? That package contains a modified flasher (for his chip to be detected) and the image that he currently uses. IMAG_RB.bin is only for a programmer, for the flasher you only need the small <image> file.

Have you used "go" with that package and shutdown afterwards? It seems weird that the same image works for a card and fails for another. Your chip is detected with this modified flasher, so it is only a matter of right image. Try it again with "go", shutdown for 1 minute, reboot and test.

Edited: The latest picture shows that you already flashed the latest image, which is SP1813 - 2.3.0.1007. Are you sure it isn't working? Maybe you forgot to shutdown?

Zitat von lordkag im Beitrag #121

---

Has your card been detected before by the flasher? Did you used the package that Hanson has posted? That package contains a modified flasher (for his chip to be detected) and the image that he currently uses. IMAG_RB.bin is only for a programmer, for the flasher you only need the small <image> file.

Have you used "go" with that package and shutdown afterwards? It seems weird that the same image works for a card and fails for another. Your chip is detected with this modified flasher, so it is only a matter of right image. Try it again with "go", shutdown for 1 minute, reboot and test.

---

My first question was if the card has been detected in the past with original flasher, not this one modified by me.

Using "go -e" will erase every sector that was written. No need for this. You should only use "go -r" before any flashing, to have a safe backup, then "go" to flash a new image. You should always shutdown after you flashed a new firmware.

Once again, any image.bin / IMAG_RB.bin is only meant for a programmer. It has 512KB and it is exactly the size of the chip. For the flasher you must use a small <image> file, to be expanded by the flasher. In your case there is no need to do anything, because the package already contains an <image> file and the bat will do the rest.

Your only task is to type "go" or "go -y" and shutdown once it says "Flashed successfully".

Zitat von lordkag im Beitrag #123

---

My first question was if the card has been detected in the past with original flasher, not this one modified by me.

Using "go -e" will erase every sector that was written. No need for this. You should only use "go -r" before any flashing, to have a safe backup, then "go" to flash a new image. You should always shutdown after you flashed a new firmware.

Once again, any image.bin / IMAG_RB.bin is only meant for a programmer. It has 512KB and it is exactly the size of the chip. For the flasher you must use a small <image> file, to be expanded by the flasher. In your case there is no need to do anything, because the package already contains an <image> file and the bat will do the rest.

Your only task is to type "go" or "go -y" and shutdown once it says "Flashed successfully".

---

Maybe the erase command has some side-effects. Do this:
- Remove IMAG_RB.bin from the package. Use "go -r" and upload the IMAG_RB.bin that you obtain.
- Test with the original flasher using "go -y"

Zitat von lordkag im Beitrag #125

---

Maybe the erase command has some side-effects. Do this:
- Remove IMAG_RB.bin from the package. Use "go -r" and upload the IMAG_RB.bin that you obtain.
- Test with the original flasher using "go -y"

---

My card is exactly the same than the one from biondo79, same Hardware ID.
Should I delete IMAG_RG.bin and just type "Go" ?

@biondo79

For the third time: You don't do anything with IMAG_RB.bin if you don't have a programmer! You should have uploaded that IMAG_RB.bin here for me, to have a look at what's been flashed or not. And when I say upload IMAG_RB.bin, I mean the IMAG_RB.bin you obtain with "go -r", not the one that was in the package. Delete that one until you own a programmer.

When I say "test with original flasher" I mean replacing the modified flasher with the original flasher, nothing more. If you get "no adapter found" it means that your SPI chip is not supported and it needs to be added to the flasher. Which leads us to my very first question: what is ID of the chip containing the image?

If you don't do what I say and you keep flashing and erasing wrong images, then what do you expect to happen? Your latest picture shows that you tried to flash the image from Station-Drivers, which was released for onboard controller with 9123 ID. Good luck reversing that: your only chance now is to use a programmer to flash IMAG_RB.bin from the package that Hanson provided. Again, only at this step you should have used IMAG_RB.bin. There is nothing more I can do, you have done it all by yourself.

@THZ

In the previous page you will find a few questions. If you don't follow them and reply to each one, then there is no need to go on. Otherwise you will just brick the controller on your own with erratic flashing and erasing. Hanson has already tested that image with success on his card by following my advices. I need to know the answers before I can provide steps for your card.

Zitat von lordkag im Beitrag #128

---

For the third time: You don't do anything with IMAG_RB.bin if you don't have a programmer! You should have uploaded that IMAG_RB.bin here for me, to have a look at what's been flashed or not. And when I say upload IMAG_RB.bin, I mean the IMAG_RB.bin you obtain with "go -r", not the one that was in the package. Delete that one until you own a programmer.

When I say "test with original flasher" I mean replacing the modified flasher with the original flasher, nothing more. If you get "no adapter found" it means that your SPI chip is not supported and it needs to be added to the flasher. Which leads us to my very first question: what is ID of the chip containing the image?

If you don't do what I say and you keep flashing and erasing wrong images, then what do you expect to happen?

---

I have edited my previous post with a reply. You flashed a wrong image with 9123 ID for onboard controller, because you refused to follow my advices in details. Nothing more that can be done, only a programmer is the solution.

thanks for the support

where can I buy a programmer? :)

@lordkag:
In order to move along, I need to know that you understand the risk and that you are OK to test as it is, even if your Marvell controller might cease to work. Once you have thought this well, you will need to provide the following informations:
- what is the type of controller: onboard (which mainboard), external (which card): External card U3S6
- what is the ID of the controller: 9120, 9123, 9128 ... : 9120
- what is the full ID of the chip containing the image, which is located next to the Marvell controller: ?
I typed GO, and here is what I got:

@biondo79

You have yet again avoided my questions and steps. I asked you to upload the IMAG_RB.bin you obtained, to see what was written. I also asked you to post the ID of the chip containing the image, which is a DIP8 chip. You jump from one action to another without following good advices.

@THZ

Look at this image. The DIP8 chip is top right with a smudge on it. Also use "go -r" and upload the dumped image. Will be back in a couple of hours.

Zitat von lordkag im Beitrag #133

---

@biondo79

You have yet again avoided my questions and steps. I asked you to upload the IMAG_RB.bin you obtained, to see what was written. I also asked you to post the ID of the chip containing the image, which is a DIP8 chip. You jump from one action to another without following good advices.

@THZ

Look at this image. The DIP8 chip is top right with a smudge on it.

---

Here is the picture from my card with the DIP8 chip:


I didn't get "IMAG_RB.bin" after I typed "go -r". There was no such file created on the USB stick.

By the way: "Current Image Version is 1.0.1.1606" - isn't that newer than 1.0.0.1813 ?