Installation / Removal > Other - Installation/Removal

Issues installing Rockbox on HIFI Walker H2 v1.3

<< < (3/4) > >>

dconrad:
Hmm, ok, let's try another - https://drive.google.com/file/d/13E60WlTTVf5s43Dt69YyeeA2GL_dBzVa/view?usp=sharing

This time I just copy/pasted parts from the identify function into the flash_info function, so let's see if our flash_info file is any different. No need to run the flash_onfi_info.

The mystery continues.

Arrefur:
The flash_info file seems to be the same.

--- Code: ---readID opcode  = FF E5 71 E5
readID address = E5 71 E5 71
readID dummy   = E5 71 E5 71
sfc params0  = 06 05 04 03
sfc params1  = 02 55 AA 55
sfc params2  = 00 6E 02 02
sfc params3  = A4 2F 00 00

--- End code ---
The mystery that keeps on giving.

dconrad:
Hold up, I commented out the part where it tries to read the readID via the opcode address. I think you might not be trying the new file when you download it. Can you double check your command you're running (each file has a different filename)?

Arrefur:
I've been replacing the bootloader files each time, they all have different names (eg. sanity_check_bootloader.erosq; long_reset_delay_bootloader.erosq; second_read_bootloader.erosq; tsh0_bootloader.erosq; read_info_with_identify_bootloader.erosq). Did I misunderstand on how to run them?

dconrad:
What jztool command are you running? It will need to change to match the new filename each time. Are you putting these test files on the SD card, or in the same place as where jztool is?

The wiki might not be clear on this - when you run something like "jztool erosq load bootloader.erosq", it's looking for the file "bootloader.erosq" in the same folder as jztool and sending that over USB. So you'll need the new files in the same folder and change that filename to send the desired one.

EDIT:

Wait. Are you using the jztooljs webpage? If so, that would explain it. It is loading a very old bootloader over USB, about 2 months before the definition for your NAND chip was added.

It's hard to explain how the system works unfortunately - this is why we're trying to get away from jztool. The jztool program only sends a file over USB from the computer to the player to run temporarily. Then the temporarily running bootloader reads a file from the SD card and writes it to flash. It's very confusing if you're not used to it.

If all this is true, please try the official release bootloader by putting jztool and the official bootloader bootloader.erosq file in the same folder and running the correct command. Then do the flash info and flash ONFI info and see if it works.

If that works, I would like to understand why the update file doesn't work, because I have a suspicion we may also have a miscommunication on that too, it may work fine.

Navigation

[0] Message Index

[#] Next page

[*] Previous page