Software advice

[Jimmckeown]

I would like to know where the best place is for getting advice on 9x problems. I have a TGY 9x V2 that I have upgraded with a Frsky DIY DHT 2 way osd system, with the Fr SKY D8R 2 RX. Did the blue backlight thing change the battery to LiPo. Then without losing a beat I got a USBasp, eepe, AVRDude, soldered tiny little wires to the mother board and now in the process of upgrading the firmware. The only problem seems to persist has to do Windows 7 failing to recognize unsigned usb driver for the USBasp. Periodically I trick it to work. The usb port talks to TGY 9x through the USBasp programer. The screen is powered and the TX chirps. When I turn on the TX the chirping stops. Now I go to eepe or the 9CX companion and attempt to retrieve a copy of the TGY 9x firmware. At this point I receive this message
=================================================================================
Started AVRDUDE
C:/Program Files (x86)/companion9x/avrdude.exe -c usbasp -p m64 -P usb -U eeprom:r:C:/Users/JMCK/AppData/Local/Temp/temp.hex:i
=================================================================================
avrdude.exe: error: could not find USB device "USBasp" with vid=0x16c0 pid=0x5dc

=================================================================================
AVRDUDE done - exit code 1
=================================================================================

My interpretation is that the USBasp device is faulty. Could you give an opinion and/or set me up with someone that can step me thru the process,
thank you for the time it takes.

[B12]

Most likely your issue is the driver install for the usbasp. That error means the avrdude cannot communicate with the programmer for some reason and the reason is 9/10 driver issue especially with those cursed vistas and sevens. The chirping is the low voltage alarm of the tx since the usb only supplies 5V. It is to be ignored. The tx is powered via usb during programming and turning it on by the switch is not needed or recommended.

[GrootWitbaas]

Check if you are using the correct path for avrdude, and check under device manager if you have usbasp installed.


---
I am here: http://maps.google.com/maps?ll=48.930808,9.478291
Sent from my iPhone using Tapatalk

[erazz]

The output shows that he got AVRDUDE.

I would think this is a driver issue.... Damn windoze.

[cre8tiveleo]

Winblows! I got out of programming because of winblows.


---
I am here: http://maps.google.com/maps?ll=44.003098,-79.457323

[GrootWitbaas]

There are some avrdude version that does not support usbasp. I have come across this when i was doing the windows guide elsewhere on the forum. That is why I suggest to check the path, if it's not /eepe/ then he may point to another avrdude he has installed. I will look for the posts about this during the night when at work and forced to use windowzzzz

Gota love Mac, no drivers needed, it just works


Sent from my iPhone using Tapatalk

[cre8tiveleo]

It's not the Mac, it's the operating system. :p


---
I am here: http://maps.google.com/maps?ll=44.003098,-79.457323

[GrootWitbaas]

You are talking to someone who hacked pc hardware for years to run osx, and tbh since I got a real Mac I have not looked back. It's not just the one or the other, but the combination, just like 9x and er9x

Now back to topic before the MOD picks up on this


---
I am here: http://maps.google.com/maps?ll=48.930664,9.478555
Sent from my iPhone using Tapatalk

[cre8tiveleo]

Lol


---
I am here: http://maps.google.com/maps?ll=44.003175,-79.457723

[erazz]

Gota love Mac, no drivers needed, it just works

Ahemm... Cough.... Linux... No Drivers..... Mac = copycat.... Cough, chough, bronchitis

[erazz]

Back on subject...

Jimmckeown,
Check out this thread:
viewtopic.php?f=5&t=393&p=4275#p4197

[ShowMaster]

Maybe a link here to a good working USB driver for SP and the solder in for win 7 32 and 64 bit OS.
Driver issues seems to be at the top of posts, along with wrong solder points and reversed battery.
I use a XP netbook and never tried my w7 64B system so I may have had dumb luck right off.
Anyone know how to create a BART boot CD with the best OS on it?
I'm nor sure about eepe updates
Just thinking of a good way to make it all play.
What about Mac? Can a Mac run a BART boot CD and run another OS for programmig only?
SM

[erazz]

Hmmm.... Common issues... wiki?

[GrootWitbaas]

What about Mac? Can a Mac run a BART boot CD and run another OS for programmig only?
SM

Why would you wanna spoil a mac with that ... it just works

[ekill]

I just started playing around with the Mac version while waiting for my programmer and noticed that I can't seem to find/load the latest binaries and save to a folder like on the Windows version. Or is it only when updating eepe on the Mac that it includes the latest binaries?

Thanks....Earl

[GrootWitbaas]

New eepe for mac was done, see topic eepe on mac


Sent from my iPhone using Tapatalk

[cre8tiveleo]

Gota love Mac, no drivers needed, it just works

Ahemm... Cough.... Linux... No Drivers..... Mac = copycat.... Cough, chough, bronchitis

