path: root/bootloader
AgeCommit message (Collapse)AuthorFilesLines
2014-08-29Hopefully fix most of the errors and warnings from the last pushMichael Sevakis1-0/+1
Change-Id: I1a466b2d55f120796910039a0296ca324c58e891
2014-08-30Rewrite filesystem code (WIP)Michael Sevakis20-51/+70
This patch redoes the filesystem code from the FAT driver up to the clipboard code in onplay.c. Not every aspect of this is finished therefore it is still "WIP". I don't wish to do too much at once (haha!). What is left to do is get dircache back in the sim and find an implementation for the dircache indicies in the tagcache and playlist code or do something else that has the same benefit. Leaving these out for now does not make anything unusable. All the basics are done. Phone app code should probably get vetted (and app path handling just plain rewritten as environment expansions); the SDL app and Android run well. Main things addressed: 1) Thread safety: There is none right now in the trunk code. Most of what currently works is luck when multiple threads are involved or multiple descriptors to the same file are open. 2) POSIX compliance: Many of the functions behave nothing like their counterparts on a host system. This leads to inconsistent code or very different behavior from native to hosted. One huge offender was rename(). Going point by point would fill a book. 3) Actual running RAM usage: Many targets will use less RAM and less stack space (some more RAM because I upped the number of cache buffers for large memory). There's very little memory lying fallow in rarely-used areas (see 'Key core changes' below). Also, all targets may open the same number of directory streams whereas before those with less than 8MB RAM were limited to 8, not 12 implying those targets will save slightly less. 4) Performance: The test_disk plugin shows markedly improved performance, particularly in the area of (uncached) directory scanning, due partly to more optimal directory reading and to a better sector cache algorithm. Uncached times tend to be better while there is a bit of a slowdown in dircache due to it being a bit heavier of an implementation. It's not noticeable by a human as far as I can say. Key core changes: 1) Files and directories share core code and data structures. 2) The filesystem code knows which descriptors refer to same file. This ensures that changes from one stream are appropriately reflected in every open descriptor for that file (fileobj_mgr.c). 3) File and directory cache buffers are borrowed from the main sector cache. This means that when they are not in use by a file, they are not wasted, but used for the cache. Most of the time, only a few of them are needed. It also means that adding more file and directory handles is less expensive. All one must do in ensure a large enough cache to borrow from. 4) Relative path components are supported and the namespace is unified. It does not support full relative paths to an implied current directory; what is does support is use of "." and "..". Adding the former would not be very difficult. The namespace is unified in the sense that volumes may be specified several times along with relative parts, e.g.: "/<0>/foo/../../<1>/bar" :<=> "/<1>/bar". 5) Stack usage is down due to sharing of data, static allocation and less duplication of strings on the stack. This requires more serialization than I would like but since the number of threads is limited to a low number, the tradoff in favor of the stack seems reasonable. 6) Separates and heirarchicalizes (sic) the SIM and APP filesystem code. SIM path and volume handling is just like the target. Some aspects of the APP file code get more straightforward (e.g. no path hashing is needed). Dircache: Deserves its own section. Dircache is new but pays homage to the old. The old one was not compatible and so it, since it got redone, does all the stuff it always should have done such as: 1) It may be update and used at any time during the build process. No longer has one to wait for it to finish building to do basic file management (create, remove, rename, etc.). 2) It does not need to be either fully scanned or completely disabled; it can be incomplete (i.e. overfilled, missing paths), still be of benefit and be correct. 3) Handles mounting and dismounting of individual volumes which means a full rebuild is not needed just because you pop a new SD card in the slot. Now, because it reuses its freed entry data, may rebuild only that volume. 4) Much more fundamental to the file code. When it is built, it is the keeper of the master file list whether enabled or not ("disabled" is just a state of the cache). Its must always to ready to be started and bind all streams opened prior to being enabled. 5) Maintains any short filenames in OEM format which means that it does not need to be rebuilt when changing the default codepage. Miscellaneous Compatibility: 1) Update any other code that would otherwise not work such as the hotswap mounting code in various card drivers. 2) File management: Clipboard needed updating because of the behavioral changes. Still needs a little more work on some finer points. 3) Remove now-obsolete functionality such as the mutex's "no preempt" flag (which was only for the prior FAT driver). 4) struct dirinfo uses time_t rather than raw FAT directory entry time fields. I plan to follow up on genericizing everything there (i.e. no FAT attributes). 5) unicode.c needed some redoing so that the file code does not try try to load codepages during a scan, which is actually a problem with the current code. The default codepage, if any is required, is now kept in RAM separarately (bufalloced) from codepages specified to iso_decode() (which must not be bufalloced because the conversion may be done by playback threads). Brings with it some additional reusable core code: 1) Revised file functions: Reusable code that does things such as safe path concatenation and parsing without buffer limitations or data duplication. Variants that copy or alter the input path may be based off these. To do: 1) Put dircache functionality back in the sim. Treating it internally as a different kind of file system seems the best approach at this time. 2) Restore use of dircache indexes in the playlist and database or something effectively the same. Since the cache doesn't have to be complete in order to be used, not getting a hit on the cache doesn't unambiguously say if the path exists or not. Change-Id: Ia30f3082a136253e3a0eae0784e3091d138915c8 Reviewed-on: Reviewed-by: Michael Sevakis <> Tested: Michael Sevakis <>
2014-08-28Fix up the bootloadersMichael Sevakis19-26/+31
They can't access the raw RBVERSION define any longer. Change-Id: I698062b36306399945c01de54cdccaa1a1a8434e
2014-08-08Bootloaders need the reacharound to get at the internal goodsMichael Sevakis24-36/+24
They need to include kernel-internal.h in order to perform inits. Change-Id: I5b0f155e4ff49a065c6cb97691ecd4396a199979
2014-07-07crc-mi4: use const lookup table for crcMarcin Bukat3-7/+0
This doesn't touch external tools as I see no need for. Change-Id: Ia69248c4b6a033c3772916525257e3540bddcffa Reviewed-on: Tested: Sebastian Leonhardt <> Reviewed-by: Marcin Bukat <>
2014-05-24Separate keymaps for YH-820 and YH-920/925Sebastian Leonhardt1-1/+2
Although both players basically have the same keys, the differences in the layout is rather big, so I think both deserve their own keymaps. (On the yh820 the FFWD/PLAY/REW buttons are located above the direction keys, on the yh920 at the side of the player. Furthermore the yh920/925 has a REC switch, whereas yh820 has a push button.) Change-Id: I0e62a1b101c387646c0bdb07ea142d9d2430ca15 Reviewed-on: Reviewed-by: Szymon Dziok <>
2014-03-27Sansa View: replace real bootloader with a simple test code.Szymon Dziok2-0/+67
After placing the firmware.mi4 file in the root dir of the player in UMS mode of the OF, Sansa should do stupid blinking with the backlight and buttonlight alternately. Recovering from this state is possible through the recovery mode (see Wiki), by putting an original copy of the firmware.mi4. Change-Id: Ia913442b97e8c405f55c4676b9a2bf0b1b1d05d6
2014-02-10zen/bootloader: power down the LCD at the end of the bootloader if neededAmaury Pouly1-0/+7
On the ZEN, the LCD is fed continuously by the DMA and this refresh needs to be stop when the bootloader gives control to the firmware, otherwise the DMA will source data from invalid region and it might even lock-up if the new code touches the memory setup. Work around this by properly stopping the LCD driver: the bootloader assumes that if the target defines HAVE_LCD_ENABLE in bootloader build (which is unusual) then it needs to stop the LCD. Since stopping the LCD could produce funny screens, power down backlight which is expected to power down the LCD too, giving a nice black screen instead of some random pixels. Change-Id: I7ce5ba9bfd08e596907c4ff8f80feb189f0576ce
2014-02-10imx233: stop the watchdog before loading main firmwareAmaury Pouly1-0/+2
Change-Id: I0a13444d6788a09b0fc04ed1a5115cb2e5fe6f57
2014-01-05Add missing kernel.h includes (hopefully all of them).Thomas Martitz1-1/+2
Change-Id: I9c1825296a788587b8d494d8514b3314847b0ff0
2013-12-16Introduce IHIFI760/960 targets.Andrew Ryabinin1-1/+2
Change-Id: Ie36e48742c0ed9aa3fd6f49aa034a11d2492327c
2013-11-23rk27xx: fix typo in comment about SCU_ID valuesMarcin Bukat1-1/+1
Change-Id: Iae4df54488d02246a4626c0f90b80b56aee891fa
2013-11-19Fix sim redAmaury Pouly1-1/+1
Change-Id: Icbdf47c5c508516892b1ce75558b878dc512e780
2013-11-19Fix redAmaury Pouly1-6/+1
Change-Id: Iaf77dd0ac6af921f67f883064f490a9e9c7d36b0
2013-11-05Introduce HiFi E.T. MA8/MA8C ports.Andrew Ryabinin1-1/+1
HiFi E.T. MA8 is almost the same as MA9 except another DAC(pcm1792 in ma8, df1704 in ma9). MA8 has ILI9342 lcd, MA8C has ILI9342C lcd. Change-Id: If2ac04f5a3382590b2a392c46286559f54b2ed6a
2013-11-05Introduce HiFi E.T. MA9C port.Andrew Ryabinin1-1/+2
The only difference between this target and HiFi E.T. MA9 is display driver (ILI9342 in MA9 and ILI9342c in MA9C) Change-Id: Icc3d2490f850902a653175360f12283f3708bbb7
2013-10-21imx233/bootloader: fix comment about disk initAmaury Pouly1-2/+2
Change-Id: I44a676237564490771a1ed2c81e9434fc6c6f74d
2013-10-21imx233: fix bootloaderAmaury Pouly1-2/+1
The bootloader must call disk_init_subsystem() because it is multithread (because of USB), otherwise strange things might happen. Calling disk_init() is unnecessary since it is call when mounting partitions. Change-Id: If7aff3dea0b96144e2a9b0f6179a9a0a632b93ed
2013-09-26imx233/bl: usb mode has priority over holdAmaury Pouly1-17/+18
Change-Id: I0d124eaed0ebf1ca18c022684a96dfbf7d740c7e
2013-09-26imx233/bootloader: fix redAmaury Pouly1-0/+5
Change-Id: I209cdee6007d3b3c039f6b0b63a30fabc8aefb41
2013-09-26imx233/bootloader: power off on holdAmaury Pouly1-0/+12
Change-Id: I3081ca6e47bed5a69e6163cb539d0a8516b689d2
2013-09-25imx233: always boost in bootloaderAmaury Pouly1-0/+5
Many imx233 targets boot in a very low performance mode, typically cpu and dram at 24MHz. This results in very slow boots and very unstable USB bootloader mode. Since cpu frequency scaling is disabled in bootloader in rockbox, always make the frequency scaling code available and boost at boot time. Change-Id: Ie96623c00f7c4cd9a377b84dcb14b772558cfa4d
2013-09-25imx233: shorten bootloader messages when screen is smallAmaury Pouly1-7/+10
Change-Id: I403a76277e756cf06b4dca4906940d5fbf32d763
2013-09-05fix copyrightAmaury Pouly1-1/+1
Change-Id: Ie0dea643afa93d9a919e4f2406de65aed174c0a6
2013-06-27sansa connect bootloader: fix redMarcin Bukat1-0/+1
Change-Id: Ide8784e33e1671bf915b5375fb5cd8dae4e09ae6
2013-06-27Move load_firmware() to separate fileMarcin Bukat20-470/+124
The idea is to share loading code between bootloaders and rolo(). Change-Id: I1656ed91946d7a05cb7c9fa7a16793c3c862a5cd Reviewed-on: Reviewed-by: Marcin Bukat <>
2013-06-18imx233: fix bootloader for stmp3600 and stmp3700Amaury Pouly1-1/+3
Change-Id: Icfdf4c0a35813576c9d2a60558b4c00599f091fc
2013-06-16imx233: rewrite power using new registersAmaury Pouly1-1/+1
Change-Id: Ifbee91161220419f4d1750672b5c4ae3537cefca
2013-05-06Introduce HiFi E.T MA9 port.Andrew Ryabinin1-1/+1
Change-Id: I79aadc958fd5222f26f91ed127f8c6fb2c465dc2
2013-04-30Fix red.Andrew Ryabinin1-1/+1
Change-Id: I64cf91a2ddc4fbf89d83bb5a401e9e4021f8c160
2013-04-30rk27xx: initialize i2c driver in bootloader.Andrew Ryabinin1-0/+2
Change-Id: I0b343425d0cfef4d4609cabca79c1f31d8327d3b Reviewed-on: Reviewed-by: Andrew Ryabinin <>
2012-11-24Another optimization for the OF in the mi4 format.Szymon Dziok1-34/+10
What it does: - removes unnecessary file operations for the OF (one lseek() and one read() per one key), - simplifies the code and reduces the code size. Speedup is not noticeable but theoretically some is. Change-Id: I43a6dd21d3af48ea8d3b27d676c84b2084c0b88c Reviewed-on: Tested-by: Szymon Dziok <> Reviewed-by: Thomas Martitz <> Reviewed-by: Szymon Dziok <>
2012-08-30imx233: display battery voltage in bootloader (along with percent)Amaury Pouly1-1/+1
Change-Id: I7b14496ba891a9ff2f6373571a11835d37abee4e
2012-07-10rk27xx: support entering rkusb mode on rk2706AMarcin Bukat1-9/+36
We know about two different bootroms. First can be found in rk2706A, the second in rk2706B and rk2705. This two versions are very similar but memory addresses are different. It seems it is possible to distinguish bootrom version by reading SCU_ID register. Change-Id: I01681b5e3a82930ae74a5cce6ab0244d7cd333d2
2012-06-23pp bootloader: speed up loading of the OF in the mi4 formatSzymon Dziok1-20/+13
This change replaces an odd way to increment tea key in a function responsible for finding the proper key (it doesn't have to be done in a for loop, it's just adding a 32bit number to a 128bit number). It reduces the time needed to find the key practically to zero and it gives in the best case 2 seconds of overall speedup in loading the OF. Change-Id: I0632526c3dfeb4d0603e77239f298a89076b630b Reviewed-on: Tested-by: Szymon Dziok <> Reviewed-by: Thomas Martitz <> Reviewed-by: Szymon Dziok <>
2012-05-20Make Meizu M3 compile againBertrik Sikken1-6/+12
Change-Id: I44436068cf6f2c3942fb63f988bf627eaa9abb97
2012-05-19imx233: move the freescale partition handling to its own fileAmaury Pouly1-6/+13
The freescale firmware partitions has a lots of quirks that need to be dealt with, so do it the proper way. Change-Id: I8a5bd3fb462a4df143bc6c931057f3ffedd4b3d3
2012-05-07remove debug-target.hRafaël Carré1-1/+0
2012-04-30rk27xx: Print rockbox version in bootloader.bootloader_hifimanhm801_v1bootloader_hifimanhm60x_v1Andrew Ryabinin1-0/+2
Change-Id: I7f19f45e85aa09b0b19573053f7f27794196e6fb
2012-04-27rk27xx: Add failsafe mode to the bootloaderMarcin Bukat1-2/+80
Change-Id: Iba8fdc50b3c71831a6f55d15779fee8d1f12cb4f
2012-04-04Refactor and unify objcopy calls in the build system. Also now properly ↵Thomas Martitz1-1/+1
handles DEBUG builds on hosted targets to keep debug symbols if necessary. Change-Id: I884031b79c6d49479e4d95752f35ced68872dd5d
2012-03-26Fix bootloaders.Thomas Martitz1-9/+4
Change-Id: I7e1666d604c554509375a4ae858ff3cd7be96b3a
2012-03-19center logo horizontaly in bootloader version of show_logo()Marcin Bukat1-2/+3
Change-Id: I537466825de7f3bc8d55d9519cd27f562fbb344f
2012-03-15imx233: enable charging in bootloader USB mode by including powermgmtAmaury Pouly1-0/+13
Change-Id: I8b91b3ab60cb9ffaa127333e9bcef8c33be742fa
2012-03-04rename rkw.h header fileMarcin Bukat1-1/+1
Change-Id: I2cb6ea7da9c20ed0ef87f4b8ea90d2e4a4a3bca2
2012-03-04rk27xx: Implement dualboot capable bootloaderMarcin Bukat1-163/+89
Change-Id: I399e10635f611bdf6f7c1bd5843fa132dc88bfb4
2012-02-28imx233: print power up source in the bootloaderAmaury Pouly1-0/+2
Change-Id: I9ff4738b7efdb25ab57b0061f60c7fde58b9a0b5
2012-02-22unwarminder: fix bootloader buildsMarcin Bukat1-4/+10
Change-Id: I045a4c9639ff17c96b514996574d41f586b5bd7c
2012-01-03Rework powermgmt to enable code re-use on appliation and sims.Thomas Martitz5-5/+5
* Introduce CONFIG_BATTERY_MEASURE define, to allow targets (application) to break powermgmt.c's assumption about the ability to read battery voltage. There's now additionally percentage (android) and remaining time measure (maemo). No measure at all also works (sdl app). If voltage can't be measured, then battery_level() is king and it'll be used for power_history and runtime estimation. * Implement target's API in the simulator, i.e. _battery_voltage(), so it doesn't need to implement it's own powermgmt.c and other stubs. Now the sim behaves much more like a native target, although it still changes the simulated battery voltage quickly, * Other changes include include renaming battery_adc_voltage() to _battery_voltage(), for consistency with the new target functions and making some of the apps code aware that voltage and runtime estimation is not always available. git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2012-01-03The connect is not a PP and doesn't have ATA storageRafaël Carré1-1/+0
git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657