Replies to This Discussion

Permalink Reply by Chris Anderson on May 10, 2009 at 8:19am

Works great for me. You are selecting the 328 board from the drop down menu, right?

• ▶ Reply

Permalink Reply by Peter Seddon on May 10, 2009 at 8:36am

Yep I am selecting 328.

I may have to attach the ISP connection and see what is in the EEPROM to make sure it is accessible.

Thanks for the response, Peter

• ▶ Reply

Permalink Reply by Peter Seddon on May 10, 2009 at 10:43am

Well I am totally confused. I can't read either the FlashROM or the EEPROM via the ISP port and the chip type reads back as Mega168 when I access the fusebits and lockbits on the 328 Ardupilot. The 168 board works as you would expect. .

I will have to investigate further!!

regards Peter

• ▶ Reply

Permalink Reply by Chris Anderson on May 10, 2009 at 11:22am

You're sure this is the red board and the chip says ATMega328P on it?

• ▶ Reply

Permalink Reply by Peter Seddon on May 10, 2009 at 12:33pm

Yes to both questions.

I think there must be a chip problem - I can read the ATtiny as expected.

I've had a look at the board under an eyeglass and can't see anything obviously wrong.

Sadly I can't find a source in the UK for 328P so it is back to Sparkfun.

regards Peter

• ▶ Reply

Permalink Reply by Andrew Wong on May 18, 2009 at 7:54pm

I am having similar trouble. I have 2.1.1 on the Ardupilot (328) and the arduino IDE is able to read and write to the board without problem. I have selected 328 from the drop down menu and the correct COM port. I get the something is wrong error when writing and the I can't read error when reading.

By the way, my GPS LED is blinking in 2.1.1 and I'm not getting any data from the GPS (all the navigation values are 0). However, the FMA sensors are reporting data.

• ▶ Reply

Permalink Reply by Andrew Wong on May 18, 2009 at 9:11pm

I resolved the GPS issue. From my not-so-technical investigation, 2.1 does not program the GPS into binary mode. I downloaded 2.0.1 and got the GPS working there. Then I upgraded to 2.1 and the GPS worked.

I'm still lost on the Config tool part of this whole process. It still does not seem to work for me.

• ▶ Reply

Permalink Reply by Peter Seddon on May 19, 2009 at 2:33am

The GPS gets put into Binary mode by shorting pins D6 and D7 before applying power and then removing the link when the initial activity has completed - there is a post about this somewhere.

Regarding your problem with the Config Tool, it is worth trying it after having just switched your PC on as the COM port may be being grabbed by some other application preventing the Config Tool from accessing the port.

Peter

• ▶ Reply

Permalink Reply by Andrew Wong on May 19, 2009 at 12:12pm

Still no dice after rebooting. I don't think the com port is being grabbed by another program because i can see the red and green tx and rx lights light up for a split second (on the FTDI board) then the board blinks green for another second before the program gives me a "Something is wrong" error message.

I will try the utility on another computer just to make sure it isn't a problem with my laptop.

• ▶ Reply

Permalink Reply by Andrew Wong on May 19, 2009 at 2:45pm

Just tried on another computer and still no luck. Is there anyone besides Chris and Jordi who has this program working?

• ▶ Reply

Permalink Reply by Chris Anderson on May 19, 2009 at 8:01pm

Andrew, I think the problem is that you've got bad data in the EEPROM and the utility is choking on it. If you don't write first before doing anything else with the utility (yes, that's clumsy--we're fixing it) you may encounter the problem you're seeing.

Jordi is planning to add an "Erase EEPROM" button on the next version that will avoid this problem.

Most people are using this utility fine; I'm sorry that you've had a problem. In the meantime, you can downgrade to 2.0.1 and enter the config details manually.

• ▶ Reply

Permalink Reply by Andrew Wong on May 19, 2009 at 8:42pm

Just sent you a message about that.

On a side note: reading works.

I read the instructions on clicking write immediately after connecting the board, but I was unable to successfully write to the eeprom.

I would prefer not to downgrade to 2.0.1 because I have my FMA sensor glued in diagonally. I just looked up the command needed to erase the eeprom, but as of 4/19, the config utility is still closed source :(. Maybe I'll try to write up something myself and fry the brains out of my board (Yay!).

• ▶ Reply

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page