SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware

[bahus]

> you can also redirect the firmware to a different directory on the sdcard with Redirect file

It doesn't seem to work for me on my Sansa Clip Zip. I'm trying to load firmware (latest daily build) from /rbclipzip/.rockbox folder on my SD card.
On loading it gives me splashes "No .rockbox directory" then "Installation is incomplete" and then loads in failsafe mode.
Boot 9de8993af6

Boot data:
Bootdata RAW:
Boot Volume: <1
CRC: 1b6947cc
CRC: OK!
00: 01 00 00 00 00

If .rockbox is placed in root of SD Card everything works smoothly

[Bilgus]

Unfortunately I broke the patch that was supposed to do that functionality so it only works from the root of the card till I get back to it
Edit -2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
https://www.rockbox.org/daily.shtml

root redirect is in the dev builds now you can redirect to any folder
@amachronic also made a plugin to switch which build you run [Apps/multiboot_select]

[odel]

I had problems getting my clip zip to boot from SD until I formatted it as Fat32.

Now it works great!

[bahus]

> you can also redirect the firmware to a different directory on the sdcard with Redirect file

Bilgus
Just noticed that this feature is fixed with https://github.com/Rockbox/rockbox/commit/c9857098ac0a3173d5d03baa3c32d9a8e29faec8
Cool!

My tests result:
1) It doesn't work with `/rbclipzip` in redirect file. But does work with shorter folder name `/rbcz`. Is it expected restriction on folder length?
2) With .rockbox placed in the root directory of SD card, I see content of SD card right inside Files menu (folders and files). But now additional entry is appeared mircorSD0 (for internal) and microSD1(for SD card). Not sure if this change is related to your changes but it was only single microSD0 (for internal) before. microSD1 entry is redundant here.

And with `/rbcz/.rockbox` I see only 2 entries microSD0 (for internal) and mircorSD1 (for actual SD) in Files menu. Would be cool to see content of SD card right inside Files menu (basically behave in the same way when it's placed in root of SD)

[Bilgus]

I'll have to look into the name length, shouldn't be an issue.. IIRC its MAX_PATH @ 260 chrs and testing it I see it boots the file just fine but it appears to lose the last 2 chars once booted so yeah def a bug

Yes SD<0> and SD<1> are related to this patch, I'll have to see about the best way to hide them, not sure that enumerating everything in the root is the best idea as it could get pretty confusing but i'll try it

thanks for the report

Edit:
Oh nevermind I see the issue the buffer is too small in the redirect

[Bilgus]

>Yes SD<0> and SD<1> are related to this patch, I'll have to see about the best way to hide them, not sure that enumerating everything in the root is the best idea as it could get pretty confusing but i'll try it

yeah as I suspected it has to be this way if you enumerate the root of the SD into the redirected folder and it has the same dir names its a crapshoot on which folder you actually get (last mounted overwrites the prior)

[Bilgus]

Fixed as of today Mar 06 2022

[skwal]

because of problems with the internal storage i use rockbox on sd as decribed.
works.

but i have on question.
after using rockbox on sd i et two sd cards shown on the player
sd0: empty
sd1: my files

on the pc i only get one sd card: sd1 with my files


when  activate auto bookmark rockbox writes the bookmark.
but when i activate as start mode latest bookmarks he say: no bookmark found
manuel i ca find the latest bookmark (sd1)

is the problem that rockbox searches the bookmarks on sd0 and not on sd1 ? how can i solve this?

[cj17]

Could somebody please tell me what I'm missing with this?

I've got a clip zip with firmware version V01.01.20A and I've followed the instructions as I understand them:

- I downloaded a dev build and put that on my SD card (which is a Sandisk 16gb - fat32).
- I created the empty file as instructed with the proper name.

But when I switch it on it just boots straight into the sansa firmware.  Have I missed something?

Would really appreciate any help with this...

Thanks in advance!

[7o9]

Did you miss installing the bootloader?

[cj17]

@7o9 Thanks  very much for your reply.

I didn't install a bootloader - I thought because that part was struck out in the instructions that it was no longer necessary and installing a Dev build somehow made it not necessary.  I saw it said the bootloaders were available on the "mainsite" but there was no link and I didn't see them on the mainsite.

So do I need to install the bootloader on my Clip Zip first?   And where are the bootloaders?

Thank you!

[eugenkss]

When you install via the Rockbox Utility, you can select to install also the bootloader.

For manual installation, there are instructions in the Rockbox Manual on how to install a bootloader

[cj17]

Hi,

Thanks for your help and please excuse if this is a silly question but does the bootloader get installed on the device or the SD card?

Also, I just copied the latest daily build onto the SD card as I thought that had the bootloader - so that's not right?

Previously I did use the utility to install and did select the bootloader to install but that didn't work either so I must be missing something.

Can somebody please clarify a couple of things for me:

1/  Is it necessary to use a dev build or does this work with the latest stable version?

2/  Is the Multiboot bootloader different from the regular bootloader? 

It says above that "Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite" but there's no link and I've looked but not found them - where are they?

I'm keen to get this working but can't see what I'm doing wrong.

Thanks for all the help with figuring this out!  Much appreciated!

[7o9]

The bootloader is installed to the device’s flash memory and must be installed so the device actually knows to look for Rockbox.

The multiboot functionality is part of the regular bootloader now. Only when it was new and experimental there was a separate version for the adventurous.

Dev builds of Rockbox are much newer than the latest release. They are stable and fully suited for daily use.

Rockbox utility is the easiest way. What went wrong when you tried to use it?

[cj17]

Thanks v. much for clarifying.

When I tried it it just booted straight into the Sansa software.

Should it work with the stable release version too?