Yet Another Question From a N00B Regarding FW

Home Forums TinyG TinyG Support Yet Another Question From a N00B Regarding FW

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #6896
    mrhiggs
    Member

    Hey Guys, Let me preface that I am completely new to CNC/and the coding involved so I’m really sorry if this question is a total waste of your time. I have looked through the WIKI as well as this forum for 2 days hoping and hoping that I wouldn’t have to make a fool of myself and ask…

    Per the previous FW build not being able to save settings that was put onto my TinyG from tgFX I decided to update the FW via avrdude.

    Here is where I’m at:

    C:\Users\Jarret>”C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avrdude.e
    xe” -p x192a3 -c avr109 -b 115200 -P COM3 -U flash:w:tinyg-edge-438.02.hex

    Connecting to programmer: .
    Found programmer: Id = “XBoot++”; type = S
    Software Version = 1.7; No Hardware Version given.
    Programmer supports auto addr increment.
    Programmer supports buffered memory access with buffersize=512 bytes.

    Programmer supports the following devices:
    Device code: 0x7b

    avrdude.exe: AVR device initialized and ready to accept instructions

    Reading | ################################################## | 100% 0.01s

    avrdude.exe: Device signature = 0x1e9744
    avrdude.exe: NOTE: FLASH memory has been specified, an erase cycle will be perfo
    rmed
    To disable this feature, specify the -D option.
    avrdude.exe: erasing chip
    avrdude.exe: reading input file “tinyg-edge-438.02.hex”
    avrdude.exe: error opening tinyg-edge-438.02.hex: No such file or directory
    avrdude.exe: input file tinyg-edge-438.02.hex auto detected as invalid format
    avrdude.exe: can’t open input file tinyg-edge-438.02.hex: No such file or direct
    ory
    avrdude.exe: read from file ‘tinyg-edge-438.02.hex’ failed

    avrdude.exe done. Thank you.

    I have the hex file sitting there in the same folder with avrdude.exe, and it DOES appear to be a valid “.hex” file.

    What dumb thing have I done that I am overlooking?

    Thank you in advance

    #6898
    mrhiggs
    Member

    WOW! ok as stated I’m a n00b and apparently a bit of a fool… Just looked at my command line prompt code… YIKES. Sorry for wasting time. Please feel free to delete post.

    #6899
    cmcgrath5035
    Moderator

    You are apparently running from windows.
    Load up Coolterm as well and get aquainted.

    Good luck on your journey

    #6900
    cmcgrath5035
    Moderator

    You are apparently running from windows.
    Load up Coolterm as well and get aquainted.

    Good luck on your journey

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