There's something about these old Macs. I've got the same problem. The drive appears as read-only, and you can't drop anything onto it. And by the way, it's now late 2017, and no progress.
capt_cpt I am working on a Mac Pro 15" 2009 running 10.11.6 El Capitan and WinXP running on Parallels Virtual Machine.
I've got a suspiciously similar Mac Pro 13" mid-2009 and 10.11.6 El Capitan. My WinXP runs on VMWare. More about Windows in a bit.
mamunJust as a reminder you don't need to use USB Bridge tool to program the Xpress board.
I got more than a little irritated with the notion that I didn't need the USB Bridge, and no explanation as to what
I should use. Turns out, I got caught up in a detour, because the screen shot in the quick start guide makes it look like there's a path between the compiled file and the IDE's green status buttons at the bottom of MPLABX(press). When I clicked there I got taken through the USB Bridge installation, and while that
was working fine, it said that my programming tool wasn't.
Well, the programming tool isn't needed, and neither is the USB bridge, asstated. What IS
needed is a working emulated mass storage device (or MSD)--that's what the dev board is supposed to look like when you plug it in. With regard to that,
ralphrmartinI already thought o[f] doing this. You cannot reformat the board - it is a read only device!
The board is going to have a USB-enabled PIC emulating a mass-storage device, and you can be sure no one wasted time in the driver giving it the capability to rewrite its directory structure. So, it's more of a case of the host computer and the device having to get together on this "write a file" service that it's supposed to provide.
stevehowesIf it's anything like it is on Ubuntu you can copy the files in a terminal.
This initially struck me as irrelevant. But it turns out to be genius. Between this and the remark about not needing the USB Bridge, I began to wonder if the eval-board-MSD just wanted to have a file written to it. You'll recall that early on, user "capt-cpt" was talking about using the Windows machine inside his Mac to program the device. So I woke up Windows XP over in the VmWare (Fusion) window and plugged the board in. At this point, we had a little tiff about there not being any drivers for XP, but after I told it to just leave it unconfigured, I noticed a new drive appear in the File Manager! And it let me create files on it! I had write access! And not just hex files, but whatever I tried. Mind you, this is running on the very same Mac that won't talk to the thing natively.
To get to the point of the story, I was able to drag hex files onto the drive and they would program the device. I had built one that turns the LED on, and another that turns it off, so I could get a sense that it was doing what i intended. And no Bridge running, either. In fact, once you have the hex files, you don't need to have MPLAB-Ex or even the browser open. I discovered all it really does is wait for someone to close a (hex?) file and it will transfer it out to the board. "Closing the file" included these tests:
- Dragging a file from another drive and dropping it.
- Copying one file to another, even on the emulated drive.
- Copying a different file over top of existing one.
- Copying a file to an arbitrarily-named hex file.
- Opening the hex file in an editor and hitting save (control-S)
Also of note, the next time I plugged the board in, all the files were gone. So apparently it's all done in RAM.
Posted for posterity, because I sure could have benefitted from finding info like this.