Short version is that I changed the sampling rate in order to get a longer capture, but didn't realize that the stop sign is "cancel" -- not stop. I.e., in order to see the capture, it looks like I have to wait for the capture to finish on its own. I thought the stop sign was allowing me to do a partial.
While trying to figure out how things work, I managed to attempt a capture (nothing useful), but it appeared to be working (I saw a tiny little blip). Then I somehow managed to get myself stuck in this mode where I can't see the diagram, all of the tools menu items are gray except for serial console, the measurement tab is disabled, captures never end and I can't cancel them once started.
I've tried resetting the OB and relaunched the client, but nothing changes.
Firmware flash does *not* work from 2012 MBPR and VMWare. Flashed it from my husband's PC and it worked fine.
I first had trouble getting is connected to the MBPR. I plug it in, it powers on and VMWare (which is always running) prompts me whether I want to connect to Mac or Windows. I select Mac. And VMWare keeps prompting with the same question over and over.
However, I closed VMWare, it automatically connected to the Mac, the serial device shows up and is immediately recognized by the ols client.
So the OB is good and I didn't fry it. I just need to remember I can't use it when VMWare is running.
FWIW, this only happens on the 2012 MBPR. I have an old 2006 MBP with VMWare running and it doesn't have this issue.
No matter... I'm up and running and off to figure out how to do some captures.
[quote author="tayken"]Windows VM usage with hardware is usually problematic. Timeout is normal with that. I had a hard time updating the firmware on a Linux machine too but a Windows machine solved the problem. If you have access to one, you can try it out.[/quote]
Thanks tayken. This would be the first time I've had hardware issues in a VM, but I'll try to hijack my husband's PC to see if I have the same behavior.
[quote author="tayken"]But seeing that even with shorting pins you're having a hard time getting it into the bootloader mode, there seems to be a problem with the hardware. Can you check for solder bridges or unsoldered pins/parts?[/quote]
I agree it feels like a hardware issue. I did look at the board, but didn't see anything unusual. I'll take another look -- it seems I need to prove that before seeed will replace the board.
I contacted seeedstudio (which is where I bought it) and they said I have to come here for support. I either need to make it work, or have someone confirm that the behavior I'm seeing means a defective ROM... otherwise, I've bought myself a pretty expensive coaster.
My first problem was that I didn't get a USB port when I connected it to my MBP (Mavericks). So I loaded all the software to a Windows VM and connected it there. I really want to use it from the MBP, so I decided to update the PIC and FPGA.
So the first thing that happens is that the PIC update has intermittent success -- very flaky. When I try to update the PIC from ols_upgrader, all I get is timeout errors. It's successful with ols_winloader, but only about %50 of the time.
I can't update the FPGA at all -- from neither ols_upgrader nor ols_winloader. ols_upgrader keeps telling me it can't write to flash ROM. ols_winloader says it can't erase the flash ROM.
The other thing that's flaky is that I sometimes have a hard time getting it into bootloader mode (by shorting the two pins -- not using the ols_upgrader tools).
I've tried different USB cables and reinstalled drivers, and keep getting the same results. It's probably worth mentioning that this is one of the OLS's with the WinBond flash.
Does this sound like a bad OLS? Or are there other things that could cause the kinds of failures I'm seeing?
