Issues with Maple and Maple Native on Ubuntu 14.04 AMD64

LeafLabs Garden » Support » Maple Hardware Support

Issues with Maple and Maple Native on Ubuntu 14.04 AMD64

(5 posts) (3 voices)

Started 1 year ago by gp
Latest reply from gp

gp
Member

Hello,

A while ago I bought a Maple rev5 Spring 2012 and Maple Native Beta Fall 2011, but never did anything with them.

Today after a new install of Ubuntu 14.04 AMD64, I decided to get the Maple IDE installed and unbox the Maple and Maple Native; however I'm having some issues with the IDE and these boards for some reason, so hopefully someone can shed some light on these issues.

I've followed the 64-bit installation instructions exactly, with exception to ia32-libs which gives the following message:

----------

Package ia32-libs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
lib32z1 lib32ncurses5 lib32bz2-1.0

----------

I then installed ib32z1 lib32ncurses5 and lib32bz2-1.0 as a replacement.

Starting with the Maple, once plugged in I get the following in dmesg:

----------

[ 5352.804118] usb 4-1: new full-speed USB device number 25 using uhci_hcd
[ 5352.965139] usb 4-1: New USB device found, idVendor=1eaf, idProduct=0003
[ 5352.965149] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5352.965157] usb 4-1: Product: Maple 003
[ 5352.965164] usb 4-1: Manufacturer: LeafLabs
[ 5352.965171] usb 4-1: SerialNumber: LLM 003
[ 5355.460292] usb 4-1: USB disconnect, device number 25

----------

Although the udev rules have been installed, no /dev/ttyACM0 device (or any /dev/ttyACM* device for that matter) is initiated. Here is the output from lsusb and dfu-util -l:

----------

root@T61:~# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@T61:~# dfu-util -l
dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

----------

The board is not detected by the Maple IDE (serial ports are greyed out), and even running the IDE as root results in a "Couldn't find the DFU device: [1EAF:0003]" error when attempting to upload to the LeafLabs Maple Rev3+ Flash target in the IDE.

I then put the Maple into Perpetual Bootloader Mode, with the following dmesg output:

----------

[ 5718.276160] usb 4-1: new full-speed USB device number 26 using uhci_hcd
[ 5718.436242] usb 4-1: New USB device found, idVendor=1eaf, idProduct=0003
[ 5718.436254] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5718.436262] usb 4-1: Product: Maple 003
[ 5718.436269] usb 4-1: Manufacturer: LeafLabs
[ 5718.436276] usb 4-1: SerialNumber: LLM 003

----------

lsusb and dfu-util -l:

root@T61:~/Projects/maple/maple-ide-v0.0.12# lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 026: ID 1eaf:0003
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@T61:~/Projects/maple/maple-ide-v0.0.12# dfu-util -l
dfu-util 0.5

(C) 2005-2008 by Weston Schmidt, Harald Welte and OpenMoko Inc.
(C) 2010-2011 Tormod Volden (DfuSe support)
This program is Free Software and has ABSOLUTELY NO WARRANTY

dfu-util does currently only support DFU version 1.0

Found DFU: [1eaf:0003] devnum=0, cfg=1, intf=0, alt=0, name="DFU Pro"
Found DFU: [1eaf:0003] devnum=0, cfg=1, intf=0, alt=1, name="DFU Program FLASH 0x08005000"

----------

Same "Couldn't find the DFU device: [1EAF:0003]" message as before, even when running the Maple IDE as root.

I have a bit better luck with the Maple Native, but still can't upload a program to it. After compiling again and uploading to the Native flash target, I get this far:

----------

Binary sketch size is reported above. Check it against a 500000 byte maximum.
Loading via dfu-util
Resetting to bootloader via DTR pulse

----------

...at which point the IDE just hangs. Resetting the board doesn't appear to execute any loaded code in the flash of the Native, and putting it into perpetual bootloader mode results with:

----------

Searching for DFU device [1EAF:0003]...
Error!

Couldn't find the DFU device: [1EAF:0003]

----------

Any ideas? I know that Ubuntu 14.04 was just released, but at the very least the Maple should be registering a /dev/ttyACM* device which it never does (although at least the Maple Native gets that far).

Thanks in advance!

Posted 1 year ago #
gp
Member

Does anyone actually use these forums anymore?

Is the Maple project dead at this point?

Posted 1 year ago #
ventosus
Member

Have you tried with the unix toolchain directly?
It may help to narrow down the problem.

http://leaflabs.com/docs/unix-toolchain.html

Posted 1 year ago #
tormod
Member

> Does anyone actually use these forums anymore?

Why do you ask this? You can see as well as me that people post both questions and answers here every week. Or are you so offended about nobody answering you the same day?

> Package ia32-libs is not available, but is referred to by another package.

Using ia32-libs have become obsoleted by the new multi-architecture system https://wiki.debian.org/Multiarch in newer Linux distributions.

> Although the udev rules have been installed, no /dev/ttyACM0 device (or any /dev/ttyACM* device for that matter) is initiated.

The udev rules in question *only* change the owner/permissions on the device, they will not make the device show up or not in the device tree.

It is important to understand that the Maple shows up as several completely different USB devices from the point of view of the computer. For 8 seconds after reset (or forever in "perpetual" mode if you press Button before the blinking goes from fast to slow) it is a USB DFU device, with USB ID 1eaf:0003 (you can see this with "lsusb") - this is the USB bootloader. There is no device under /dev except the rather anonymous node under /dev/bus/usb/X/Y.

When an application ("sketch") is running there will appear a CDC serial port device (/dev/ttyACMx under Linux) unless the application has disabled this. This is USB ID 1eaf:0002.

So unless you put it into the perpetual bootloader, the IDE has only a small window where it should start up dfu-util behind the scene and start communicating with the bootloader. I can see from the timestamps in your log above that the OS only sees the bootloader for 2.5 seconds.

And if there is a problem with the sketch, it might not start up the serial port, and in this case the IDE is not able to switch the Maple into bootloader mode. Then you'll have to use the perpetual bootloader.

I'd suggest you put the device into perpetual boot loader, and run dfu-util manually at least the first time. I believe the IDE reports somewhere where it puts the .bin file (the compiled sketch to be uploaded). In your case I guess the IDE freaks out because there is no CDC serial port device to talk to and thus no DTR to pulse.

Finally, there is also the serial boot loader mode that is used for flashing the bootloader. This operates on a real serial port (pins PA9 and PA10), and there is no USB device active. This mode is entered by holding the Button while releasing Reset - kind of easy to mix up with the perpetual bootloader.

Posted 1 year ago #
gp
Member

This was an issue with 64-bit Ubuntu and libusb support:

root@T61:~/maple-ide-v0.0.12/hardware/tools/arm/bin# ./dfu-util
./dfu-util: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory

Fixed with apt-get install libusb-0.1-4:i386

Thanks for the help.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.