Building g2core for DUE-gshield problems

Home › Forums › TinyG › TinyG Support › Building g2core for DUE-gshield problems

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • June 2, 2018 at 10:21 am #11001
    wahran
    Member

    Hello all,
    I am using Windows 7 64 bits.
    I have a DUE board, and I purchased a gshield v5 to try with it. I downloaded the binary firmware (outdated) and flashed it into the DUE, and I got the 2x TinyG V2 COM ports in the Device Manager, and used both Goko and UGS with some success (some of the functions didn’t work).

    I decided to build a more recent version of the firmware. I setup first under Ubuntu (VMWare), and built it according to the directions (gshield + DUE). I flashed the new firmware and upon rebooting, I get an unknown “TinyG v2” device, I cannot install any drivers for it.

    I figured something was wrong with the build process. I then followed the Windows AS 7 directions, and setup again, pulled the firmware from Git, and rebuilt.

    I selected gshield again and ATSM3X8E for the DUE CPU. The elf/bin files get put under g2core/bin/ShapeokoDualY-gShield (not sure why Shapeoko…). I flashed it and got the same single “TinyG v2” unknown device.

    If at any time, I put back the outdated online firmware, I get the right two COM ports and things are back to normal.

    I am obviously building/compiling the wrong stuff (target, board..etc) What I am doing wrong?

    Thanks!

    Wahran.

    June 2, 2018 at 10:44 am #11002
    cmcgrath5035
    Moderator

    A few ideas, you have many things going on here (maybe).

    The current builds of G2core you could try can be found here:
    https://github.com/synthetos/g2/releases

    g2core-gShield-101.02.bin is the most up to date prebuilt binary for DUE/gshield.

    Read the G2core wiki.
    As of release 100.xx, G2core reverted to exposing only one USB divice when connecting an transitioned to using Line Mode protocol.

    If you continue to see the “unknown “TinyG v2” device” on startup, you might have a driver issue with Win7(64 bit).

    June 2, 2018 at 10:47 am #11003
    Zootalaws
    Member

    Which build did you use?

    You should be using the edge 101.02 branch.

    Worked fine for me with a Due clone.

    You haven’t given much to go on.

    June 2, 2018 at 11:09 am #11004
    wahran
    Member

    Thank you both for the quick replies.

    cmcgrath5035 :
    I started with this whole think a couple days ago, and did as much reading as possible to get me going, some of it, I am sure outdated (I have only seen the mention of 2 COM ports, data and control, must have been reading old stuff…) Thanks for the pointers. I tried the 101.02 firmware and I get the same “TinyG v2” device issue, so I guess that is a driver issue.
    Booted my Win10 laptop, driver loads a generic COM port, Connects with Goko or UGS 2.0 , but can’t get anything to work (mostly jogging…), will have to spend some more time there, now that I know the firmware is good.

    Zootalaws: First day with Git ;-( I cloned the g2.git –recursive, without any other parameters, so I guess the latest, whatever that is, have to read on how to select a specific branch. Sorry, I saw my post going into 3 long paragraphs and didn’t want to make it too painful to read…

    June 2, 2018 at 4:25 pm #11005
    cmcgrath5035
    Moderator

    Read thru https://github.com/synthetos/g2/blob/edge/README.md
    Pay particular attention to the long list of things that were introduced with 100.xx. Big chages from the

    Most folks use Edge branch.
    I am not a Goko user, have seen reports that Goko might not be G2core friendly yet. I’d try CoolTerm or putty for getting started.
    Line Mode protocol is sort of new here.
    I believe it is a correct statement that the G2core interface should appear as a plain USB interface, nothing special. when running via the DUE user port (not the programming port), you are connected to native USB hardware, not an FTDI-like device.

    June 2, 2018 at 5:24 pm #11006
    wahran
    Member

    I am not a Goko user either, I am not committed to anything yet, I was just getting a feel for different g code senders. I tried both UGS and Goko, and they both worked with the older firmware (I believe 078?), i.e. steppers on axis moved when jogged or gcode file downloaded.
    I have been using the programming port for flashing the firmware and the native USB port for talking to the board.
    I gave up on Windows 7 and the COM driver for now, I have been using a Windows 10 laptop, where the driver loaded without a glitch, I can even connect and “talk” to the board from a terminal session in putty, but no luck with UGS or Goko. Is there a specific version of UGS that works with 100.xx?
    Thanks.

    June 2, 2018 at 8:18 pm #11007
    cmcgrath5035
    Moderator

    Is there a specific version of UGS that works with 100.xx?

    I don’t recall seeing traffic on the UGS question, perhaps someone will chime in.
    Does UGS have a “speak JSON” option?
    G2core defaults to JSON for almost everything.
    You can modify that behavior by modifying $ej parameter

    June 6, 2018 at 8:25 am #11011
    Zootalaws
    Member

    UGS is JSON compliant. You configure it with a json file and it interprets json for control.

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.