macsrevenge

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • July 21, 2015 at 2:47 pm in reply to: Travel per revolution problem #8076
    macsrevenge
    Member

    thanks again for the info.

    July 19, 2015 at 4:45 pm in reply to: Travel per revolution problem #8068
    macsrevenge
    Member

    Now that’s strange. Been dealing with this problem all day, seems to have spontaneously fixed itself?? Thanks for reading.

    July 19, 2015 at 4:21 pm in reply to: Bare Xmega configuration help #8066
    macsrevenge
    Member

    I must admit I just went back and followed the official TinyG wiki page. It flashed no problem using Atmel studio 6 via an AVRISP MkII. Not sure what the initial difficulties were caused by. Have encountered a new problem but may be best to put that in a new thread.

    July 15, 2015 at 5:01 pm in reply to: Bare Xmega configuration help #8013
    macsrevenge
    Member

    Managed to get everything up and running again, bootloader and all. Thanks again for the help.

    June 17, 2015 at 4:17 pm in reply to: Bare Xmega configuration help #7849
    macsrevenge
    Member

    If in doubt go back to the basics. dry solder joint at pin 18 (Tx) on the replacement Xmega. Now get communication both ways in coolterm. Can hopefully get some configuration stuff done now. Thanks a million for your help.

    June 17, 2015 at 7:28 am in reply to: Bare Xmega configuration help #7845
    macsrevenge
    Member

    Thanks, certainly some things to try out. Should clarify the reset was a hardware reset using the button on the board, the firmware is being uplaoded via the ISP header rather than via the usb/bootloader route (which is unavailable to me due to the bootloader issues). CP shows the current firmware in a popup at the top of the window when it connects to the com port.

    Will physically check the traces between the ftdi chip and the micro tonight. Though the last micro was damaged it still functioned (just ran at 120 degrees) and the comms worked at this point so presuming the ftdi chip itself is OK.

    Thanks again for the input.

    June 17, 2015 at 1:48 am in reply to: Bare Xmega configuration help #7841
    macsrevenge
    Member

    Hi Cmcgrath, thanks for the reply. Sorry if I was not clear in the last post.

    In coolterm, on connection and board reset I will get:

    {“r”:{“fv”:0.970,”fb”:440.14,”hp”:1,”hv”:8,”id”:”5U1316-KLZ”,”msg”:”SYSTEM READY”},”f”:[1,0,0,8197]}

    but then nothing, no response other than a brief flash of D4 to any command including $,$$ and ?.

    chillipepper will connect via the serial port json server and identify the board firmware but any commands just build up in the buffer.

    I thought there would be some kind of EEPROM initialisation on first run. Just leaves me scratching my head on where to go now.

  • Author
    Posts
Viewing 7 posts - 1 through 7 (of 7 total)