»
«


maple-v2-proto

A good story to come… Great things have been brewing. Show us what you’ve been cooking!


This entry was posted by okie on Friday, February 5th, 2010 at 2:59 am. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response.

7 Responses


  1. Written by Pete
    on February 11, 2010 at 2:53 pm
    Reply · Permalink

    I am eagerly anticipating v2!

  2. Written by jessb
    on February 11, 2010 at 9:01 pm
    Reply · Permalink

    sweeeeeeeeeeeet

  3. Written by signal7
    on February 24, 2010 at 6:06 pm
    Reply · Permalink

    Gosh, I wish I could get my hands on one just so I could experiment with some decoupling techniques. Your noise is my gold!

  4. Written by joshua wojnas
    on February 26, 2010 at 4:30 pm
    Reply · Permalink

    I still wonder if it will be able to print out the usb port like a high speed or full speed virtual com port at usb speeds.

    • Written by bnewbold
      on March 30, 2010 at 11:20 pm
      Reply · Permalink

      We certainly seem to get a lot of through put over the USB serial port though I can’t say i’ve calculated or tested the speed. Do you have a particular application in mind?

    • Written by okie
      on March 31, 2010 at 9:23 am
      Reply · Permalink

      Good question. How straight-forward it is to write software for your computer that can access the USB port/virtual COM port at full and high speed USB data rates?

    • Written by poslathian
      on April 27, 2010 at 4:53 pm
      Reply · Permalink

      in the new library setup (libmaple + wirish, now in our github repo) the usb stack has been stripped out of the bootloader as a runtime library and is now statically compiled in to user sketches. Why is this good? because there is nothing preventing you from using that usb stack to implement all sorts of faster/better/different usb protocols on maple! You could do fast isochronous pipes, for audio/video, or be an HID device (accelerometer mouse!) or whatever.

      The only catch is that the ide uses the virtual com port to pulse DTR/RTS and engage the auto-reset into bootloader mode when you hit program. This is just like how arduino does it. So if you strip out the virtual com port in favor of whatever hotness you come up with, youll need to either manually reset the board for programming or add some hooks to the IDE/your code to engage a reset.

      We’d love to see some advanced usb stuff happen on this platform!

Leave a Reply




Contact webmaster@leaflabs.com with website issues

Powered by WordPress, nginx, Linux, vim, and coffee.

This site intended to be valid HTML 4.01 Strict. Best viewed with any standards-compliant browser.

Copyright LeafLabs LLC, 2009-2010.
Unless otherwise noted all content on this website is released under the Creative Commons Attribution Licence 3.0

Hello Anonymous! Login?