Ahem.. cough cough.. UNIX... No Drivers.. linux, mac... copycat... ahem.. cough cough... hack! I'm not sick.. physically...

[GrootWitbaas]

Erm...... Lets no go off topic.


Sent from my iPhone using Tapatalk

[Romolo]

On Windogs7 64 bit, even if drivers are correctly recognized they may not work due to missing/wrong signature...
At the start press F8 and go without signature check...

[Crucial]

Where did you download your drivers from?

This driver zip says it has a driver for x64 but I haven't tested it.
http://www.fischl.de/usbasp/usbasp-wind ... -05-28.zip

This is a tutorial for getting a USBASP to work on Win 7. If I remember right this was the process I used to get a signed driver to work on my Win 7 install.
http://www.wortelsoft.nl/english/usbasp.html

I don't have to do the F8 dance when I want to program.

[kaos]

Got the same problem today. I got my ERsky9x board going. now ready to upload /download eeprom files from it using companion9x. companino9x installed without problem. I can open my er9x eepe file using the companion no problem. but when I try to download eeprom file from the ERsky9x Tx, this showed up:
======================================================================
avrdude.exe: error: could not find USB device "USBasp" with vid=0x16c0 pid=0x5dc

=================================================================================
AVRDUDE done - exit code 1
===========================================================================

I am still using eepe for my er9x TX and upload/ down load from eeprom without any problem.

using Win7 64 Ultimate

When usb calbe attached to Tx, there is sound indicating device attached and TX shows "USB"

Any idea?

[cre8tiveleo]

Turn on your tx when attached to usb, try it.


---
I am here: http://tapatalk.com/map.php?kuxz3c

[kaos]

no smoke would come out?
just tried it. nothing happened. good news is no smoke.

attached usb with Tx off, turn Tx on, still get the same message. The Tx still shows "USB" with no back light on.

try turn Tx on 1st before attaching to usb? Tried this too. once TX on, plug USB, the Tx light shuts off and 'USB' shows. but still , get the same message from Companion9x.

SamBa still communicate with Tx.

[Hippo]

The ersky board requires Sam-Ba instead of avrdude. There's some info in the wiki about it. Several hoops to jump through, but not too difficult.

Dan

[Hippo]

Oh, I think I see. Have you set the firmware type properly in companion9x? I think it knew automatically to use samba instead of avrdude one I selected the right firmware.

[kaos]

you are saying change the set up 'arvrdude location' to 'xxxxxxxxxxxx/samba.exe' ?

currently is: "C:/Program Files (x86)/companion9x/avrdude.exe"

yes!
Did not know need to set the 'setup' for port and sam-ba location. defaulted to avrdude and com23.

just downloaded the bin file and opened up in companion9x.

Thx Hippo. Still looking forward to your cnc board.

[Rob Thomson]

You will also need to make sure that the profile in companion is set too open9x/arm or ersky9x/arm.

And that the com port setting is correct.

Sent from my Nexus 7 using Tapatalk 2

[kaos]

thx Rob. just edit my post. both of your points are needed. Thought it is auto detect. After all, Window/usb is not that smart.

I did change to com4 though.

[kaos]

still not quite right.
I did 'read from eeprom memory to file' and it seems to download the bin file. with 'SAM-BA done - exit code 1'. but the running green bar on top stopped short before the end and % shows 95%. I just exit it.

load the down loaded bin file. 1st model is fine. but if I select anyother model, "Comapnion.exe stopped working" close program and I am kicked out of Comanion. 1st model has no porblem. but not any other model.

[kaos]

