dgtlmoon

I tried flashing just a small image (actually the grbl project hex which I know wont work but I wanted to see if it would pass to rule out any filesize issues) and it still fails

so it’s something higher up, most likely the bootloader has got itself in a pickle

Request to contact url sent on friday, I included the Id # of the board in that request

Heya

So it’s a rPi Model 2 B. Last I checked rPi’s dont run windows, so the answer is in my first comment there (Linux)

I need to repeat myself here for the sake of keeping this ontopic – All I simply done was accidentally uploaded some binary data in the gcode field and now the device is requiring a reflash because the LOCK bits are not set right

I see your reply here in the forum but I have not got a reply from your company about if my board is involved in the problems you mentioned

I have tried reflashing the device with the information from other people who have also have had their board stuck in SPDir from https://www.synthetos.com/topics/tinyg-wont-boot-spdir-light-flashing-constantly/

I have to admit that I really have zero windows experience but have been doing some atmel programming as a hobby for a few years from Linux using avrdude.

So I followed https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware – I’ve tried the packaged Ubuntu avrdude as well as the one mentioned in the wiki

root@dgtlmoon-XPS-15-9550:~/workspace/cnc/tinyg/arduino-flash-tools-master/tools_linux_64/avrdude/bin# avrdude -p x192a3 -c avr109 -b 115200 -P /dev/ttyUSB0 -e -U flash:w:../../../../tinyg-master-440.20.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: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9744 (probably x192a3u)
avrdude: erasing chip
avrdude: reading input file "tinyg-master-440.20.hex"
avrdude: input file tinyg-master-440.20.hex auto detected as Intel Hex
avrdude: writing flash (118274 bytes):

Writing | ################################################## | 100% 10.91s

avrdude: 118274 bytes of flash written
avrdude: verifying flash memory against tinyg-master-440.20.hex:
avrdude: load data flash data from input file tinyg-master-440.20.hex:
avrdude: input file tinyg-master-440.20.hex auto detected as Intel Hex
avrdude: input file tinyg-master-440.20.hex contains 118274 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 11.14s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0000
         0xff != 0x0c
avrdude: verification error; content mismatch

avrdude done.  Thank you.

The image looks correct

# md5sum tinyg-master-440.20.hex 
6d1ddc5e56784fc69ccec021735f7953  tinyg-master-440.20.hex

# head -n 5 tinyg-master-440.20.hex 
:100000000C94E24B0C94034C0C9477D20C94034C5C
:100010000C94034C0C94034C0C94034C0C94034C24
:100020000C94034C0C94034C0C94034C0C94A2D4ED
:100030000C94034C0C94034C0C9468B70C94034C34
:100040000C94034C0C94034C0C94034C0C94034CF4

No problems registering the USB device in dmesg

[  381.605671] usb 1-1: new full-speed USB device number 3 using xhci_hcd
[  381.741747] usb 1-1: New USB device found, idVendor=0403, idProduct=6015
[  381.741760] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  381.741764] usb 1-1: Product: FT230X Basic UART
[  381.741768] usb 1-1: Manufacturer: FTDI
[  381.741771] usb 1-1: SerialNumber: DN010NRM
[  382.786824] usbcore: registered new interface driver usbserial
[  382.786843] usbcore: registered new interface driver usbserial_generic
[  382.786856] usbserial: USB Serial support registered for generic
[  382.789628] usbcore: registered new interface driver ftdi_sio
[  382.789644] usbserial: USB Serial support registered for FTDI USB Serial Device
[  382.789671] ftdi_sio 1-1:1.0: FTDI USB Serial Device converter detected
[  382.789698] usb 1-1: Detected FT-X
[  382.789870] usb 1-1: FTDI USB Serial Device converter now attached to ttyUSB0

This is run from Ubuntu

The only success I see is people saying they reflashed it using a AVRMkII https://www.synthetos.com/topics/did-i-blow-up-my-board/

Which led me to this https://github.com/synthetos/TinyG/wiki/Firmware-Update-Verification-Failure

which says, basically I need to buy that piece of hardware to be able to use your product 🙁

Im really not sure what todo from here, did anyone in synthetos get my contact form with my Board Id to let me know if it was part of the problem?

• This reply was modified 8 years, 6 months ago by dgtlmoon.

Thanks for the reply! Ah so it’s not as simple as I thought then 🙂

It’s the SPDir LED that flashes, I did try the avrdude reflash which worked but gave the error that led me to the page about using the additional piece of hardware to reset the LOCK bits with Atmel Studio 6

I was running the TinyG behind the excellent serial-port-json-server on a Raspberry Pi

I will send the other details to that contact form now

thanks again!