Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won

  1. Weird, the prebuilt bin works for me in xubuntu 12.10. In theory it should not affect anything, except for the changed code start address.
  2. @chicken: I've added precompiled bootloader images to the github repo. @igor: Thanks for the helpful suggestions. I agree that the code isn't very polished, will try to fix it up, get rid of magic numbers. To be honest, I didn't put much thought into that filesystem image. I've created it by making a 512kB file, formatting it to FAT12 with 512b sectors using mkfs.msdos, mounting it and adding a firmware.bin file of the right size. According to FAT documentation, f0 means a 1.44MB/2.88MB floppy. Like you said, it's just cosmetic, I didn't bother with it Yeah, might as well get rid of the whole thing. That's the sector where the data starts. That's the number of blocks for user firmware, should be 240 of course, or calculated from USER_PROGRAM_LENGTH. Oops, that's a bug. But that line is not needed anymore. In the latest version, the program assumes the first cluster in the data region the host tries to write to is the beginning of a new firmware, so it doesn't look at the directory entries at all. I had to do this, because on Ubuntu, the file manager first starts with writing data to disk (and not in the same place as the previous firmware.bin), and modifies the directory entry afterwards (Windows, for example, modifies the directory entry first). Also thanks to this, you don't have to rename your binary to firmware.bin anymore. I don't think it gets written to, but we have a lot of RAM, why not use it?
  3. The error when ejecting on Linux is harmless, I have no idea how to fix it. Check the latest version, I think I have fixed problems with uploading firmware via a file manager on Linux. The problem was that when using a file manager, copying a file to the drive interacts with the filesystem differently than just using cp from the command line! Edit: In the latest version, you don't have to name your file "firmware.bin" anymore!
  4. Hi, I wanted to share a bootloader I wrote for the Stellaris Launchpad (and other boards/chips if you change it up a bit). The bootloader acts as a mass storage device, and allows for software update by simply moving a file to the device. No software or drivers needed! It's inspired by the bootloader found on some NXP LPC microcontrollers. The project was surprisingly easy thanks to the awesome Stellaris USB Library. Grab the source here: https://github.com/Emeryth/Stellaris-mass-storage-bootloader Pleas report any issues you encounter.
  • Create New...