Hi,
I got one of the new Arch Pro boards connected to my Mac. Using the USB Port next to the ethernet socket I’ll get a Arch Pro storage device of 2k capacity with a HTML file. On the second USB port which should be for programming with bins, I don’t get the expected MBED storage.
According to syslog, the device is found but times out:
USBMSC Identifier (non-unique): 90040200E48DC4231972ABDF 0xd28 0x204 0x100, 1
USBF: 170635.871 AppleUSBEHCI::Found a transaction which hasn’t moved in 5000 milliseconds on bus 0xfa, timing out! (Addr: 6, EP: 0)
USBF: 170646.880 AppleUSBEHCI::Found a transaction past the completion deadline on bus 0xfa, timing out! (Addr: 6, EP: 2)
after that the message:
USBF: 170711.923 AppleUSBEHCI::Found a transaction which hasn’t moved in 5000 milliseconds on bus 0xfa, timing out! (Addr: 0, EP: 0)
is repeating constantly
The device can be also found in System Profiler as an MBED CMSIS-DAP device … anybody got an idea?
Hi Haikowick,
Please try to press the button, and then plug in Arch Pro through the debug USB connector(next to the button). If a drive named “MBED LOADER” pops out, it is possibly that the interface firmware of Arch Pro is damaged. Have a look at https://mbed.org/users/seeed/notebook/the-mbed-interface-of-arch-pro/. And update the firmware.
And what version of Mac OS X do you use? I tested a Arch Pro on a Macbook Air with Mac OS X 10.9. It works. I would like to find out if the Arch Pro doesn’t work on a special version of Mac OS X.
Hi Yihui,
holding the reset button did work, the MBED LOADER drive did show up and I could copy the latest firmware to the device, the device did disappear and the ARCH PRO did restart. Nevertheless, this did not solve the problem. The MBED drive is still not available. As a difference to the pre-loaded version, neither syslog nor System Profiler show up the MBED now at all.
I’m using Mavericks 10.9.1, too. If I can help you in any way, please tell me 
Best, Haiko
Hi Haiko,
The “MBED LOADER” drive shows, it’s a good news.
It may be that the power supply of one usb port is not enough for the Ethernet peripheral of LPC1768 consumes lots of power.
Could you power the Arch Pro using two usb port?
Best,
Yihui
Hi Yihui,
unfortunately I don’t have a micro USB Y cable at hand. Giving it a try first with a second USB cable and second with a 0.7A rated external power supply didn’t change anything, too. Same LED indications at startup, no syslog/profiler information and no MBED device in normal operation.
Best,
Haiko
Hi Haiko,
It’s weird that “MBED LOADER” drive is available but “MBED” drive is not.
Are you able to try another computer? I will keep seeking any potential issues.
Best,
Yihui
Hi Yihui,
as a first I tried the Arch with two other Macs (one with 10.9.1 and one with 10.8.6) I could access. Unfortunately I don’t have a non-Mac at hand ^^ but I’ll try at the weekend.
Maybe the Arch Pro is broken?
Best, Haiko
“MBED LOADER” drive indicates the Arch Pro is not broken.
So let’s check if the mbed interface firmware works properly.
-
mbed interface firmware v1.0 of Arch Pro: in the attached zip file
This firmware will turn on 3 LEDs(D22, D21 and D23, near the button) by default. press the button, yellow led will blink once.
-
mbed interface firmware v1.1: https://github.com/xiongyihui/CMSIS-DAP/raw/arch_pro/interface/mdk/lpc11u35/lpc11u35_lpc1768_if_mbed_bootloader.bin
This firmware will turn off 3 LEDsby default. press the button, all three LEDs will blink once.
When “MBED LOADER” drive is showed, there is a timeout to upgrade new mbed interface firmware.
mbed_interface_v1.zip (22.5 KB)
Hi Yihui,
obviously updating the firmware or loading it doesn’t work properly. For both files, the result is the same: after copying the image to the MBED LOADER drive, the Arch reboots. Powering it up again (on USB or the external power supply), only D23 lights up. After a certain time, D1 blinks several times and that’s all. D21 and D22 never light up.
Another idea? 
Best, Haiko
Hi Haiko,
I think UARTcommunication may be the reason, as the default application of LPC1768 will send some data through UART at startup.
So I custom another mbed interface firmware(attached) to disable UART communication. I would like you to try it.
If this firmware works, download a new application to LPC1768 and avoid UART communication at the very beginning.
Then try mbed interface firmware v1.1: https://github.com/xiongyihui/CMSIS-DAP/raw/arch_pro/interface/mdk/lpc11u35/lpc11u35_lpc1768_if_mbed_bootloader.bin
best, yihui
mbed_interface_without_uart.zip (20.7 KB)
Hi Yihui,
I’m sorry to tell, but that didn’t work too. Is there anything I could have done wrong updating the firmware? ^^
After dropping the non-UART-firmware and power cycling, the Arch behaves as before and there’s still no MBED drive.
Best, Haiko
Hi Haiko,
If the on-UART firmware is successfully flashed, pressing the button will turn on 3 LEDs(near the button) once.
Is there any application that will write a file to a new detected drive?
I think the best way to find out if this board is broken is using another computer(windows is preferred) to upgrade the firmware and check if there is a “MBED” drive.
Best,
Yihui
Hi Haiko and Yihui,
Recently, I received my Arch Pro and encountered the same issue on Mac OSX 10.8.5. I tried upgrading all three firmware images mentioned in this thread under OSX with no luck. There is always no MBED storage show up under OSX.
Then I switch to a Windows XP laptop to perform firmware upgrades again. Amazingly MBED storage show up right after the upgrade and capable of download mbed compiled images. From this point, my Arch Pro works normally in both Windows and Mac.
According to my experience, I think a brand new Arch Pro could get confused when first plugged into Mac OSX, and performing firmware upgrade under Windows is the cure.
Best,
CY
Hi CY,
many thanks for that update! Unfortunately I couldn’t find the time after my last post to test the firmware update on a Windows machine. As soon as I get access to a “classic” PC (seems to be more and more seldom ^^) I’ll try and post my experience
Best, Haiko
Hi,
finally I could test your “fix” for the problem. So, flashing the updated firmware using a non-Mac laptop with Windows XP was possible for me too. Afterwards the MBED still didn’t show up on the Macbook. So back to the Windows machine I uploaded an empty “dummy” project and that did the trick. Now the MBED device also shows up on the Macbook. I think that the pre-loaded software using UART is the problem.
Finally a solution Thanks to both of you.
