mirror of
https://github.com/Rockbox/rockbox.git
synced 2026-10-10 08:03:04 -04:00
66bc0728d5
pmu_preinit() masked register 0x10 with 0xdb, which clears bits 2 and 5. With bit 2 clear the NAND chip does not answer and nand_init() fails. Masking with 0xdf clears only bit 5 and leaves bit 2 alone. Measured on a 4GB Nano 3G. Every build that had worked carried debug PMU reads, i.e. extra I2C delay, so delay was the confound to rule out and each mask was tried with and without it: 0xdb, no extra delay dead 0xdb, extra delay dead 0xdf, extra delay reads (3 runs) 0xdf, no extra delay reads One early 0xdf build without instrumentation failed once (rc=-1). That has not been explained; the final validation run is the same configuration and reads correctly. Reading the register back after pmu_preinit() gives 0xdf. The new mask keeps bit 2 and "| 0x8" only sets bit 3, so bit 2 is set as the BootROM left it - the old mask was clearing it. Bit 5 is hidden by the mask, so what the ROM leaves there is not known. What bit 2 does is not established. The old comment guessed "bit4 is related to NAND, LDO_0x15 on/off"; the register does sit among the NAND supply settings (0x15 reads back the value commented as Vnand), but no datasheet was consulted, so the new comment states only the observed effect. AI provenance: developed with Claude Opus 5 (Anthropic), used through Claude Code. The model wrote most of the code and this message under Andrew Rice's direction. Any hardware testing described above was carried out by Andrew Rice, who is responsible for this change. Change-Id: Iee73f876b7b6a5c85e09f8bf1c5ac174a49409e0 |
||
|---|---|---|
| android | ||
| apps | ||
| backdrops | ||
| bootloader | ||
| docs | ||
| firmware | ||
| fonts | ||
| icons | ||
| lib | ||
| manual | ||
| packaging | ||
| tools | ||
| uisimulator | ||
| utils | ||
| wps | ||
| .gitattributes | ||
| .gitignore | ||
| .gitreview | ||
__________ __ ___.
Open \______ \ ____ ____ | | _\_ |__ _______ ___
Source | _// _ \_/ ___\| |/ /| __ \ / _ \ \/ /
Jukebox | | ( <_> ) \___| < | \_\ ( <_> > < <
Firmware |____|_ /\____/ \___ >__|_ \|___ /\____/__/\_ \
\/ \/ \/ \/ \/
Build Your Own Rockbox
1. Clone 'rockbox' from git (or extract a downloaded archive).
$ git clone git://git.rockbox.org/rockbox
or
$ tar xJf rockbox.tar.xz
2. Create a build directory, preferably in the same directory as the firmware/
and apps/ directories. This is where all generated files will be written.
$ cd rockbox
$ mkdir build
$ cd build
3. Make sure you have mips/m68k/arm-elf-gcc and siblings in the PATH. Make sure
that you have 'perl' in your PATH too. Your gcc cross compiler needs to be
a particular version depending on what player you are compiling for. These
can be generated using the rockboxdev.sh script in the /tools/ folder of the
source.
$ which arm-elf-eabi-gcc
$ which perl
4. In your build directory, run the 'tools/configure' script and enter what
target you want to build for and if you want a debug version or not (and a
few more questions). It'll prompt you. The debug version is for making a
gdb version out of it. It is only useful if you run gdb towards your target
Archos.
$ ../tools/configure
5. *ploink*. Now you have got a Makefile generated for you.
6. Run 'make' and soon the necessary pieces from the firmware and the apps
directories have been compiled, linked and scrambled for you.
$ make
$ make zip
7. unzip the rockbox.zip on your music player, reboot it and
*smile*.
If you want to build for more than one target, just create several build
directories and create a setup for each target:
$ mkdir build-fuzeplus
$ cd build-fuzeplus
$ ../tools/configure
$ mkdir build-xduoox3
$ cd build-xduoox3
$ ../tools/configure
Questions anyone? Ask on the mailing list or on IRC. We'll be happy to help you!