Results 1 to 8 of 8

Thread: USB2AX firmaware update

  1. USB2AX firmaware update

    Hi guys,

    Long time no see... I'm not dead, just far away ^^

    So I just wanted to point out that I uploaded a new version of the firmware, with fixes contributed by Pedro Ramillo for Seed Robotics and Anthony who works at the LAAS.

    The fixes address two problems with the Dynamixel 2.0 protocol:
    - One is that the buffer was sometimes not big enough and that could lead to corrupted packets when reading the whole table of a DXL2.0 servo (since they have tables that are much bigger than the DXL 1.0 ones).

    - The other is that some DXL2.0 packets generated spurious error packets from the USB2AX to the host. In the latest version of the Dynamixel Manager at least, it caused freezes and general chaos.

    http://xevelabs.com/doku.php?id=prod...irmware_update

    I've been cleaning the website up from dead links and various outdated stuff, don't hesitate to report anything I missed please.

    Cheers!
    ---
    Personal blog: http://xevel.org
    USB2AX documentation: http://xevelabs.com

  2. #2

    Re: USB2AX firmaware update

    Good to see you back!
    Do you have a Linux version of the bootloader loader? (Or is there another DFU loader that works there?)
    Windows 10 is much harder to install drivers on than Windows 7 :-(

  3. Re: USB2AX firmaware update

    Hey Jwatte

    There's a part of the page (in the middle though, I just added links to it in the page index : http://xevelabs.com/doku.php?id=prod...rlinux_version ) about uploading from Linux. dfu-programmer works well on that platform, and is in the packages of some of the most usual flavors of the OS.
    ---
    Personal blog: http://xevel.org
    USB2AX documentation: http://xevelabs.com

  4. #4

    Re: USB2AX firmaware update

    Great -- sorry I missed it, and thanks for improving the indexing :-)

  5. Re: USB2AX firmaware update

    Hi, I just tried to update the firmware using the update tool. However, I get "unsuspected error" after hitting "Flash USB2AX". Any idea what could be the reason? It seems to happen during validation. This is the output I get:

    (...)
    Trying to open COM3...
    The thread 0x2cf8 has exited with code 0 (0x0).
    Exception thrown: 'System.IO.IOException' in System.dll
    The thread 0x1ac0 has exited with code 0 (0x0).
    The thread 0x13e0 has exited with code 0 (0x0).
    ***0***


    ***0***
    Validating...
    6540 bytes used (22.81%)


    ***1***

  6. #6

    Re: USB2AX firmaware update

    Maybe COM3 isn't the right COM port?

  7. Re: USB2AX firmaware update

    just double checked. It doesnt seem to be the reason

  8. Re: USB2AX firmaware update

    Seems there is a problem with my update software on Win10, please use another of the methods (linux or one of the recovery options).
    Damn DotNet framework breaks slightly every time they update it, and I don't have all the versions all the time...
    ---
    Personal blog: http://xevel.org
    USB2AX documentation: http://xevelabs.com

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Update firmware CM-510
    By chitti in forum Software and Programming
    Replies: 0
    Last Post: 01-16-2013, 05:42 AM
  2. Career update
    By ScuD in forum Off Topic
    Replies: 8
    Last Post: 10-20-2008, 08:49 AM
  3. Project Jim and the Thinga-ma-bot - Update 3
    By JimH in forum Rovers
    Replies: 14
    Last Post: 04-21-2008, 08:54 PM
  4. Speecys SPC-101 First Update
    By cdraptor in forum Humanoids, Walkers & Crawlers
    Replies: 6
    Last Post: 09-18-2007, 05:40 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •