LeafLabs Garden » Topic: IDE Version 0.0.5

LeafLabs Garden » Topic: IDE Version 0.0.5 http://forums.leaflabs.com/topic.php?id=51 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:16:17 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php poslathian on "IDE Version 0.0.5" http://forums.leaflabs.com/topic.php?id=51#post-244 Sat, 12 Jun 2010 18:01:11 +0000 poslathian 244@http://forums.leaflabs.com/ Jakob, This looks like a permissions issue. Try running the ide as root, e.g. $ sudo ./maple-ide On some systems, you may need to do a little work before running the udev script, such as creating the plugdev group. You may also need to do a little work such as restarting your udev. Please see the udev section of the linux install instructions here: <a href="http://leaflabs.com/docs/maple-ide/installation/" rel="nofollow">http://leaflabs.com/docs/maple-ide/installation/</a> hope that helps! videomusik on "IDE Version 0.0.5" http://forums.leaflabs.com/topic.php?id=51#post-243 Sat, 12 Jun 2010 15:54:51 +0000 videomusik 243@http://forums.leaflabs.com/ Hey leafblowers. I hope this is the right place to post, as I am new to Maple and this forum. I just got my board to today, and hurried home to hook it up and get it a-blinking. As of now, I have yet to get it to upload the program. I would like to just check that I've done everything right, as I am certain that it should be possible with my setup. I am running Ubuntu 10.4LTS on a standard PC. I followed your quickstart guide at <a href="http://leaflabs.com/docs/maple/quickstart/" rel="nofollow">http://leaflabs.com/docs/maple/quickstart/</a> and followed the JRE installation instruction on <a href="http://leaflabs.com/docs/maple-ide/installation/" rel="nofollow">http://leaflabs.com/docs/maple-ide/installation/</a>. running the terminal command to install JRE I decided not to continue (see below) because I was not sure what removing all those files would mean to rest of my system. Checking under "Ubuntu software center I could also see that "OpenJDK Java 6 Runtime" was already installed along with "openjdk-6-jre-lib", "openjdk-6-jre-headless" and "icedtea-6-jre-cacao". So I assumed that I had all the Java components I needed already. ******************* terminal text ******************* user@computer:~$ sudo aptitude install openjdk-6-jre [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing package states... Done The following packages will be REMOVED: amarok-common{u} amarok-utils{u} gobject-introspection{u} java-wrappers{u} kde-icons-oxygen{u} kdemultimedia-kio-plugins{u} libass3{u} libaudclient2{u} libaudcore1{u} libaudid3tag2{u} libaudutil1{u} libbinio1ldbl{u} libboost-date-time1.38.0{u} libboost-thread1.38.0{u} libcairo2-dev{u} libcddb2{u} libcelt0{u} libcommons-cli-java{u} libcommons-lang-java{u} libdirectfb-dev{u} libdirectfb-extra{u} libexiv2-5{u} libexpat1-dev{u} libfaad0{u} libffado1{u} libfluidsynth1{u} libfontconfig1-dev{u} libfreebob0{u} libfreetype6-dev{u} libglew1.5{u} libjline-java{u} libjpeg62-dev{u} libkcddb4{u} libknotificationitem1{u} liblash2{u} liblastfm0{u} liblog4j1.2-java{u} liblzma0{u} libmcs1{u} libmowgli1{u} libopenjpeg2{u} libpixman-1-dev{u} libpng12-dev{u} libprojectm-data{u} libprojectm2{u} libqt4-gui{u} libqt4-phonon{u} libqtscript4-core{u} libqtscript4-gui{u} libqtscript4-network{u} libqtscript4-sql{u} libqtscript4-uitools{u} libqtscript4-xml{u} libreadline5{u} libresid-builder0c2a{u} libsad2{u} libsidplay2{u} libswt-cairo-gtk-3.4-jni{u} libswt-gnome-gtk-3.4-jni{u} libswt-gtk-3.4-java{u} libswt-gtk-3.4-jni{u} libswt-mozilla-gtk-3.4-jni{u} libsysfs-dev{u} libtag-extras1{u} libx264-67{u} libxcb-render-util0-dev{u} libxcb-render0-dev{u} libxfixes-dev{u} libxft-dev{u} libxml++2.6-2{u} libxrender-dev{u} lsb{u} lsb-core{u} lsb-cxx{u} lsb-desktop{u} lsb-graphics{u} lsb-printing{u} m4{u} ncurses-term{u} nvidia-185-kernel-source{u} nvidia-185-libvdpau{u} pax{u} rhino{u} sdparm{u} wine-gecko{u} x11proto-fixes-dev{u} x11proto-render-dev{u} 0 packages upgraded, 0 newly installed, 87 to remove and 11 not upgraded. Need to get 0B of archives. After unpacking 73,5MB will be freed. Do you want to continue? [Y/n/?] n ************************************************************************* After this I downloaded the latest Linux version of the IDE: maple-ide-LATEST-linux32.tgz and unpacked to my desktop as suggested. I opened the folder and ran the install-udev-rules.sh. Then I run the IDE by double-clicking the maple-ide shell-script and selecting run in the following dialog. In the IDE I select the blink sketch. I plug in my Maple board in the front USB port on my desktop computer and press the reset button, immediately followed by the "but" button to make it enter "perpetual bootloader mode" to give me enough time to upload a sketch. I select "Tools -> Board -> LeafLabs R3 Maple to RAM", and "Tools -> Serial Port -> /dev/ttyS0" as my serial port - the only one available (when I am in normal "non-perpetual bootloader mode" I also have the option of /dev/ttyACM0, but I understand from this article: "http://leaflabs.com/docs/maple-bootloader/", that the CDC ACM is only used for user code). After having pressed the "play" button to compile the blink sketch, I press the "upload" button, and the following gets printed in my IDE terminal window: ****************************************************** Going to build using 'make' (ARM) Compiling core... Compiling any libs... Compiling the sketch... running linker asynchronously... running obj copy asynchronously... running size asynchronously... /tmp/build7589438001463521808.tmp/Blink.cpp.bin : section size addr .data 11056 0 Total 11056 Binary sketch size is reported above. Check it against a 17000 byte maximum. Loading via dfu-util Resetting to bootloader via DTR pulse Searching for DFU device [1EAF:0003]... Found it! Cannot claim interface: could not claim interface 0: Operation not permitted Opening USB Device 0x1eaf:0x0003... Found Runtime: [0x1eaf:0x0003] devnum=0, cfg=0, intf=0, alt=0, name="UNDEFINED" Claiming USB DFU Interface... ************************************************** And then it hangs here forever.. Am I correct in assuming that I should be doing the right thing up until this point? I also tried resetting the board, and _not_ entering perpetual bootloader mode. When I upload the sketch with the /dev/ttyS0 device serial port selected I get: ********************************************************** Going to build using 'make' (ARM) Compiling core... Compiling any libs... Compiling the sketch... running linker asynchronously... running obj copy asynchronously... running size asynchronously... /tmp/build7589438001463521808.tmp/Blink.cpp.bin : section size addr .data 11056 0 Total 11056 Binary sketch size is reported above. Check it against a 17000 byte maximum. Loading via dfu-util Resetting to bootloader via DTR pulse Searching for DFU device [1EAF:0003]... dfu-util - (C) 2007 by OpenMoko Inc. This program is Free Software and has ABSOLUTELY NO WARRANTY Couldn't find the DFU device: [1EAF:0003] ************************************************ with he last three lines (five, including empty lines) appearing a few seconds later. And when I select the /dev/ttyACM0 port I get the same as when in perpetual boot-loader mode. (which doesn't make sense to me, because I thought the CDC ACM port was for user code. But then again I have no clue really what's going on). I know this turned out to be a very long and probably far too simple post for what you guys are doing at the moment, but I thought maybe someone else might have a similar problem, and be very new to this thing. I am very stuck here, and would appreciate any help to get going again. I tried to follow the quickstart guide as closely as possible, and I think I have a pretty standard setup. Is there something very obvious that I am missing here? Best Regards, Jakob bnewbold on "IDE Version 0.0.5" http://forums.leaflabs.com/topic.php?id=51#post-241 Fri, 11 Jun 2010 18:55:49 +0000 bnewbold 241@http://forums.leaflabs.com/ Hi Starbug, sorry it didn't work "out of the box"... In "perpetual bootloader" mode the blue status LED should blink at a constant rate forever. In that mode the IDE should compain about "failing to reset" the board (because it's already "reset" into DFU mode) but then find it and upload via DFU. If you're successfully in perpetual bootloader (constant blinking) but there is still at "DFU device not found: 0x1EAF:0x0003" type error than there's something strange about your setup*? It sounds like that wasn't your problem though as you were able to upload after several resets... did you do anything different to get it to finally work? Now that you've managed to upload a new program (to FLASH?) can you upload new ones reliably? On to the COMM issue, you shouldn't have to flash any new bootloader, and the serial monitor in the IDE should work fine with any baudrate when using SerialUSB. One thing you could try is removing any writes (.print or .println) to Serial# (1, 2, or 3) from your sketch if you have any. Writing to those USART ports will sometimes block if there is no FTDI device or similar receiving the transmission (will be fixed in 0.1.0). This could be causing your program to halt. As another debugging step, can you confirm that your sketch is running correctly and that you just aren't receiving the bytes on windows? For example you could use the standard Examples/Digital/Blink program and add "SerialUSB.println("Hello starbug!");" to the end of the loop(), then check to make sure that the LED keeps blinking (if it doesn't blink that indicates that the program halted, possibly when trying to write). A last, most advanced debugging trick would be to try an alternative serial port monitor that can configure the DTR/RTS lines and make sure that at least one of those lines is pulled high when you are receiving bytes from the Maple. I can't think of such a program for windows (PySerial does it if you're comfortable with python, or GtkTerm on linux, or "Serial Tools" on Mac OSX). I'll ask around! *As some more context, the windows DFU drivers we use are a standard part of windows; the "driver" that needs to be installed is just a text file that tells windows to use that particular driver for the Maple device. With the Maple in perpetual bootloader mode it's a very simple DFU device with no tricky timing constraints, so unless you were using a virtual machine, a bunch of USB hubs, or something along those lines it should work every time. We've never had an upload fail on any operating system (including Windows XP 32bit) with the Maple in perpetual bootloader mode, so if you had trouble with that we'd definitely like to hear about it! starbug on "IDE Version 0.0.5" http://forums.leaflabs.com/topic.php?id=51#post-240 Fri, 11 Jun 2010 17:47:27 +0000 starbug 240@http://forums.leaflabs.com/ Installed the new 0.0.5 release of the IDE. Compiled and uploaded the InteractiveTest. I didnot see any reaction after (hold the BUT button for a few seconds immediately after you release the RESET button). It was just like before as the dfu was not detected and i had to press the reset button several times. But i managed to get a upload. Everything was fine, but after reset there is no output on the defined COMM SerialUSB. Does COMM use the same Baudrate as the SerialPort in the IDE Tools and can i also use the SerialMonitor from the IDE? I am a bit confused, must i flash the bootloader out of the new 005 directory nor not? Must i install some new drivers? Give me tip please. bnewbold on "IDE Version 0.0.5" http://forums.leaflabs.com/topic.php?id=51#post-236 Fri, 11 Jun 2010 15:04:15 +0000 bnewbold 236@http://forums.leaflabs.com/ As mentioned in a recent blog post, we've uploaded a new 0.0.5 release of the IDE; you can download from <a href="http://static.leaflabs.com/pub/leaflabs/maple-ide/" rel="nofollow">http://static.leaflabs.com/pub/leaflabs/maple-ide/</a> . Major Changes: <ul> <li>Mac OSX Compatibility! Tested on Snow Leopard (10.6) machines, both 32bit (old mac mini) and 64bit. It should be physically possible to get things compiled on other versions of OSX, but you would have to be a compilation wizard. </li> <li>New reset scheme (to work on OSX, ugh): on the falling edge of DTR look in the first USB packed for "1EAF" </li> <li>SerialUSB is now compiled in by default in sketches (required for reset scheme) </li> <li>"Less-blocking" SerialUSB: only push bytes into buffer if DTR or RTS is high (indicating a serial port monitor running on some host OS somewhere) </li> <li>Newer, cleaner binary-depedancies download scheme for building the IDE (you can directly download the codesourcery binaries for all platforms from <a href="http://static.leaflabs.com/pub/codesourcery/" rel="nofollow">http://static.leaflabs.com/pub/codesourcery/</a> ) </li> <li>Some documentation tweaks (more to come!) </li> </ul> Incompatabilities: <ul> <li>"SerialUSB" not "HardwareUSB": you now shouldn't declare a HardwareUsb device in your header. Just use SerialUSB like you would Serial1, Serial2, etc. </li> <li>New reset-over-serial scheme: if you have a maple with an old program on it, you may have to enter perpetual bootloader mode (hold the BUT button for a few seconds immediately after you release the RESET button) to upload a new program with the new scheme. The reason for this is that the special USB-serial reset-to-bootloader message that the maple listens for has changed; the IDE will try both methods but this isn't reliable. Any new program that gets successfully uploaded will have the new (much more reliable!) method included, so this only has to be done once. This is related to the bootloader, but not actually an issue with the bootloader: the "wait for reset" code is part of the SerialUSB interrupt routine in libmaple. </li> </ul> We're sorry to push changes that possibly break your existing code! Unless there are further upload and serial port issues, our development focus for the 0.1.0 release is to iron out any further API changes to prevent later broken incompatibilities. We'll also be testing on more OS versions and configurations, restructuring libmaple t (we aren't planning on doing releases) to be portable across the whole STM32F103 line (for Maple Mini and Maple Native!), providing a higher level interface for timers, upgrading Linux and Win32 to the 2010q1 version of codesourcery gcc, and possibly changing the block behavior of all the HardwareSerial and SerialUSB devices. Other development priorities (if we can squeeze them in!) are USB HID class functionality, wrapping up the I2C library, and porting arduino libraries. EDIT: just noticed a bug in ASCIITable: one of the Serial.prints should be SerialUSB.print, also you almost certainly want to replace the final infinite loop in "if(thisByte == 126) {}" with "thisByte = 0;" to make the table dump over and over; otherwise you'll miss it!