Rockbox Development > Starting Development and Compiling

Error Cross Compiler

(1/1)

djphatic:
Hi

I recently got a fuze v2 which I updating to firmware v02.03.33 as soon as I got it. I have tried installing Rockbox but the firmware update will not initialize. The only firmware file to trigger a firmware update is the official v02.03.33, all other official and patched versions will not trigger a firmware update.

So, I thought I would give compiling the svn myself and see if that did me any furthers. I have read through the guides but I keep getting errors when I try to install a cross-compiler using rockboxdev.sh

I have attached a screenshot of the error message. Does anyone have any suggestions how to get past this stage? I have also tried the VMPlayer route I also get errors (I think they are the same errors).

Thanks

marc2003:
you don't run rockboxdev.sh when using cygwin. when you run setup -X to download the bits from the rockbox server, it sets it up for you. after that successfully completes, you just checkout SVN and then run ../tools/configure from your build directory.

Chronon:
You don't run it inside of the VMWare image either, since everything should already be installed and configured there.

djphatic:
Thanks for the replies, I tried ../tools/configure and managed to get the files. Maybe I originally missed something in the cygwin setup.

Unfortunately with a new bootloader, mksamboot and OF 02.02.26, 02.03.31 and 02.03.33 I still cannot get Rockbox installed.

I have contacted Sandisk support, seems odd that my player will only detect 02.03.xx original firmwares.

Jennifur:

--- Quote from: djphatic on May 26, 2010, 08:07:43 PM ---Thanks for the replies, I tried ../tools/configure and managed to get the files. Maybe I originally missed something in the cygwin setup.

Unfortunately with a new bootloader, mksamboot and OF 02.02.26, 02.03.31 and 02.03.33 I still cannot get Rockbox installed.

I have contacted Sandisk support, seems odd that my player will only detect 02.03.xx original firmwares.

--- End quote ---

This actually seems like a problem with the new batches of the V2 Fuze players. If you take a look at the development thread for the Sansa c200v2, m200v4, clipv1, clipv2, clip+, and fuzev2. It seems like Sandisk changed something.

Navigation

[0] Message Index