Here is what shows while 'read eeeprom memory to file'. (com23 does not work, com4 did)
may be this help:
=================================================================================
Started SAM-BA
C:/Program Files (x86)/atmel/sam-ba_2.12/sam-ba.exe \USBserial\COM4 at91sam3s4-9x C:/Users/Wg/AppData/Local/Temp/temp.tcl
=================================================================================
-I- Waiting ...
-I- TCL platform : Windows NT
-I- SAM-BA 2.12 on : windows
current connection is \USBserial\COM4, \\USBserial\\COM4 to be matched
-I- Retrieved arguments from command line :
-I- argv 0 : \USBserial\COM4
-I- argv 1 : at91sam3s4-9x
-I- argv 2 : C:/Users/Wg/AppData/Local/Temp/temp.tcl
-I- Connection : \USBserial\COM4 (target(comType) = 0)
-I- Board : at91sam3s4-9x
-I- Traces Level : 4
-I- target(handle) : 52761960
Read device Chip ID at 0x400e0640 --- get 0x00000000
Read device Chip ID at 0x400e0740 --- get 0x28a00960
-I- Found processor : at91sam3s4 (Chip ID : 0x28a00960)
sourcing device file C:/Program Files (x86)/Atmel/sam-ba_2.12/sam-ba.exe/../tcl_lib/devices/at91sam3s4.tcl
sourcing board description file C:/Program Files (x86)/Atmel/sam-ba_2.12/sam-ba.exe/../tcl_lib/at91sam3s4-9x/at91sam3s4-9x.tcl
-I- Loading applet applet-lowlevelinit-atsam3s2.bin at address 0x20000800
-I- Memory Size : 0x0 bytes
-I- Buffer address : 0x4
-I- Buffer size: 0x0 bytes
-I- Applet initialization done
-I- Low level initialized
-I- Loading applet applet-flash-atsam3s2.bin at address 0x20000800
-I- Memory Size : 0x40000 bytes
-I- Buffer address : 0x20001440
-I- Buffer size: 0x6A00 bytes
-I- Applet initialization done
-I- FLASH initialized
-I- Command line mode : Execute script file : C:/Users/Wg/AppData/Local/Temp/temp.tcl
-I- SERIALFLASH::Init 0 (trace level : 4)
-I- Loading applet applet-serialflash-atsam3s2.bin at address 0x20000800
-I- Memory Size : 0x80000 bytes
-I- Buffer address : 0x20001E28
-I- Buffer size: 0x2000 bytes
-I- Applet initialization done
-I- Read File C:/Users/Wg/Desktop/Sky9x/kaos.bin at address 0x0
GENERIC::ReceiveFile C:/Users/Wg/Desktop/Sky9x/kaos.bin : 0x80000 bytes from address 0x0
-I- Complete 0%
-I- Reading: 0x2000 bytes at 0x0 (buffer addr : 0x20001E28)
-I- Complete 1%
-I- Reading: 0x2000 bytes at 0x2000 (buffer addr : 0x20001E28)
-E- No receive file name
-I- Complete 3%
-I- Reading: 0x2000 bytes at 0x4000 (buffer addr : 0x20001E28)
-I- Complete 4%
-I- Reading: 0x2000 bytes at 0x6000 (buffer addr : 0x20001E28)
-I- Complete 6%
-I- Reading: 0x2000 bytes at 0x8000 (buffer addr : 0x20001E28)
-I- Complete 7%
-I- Reading: 0x2000 bytes at 0xA000 (buffer addr : 0x20001E28)
-I- Complete 9%
-I- Reading: 0x2000 bytes at 0xC000 (buffer addr : 0x20001E28)
-I- Complete 10%
-I- Reading: 0x2000 bytes at 0xE000 (buffer addr : 0x20001E28)
-I- Complete 12%
-I- Reading: 0x2000 bytes at 0x10000 (buffer addr : 0x20001E28)
-I- Complete 14%
-I- Reading: 0x2000 bytes at 0x12000 (buffer addr : 0x20001E28)
-I- Complete 15%
-I- Reading: 0x2000 bytes at 0x14000 (buffer addr : 0x20001E28)
-I- Complete 17%
-I- Reading: 0x2000 bytes at 0x16000 (buffer addr : 0x20001E28)
-I- Complete 18%
-I- Reading: 0x2000 bytes at 0x18000 (buffer addr : 0x20001E28)
-I- Complete 20%
-I- Reading: 0x2000 bytes at 0x1A000 (buffer addr : 0x20001E28)
-I- Complete 21%
-I- Reading: 0x2000 bytes at 0x1C000 (buffer addr : 0x20001E28)
-I- Complete 23%
-I- Reading: 0x2000 bytes at 0x1E000 (buffer addr : 0x20001E28)
-I- Complete 25%
-I- Reading: 0x2000 bytes at 0x20000 (buffer addr : 0x20001E28)
-I- Complete 26%
-I- Reading: 0x2000 bytes at 0x22000 (buffer addr : 0x20001E28)
-I- Complete 28%
-I- Reading: 0x2000 bytes at 0x24000 (buffer addr : 0x20001E28)
-I- Complete 29%
-I- Reading: 0x2000 bytes at 0x26000 (buffer addr : 0x20001E28)
-I- Complete 31%
-I- Reading: 0x2000 bytes at 0x28000 (buffer addr : 0x20001E28)
-I- Complete 32%
-I- Reading: 0x2000 bytes at 0x2A000 (buffer addr : 0x20001E28)
-I- Complete 34%
-I- Reading: 0x2000 bytes at 0x2C000 (buffer addr : 0x20001E28)
-I- Complete 35%
-I- Reading: 0x2000 bytes at 0x2E000 (buffer addr : 0x20001E28)
-I- Complete 37%
-I- Reading: 0x2000 bytes at 0x30000 (buffer addr : 0x20001E28)
-I- Complete 39%
-I- Reading: 0x2000 bytes at 0x32000 (buffer addr : 0x20001E28)
-I- Complete 40%
-I- Reading: 0x2000 bytes at 0x34000 (buffer addr : 0x20001E28)
-I- Complete 42%
-I- Reading: 0x2000 bytes at 0x36000 (buffer addr : 0x20001E28)
-I- Complete 43%
-I- Reading: 0x2000 bytes at 0x38000 (buffer addr : 0x20001E28)
-I- Complete 45%
-I- Reading: 0x2000 bytes at 0x3A000 (buffer addr : 0x20001E28)
-I- Complete 46%
-I- Reading: 0x2000 bytes at 0x3C000 (buffer addr : 0x20001E28)
-I- Complete 48%
-I- Reading: 0x2000 bytes at 0x3E000 (buffer addr : 0x20001E28)
-I- Complete 50%
-I- Reading: 0x2000 bytes at 0x40000 (buffer addr : 0x20001E28)
-I- Complete 51%
-I- Reading: 0x2000 bytes at 0x42000 (buffer addr : 0x20001E28)
-I- Complete 53%
-I- Reading: 0x2000 bytes at 0x44000 (buffer addr : 0x20001E28)
-I- Complete 54%
-I- Reading: 0x2000 bytes at 0x46000 (buffer addr : 0x20001E28)
-I- Complete 56%
-I- Reading: 0x2000 bytes at 0x48000 (buffer addr : 0x20001E28)
-I- Complete 57%
-I- Reading: 0x2000 bytes at 0x4A000 (buffer addr : 0x20001E28)
-I- Complete 59%
-I- Reading: 0x2000 bytes at 0x4C000 (buffer addr : 0x20001E28)
-I- Complete 60%
-I- Reading: 0x2000 bytes at 0x4E000 (buffer addr : 0x20001E28)
-I- Complete 62%
-I- Reading: 0x2000 bytes at 0x50000 (buffer addr : 0x20001E28)
-I- Complete 64%
-I- Reading: 0x2000 bytes at 0x52000 (buffer addr : 0x20001E28)
-I- Complete 65%
-I- Reading: 0x2000 bytes at 0x54000 (buffer addr : 0x20001E28)
-I- Complete 67%
-I- Reading: 0x2000 bytes at 0x56000 (buffer addr : 0x20001E28)
-I- Complete 68%
-I- Reading: 0x2000 bytes at 0x58000 (buffer addr : 0x20001E28)
-I- Complete 70%
-I- Reading: 0x2000 bytes at 0x5A000 (buffer addr : 0x20001E28)
-I- Complete 71%
-I- Reading: 0x2000 bytes at 0x5C000 (buffer addr : 0x20001E28)
-I- Complete 73%
-I- Reading: 0x2000 bytes at 0x5E000 (buffer addr : 0x20001E28)
-I- Complete 75%
-I- Reading: 0x2000 bytes at 0x60000 (buffer addr : 0x20001E28)
-I- Complete 76%
-I- Reading: 0x2000 bytes at 0x62000 (buffer addr : 0x20001E28)
-I- Complete 78%
-I- Reading: 0x2000 bytes at 0x64000 (buffer addr : 0x20001E28)
-I- Complete 79%
-I- Reading: 0x2000 bytes at 0x66000 (buffer addr : 0x20001E28)
-I- Complete 81%
-I- Reading: 0x2000 bytes at 0x68000 (buffer addr : 0x20001E28)
-I- Complete 82%
-I- Reading: 0x2000 bytes at 0x6A000 (buffer addr : 0x20001E28)
-I- Complete 84%
-I- Reading: 0x2000 bytes at 0x6C000 (buffer addr : 0x20001E28)
-I- Complete 85%
-I- Reading: 0x2000 bytes at 0x6E000 (buffer addr : 0x20001E28)
-I- Complete 87%
-I- Reading: 0x2000 bytes at 0x70000 (buffer addr : 0x20001E28)
-I- Complete 89%
-I- Reading: 0x2000 bytes at 0x72000 (buffer addr : 0x20001E28)
-I- Complete 90%
-I- Reading: 0x2000 bytes at 0x74000 (buffer addr : 0x20001E28)
-I- Complete 92%
-I- Reading: 0x2000 bytes at 0x76000 (buffer addr : 0x20001E28)
-I- Complete 93%
-I- Reading: 0x2000 bytes at 0x78000 (buffer addr : 0x20001E28)
-I- Complete 95%
-I- Reading: 0x2000 bytes at 0x7A000 (buffer addr : 0x20001E28)
-I- Complete 96%
-I- Reading: 0x2000 bytes at 0x7C000 (buffer addr : 0x20001E28)
-I- Complete 98%
-I- Reading: 0x2000 bytes at 0x7E000 (buffer addr : 0x20001E28)

=================================================================================
SAM-BA done - exit code 1
=================================================================================

Could this be one of those sam-ba 2.12 problem? I have 2.12 loaded.