On Wed, Apr 2, 2014 at 7:54 AM, Paul Fertser <fercerpav@gmail.com> wrote:
On Wed, Apr 02, 2014 at 08:59:16AM +0400, Paul Fertser wrote:
> On Tue, Apr 01, 2014 at 08:15:13PM +0100, Spencer Oliver wrote:
> > I feel your pain, if I recall I had to take my board into work and use a
> > windoze pc to update.
> It would be interesting to know if waiting would work for you
> too. I've tried many times, and it was fairly consistent: after 3
> minutes 8 seconds the device appeared ready for mounting :)

The trick here is not only waiting but also not using any kind of
automouting as simple "mount /dev/sdb /mnt" results in a failure
(device apparently needs power-cycling after that) while
"mount -t vfat /dev/sdb /mnt" works.

I had no problems getting the device to mount in Ubuntu 12.04, it was really just plug'n'play. Both the bootloader volume and the default mass-storage flashing application. However, after upgrading the bootloader to the latest version (with support for linux and win 8.1) I managed to reload the latest version of the default application onto the blank debugger but I couldn't switch to CMSIS-DAP afterwards. Or any other application for that matter. The bootloader swallows the s19 file but still starts the default application.
For the reference,


<input name="BOARD" type="hidden" id="BOARD" value="FRDM-KL25Z" />
<input name="BOOTVER" type="hidden" id="BOOTVER" value="1.01" />

This is older than the version said to support linux, which is 1.10 I think.