Who is using the USB Bootloader with MAC OS-X ?

[lpcware]

Content originally posted in LPCWare by Rob65 on Sun Aug 28 01:25:51 MST 2011
I was wondering if there are more users out there with an Apple using the USBBootloader.
As can be read in this thread DEGoodmanWilson is having problems downloading an image into the Flash using OS-X.

I then just realized that for one of my products I am confronted with a group of users that only work on MAC OS-X (I've talked to a number of photographers and some of them even don't own a PC)

So it would be nice to know if there are other users that have similar problems with OS-X.

Regards,[INDENT]Rob
[/INDENT]

[lpcware]

Content originally posted in LPCWare by mhjerde on Thu Dec 15 10:14:41 MST 2011
Has anyone made any progress on getting firmware updating to work on a Mac?

There seems to be some workarounds like using command line tools to copy the file or disable .DS_Store file creation, but that won't fly with end users.

If the problem is that the Mac attempts to store the resource fork in a subdirectory, maybe it would be possible to circumvent this by implementing dummy commands in the bootloader?

[lpcware]

Content originally posted in LPCWare by TheFallGuy on Sat Oct 29 09:08:47 MST 2011
I don't know whether this trick will work for USB drives, but might be worth a look

http://osxdaily.com/2010/02/03/how-to-prevent-ds_store-file-creation/

[lpcware]

Content originally posted in LPCWare by DEGoodmanWilson on Sat Oct 29 05:57:04 MST 2011

---

Quote: mhjerde
Well, that is a bummer. So your work is just being shelved?

I've done a bit of testing on the Mac. It looks like the Mac tries to write additional data when copying the file. This is probably to store the resource fork.
I got an 'not enough space' error. Copying with the cp command did not work either for this test.

---

Of course, I didn't think of the extra files that OS X tries to create. That might very well be the culprit.

That said, I've been using the command line 'cp' method consistently since I first mentioned this issue. I agree that it is no good for end-users, but it at least permits me to get code on the board from my Mac! I wonder why it isn't working for you?

[lpcware]

Content originally posted in LPCWare by mhjerde on Wed Aug 31 11:09:23 MST 2011

---

Quote: Rob65
Actually, mine is kind of finished - but my customer/distributor of the product stopped his business ...

---

Well, that is a bummer. So your work is just being shelved?

I've done a bit of testing on the Mac. It looks like the Mac tries to write additional data when copying the file. This is probably to store the resource fork.
I got an 'not enough space' error. Copying with the cp command did not work either for this test.

[lpcware]

Content originally posted in LPCWare by Rob65 on Tue Aug 30 22:39:50 MST 2011

---

Quote: mhjerde
I've yet to dive in to the details of the usb bootloader. Maybe it is time to get started.

---

Actually, mine is kind of finished - but my customer/distributor of the product stopped his business ...

You can always use the application that Ken mentioned - that should work.
The thing is that there seems to be a difference in the way Finder and the command line write to the USB bootloader. Bootloader does not like this and messes up the code ...

Command line works (according to DE) but then you do need to provide a proper manual on how to do this.

Rob

[lpcware]

Content originally posted in LPCWare by mhjerde on Tue Aug 30 12:22:34 MST 2011
Hi Rob
I'm also working on a device for photographers, using the lpc17xx series and hoping to support firmware upgrades on OS X :-) You are right that all photogs uses Macs.

I've yet to dive in to the details of the usb bootloader. Maybe it is time to get started.

[lpcware]

Content originally posted in LPCWare by Rob65 on Mon Aug 29 23:32:47 MST 2011
Ken,

I forgot to mention ... I was talking about the usb_bootloader for the lpc17xx series.

that Application Note tells how to do automatic detection of the device and program the lpc13xx device with the ROM based USB bootloader - sadly the 1300 is the only series having this option built in ...

But the application note only talks about automatic detection and firmware update using a special tool. The thing is that when using the standard file manager in OS-X (Finder) the device is not programmed correctly (at least, DEGoodmanWilson was not able to do so). Command line programming seems to work.

I have (will have) a base of users who are photographers. I found that a number of them are non-technical, they do know PhotoShop better than anyone else I know. They are also able to copy a file from one location to the other - but don't ask them to install special software ...
So I will be relying on the possibility to update software using a standard disk interface, other options are SD card or USB memory stick.

Rob

[lpcware]

Content originally posted in LPCWare by kendwyer on Mon Aug 29 04:33:54 MST 2011
Hi,

I believe that this is discussed in the following AN:
http://ics.nxp.com/support/documents/microcontrollers/zip/an10986.zip