I can get the tool to work on a 168 processor Ardupillot but not the 328 version of the Ardupilot.I have not yet managed to write a blank set of data to the EEPROM on the 328 and cannot read anything back either (I get the 'Something is Wrong' message on write and 'I can't read that' on read).Anyone had success using this utility?Any suggestions as to what I am doing wrong.regards Peterps I have selected the COM port!!!
You need to be a member of diydrones to add comments!
I recently ordered the Ardupilot board and shield. In anticipation of their arrival, I have been downloading all of the software and source code so I can dive in once the hardware arrives.
I have tried running the ArduPilot config tool but it instantly crashes when I try to run it, before any type of dialog window shows up. I am running XP Home SP3. Do I need any type of runtime library for it? Or do I simply need to have the hardware connected before I run the program? Anyone have this problem?
Hi Jordi,
Please forgive me for stepping in, I’m sooo a newbie to where you guys are at. But I do agree that some of the problems we’re experiencing is hardware to this extent.
The male headers that I received with the Ardupilot board are thin round pins. Then I ordered the shield kit, and followed the instructions to match the two boards.
What I found after allot of frustration was that if you take an ohm meter and measure through each header, some of them are not complete.
Looking at many of the pictures, the proper square pins for these female headers where being used. But now we’re using the round pins.
Everyone is going back and checking there code and erasing their memory and wondering if they set the correct PIC or not, but it can be as simple as a connection between these two boards.
Before I found the mismatch between the two boards, I could not upload through the FTDI, using any of four PC’s! But after finding the bad connections, I could upload the program and I can use the utility to set waypoints and read back. (The trick to using the utility process, was to hit the reset button just at the right time, don’t know why, but it work!), “mentioned in another post I read,” ALSO! You need to put in the LAT/ LON for “Home info”, or you can’t get the map to come in right. When it does, that is so cool.
The utility program, why you have to hit the reset button to make it work? I don’t know, but I’ll leave that to you guys to figure out. But I would highly recommend for everyone to check the connections between these two boards, (the header’s).
I’m 57, and what you guy’s are doing for the hobby that I’ve been in since I was a kid, is so neat. Please keep up the good work!
Is the source available anywhere? The program doesn't run under Mono which means anyone who doesn't use Windows can't use the latest ardupilot. I'm quite happy to re-write the program in something a bit more platform agnostic.
I can't find the source either on the google code downloads site or in the SVN repo.
Well I am the proud owner of two new Ardupilot 328 boards and a shield and I seem to have the same problem again on my new board - I cannot access the EEPROM using the Config Tool although my 168 board is fine..
I have done some further digging and used an AVR ISP programmer that I use to programme many different types of AVR chips and I get some odd results:
1. I try and read what is in the FlashROM and it appears to be empty (all FF's) although there was much activity from the LED's whilst the read is in progress. And this after I have just programmed it with version 2.2!
2. The Lockbits are set differently in the 328 to the 168 - bits 5,6 are 11 so making no restrictions for SPM or LPM accessing the bootloader section and bits 1,2 are 00 so making further programming and verification of the flash and EEPROM disabled in parallel and serial programming.
3. The bootsize on the 328 is set to 256words (1024words on the 168)
4. The reset vector is selected on the 328 whereas boot vector selected on the 168
5 There are also differences on the Brown out and clock frequency/type fuse bits
I am surprised at these differences especially the lock bits.
Can anyone help me or am I confused as to what is going on and this has nothing to do with my using the Config tool?
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.
Replies
I recently ordered the Ardupilot board and shield. In anticipation of their arrival, I have been downloading all of the software and source code so I can dive in once the hardware arrives.
I have tried running the ArduPilot config tool but it instantly crashes when I try to run it, before any type of dialog window shows up. I am running XP Home SP3. Do I need any type of runtime library for it? Or do I simply need to have the hardware connected before I run the program? Anyone have this problem?
Thanks,
James
Please forgive me for stepping in, I’m sooo a newbie to where you guys are at. But I do agree that some of the problems we’re experiencing is hardware to this extent.
The male headers that I received with the Ardupilot board are thin round pins. Then I ordered the shield kit, and followed the instructions to match the two boards.
What I found after allot of frustration was that if you take an ohm meter and measure through each header, some of them are not complete.
Looking at many of the pictures, the proper square pins for these female headers where being used. But now we’re using the round pins.
Everyone is going back and checking there code and erasing their memory and wondering if they set the correct PIC or not, but it can be as simple as a connection between these two boards.
Before I found the mismatch between the two boards, I could not upload through the FTDI, using any of four PC’s! But after finding the bad connections, I could upload the program and I can use the utility to set waypoints and read back. (The trick to using the utility process, was to hit the reset button just at the right time, don’t know why, but it work!), “mentioned in another post I read,” ALSO! You need to put in the LAT/ LON for “Home info”, or you can’t get the map to come in right. When it does, that is so cool.
The utility program, why you have to hit the reset button to make it work? I don’t know, but I’ll leave that to you guys to figure out. But I would highly recommend for everyone to check the connections between these two boards, (the header’s).
I’m 57, and what you guy’s are doing for the hobby that I’ve been in since I was a kid, is so neat. Please keep up the good work!
P.S. Anyone live in the Phoenix area?
Is the source available anywhere? The program doesn't run under Mono which means anyone who doesn't use Windows can't use the latest ardupilot. I'm quite happy to re-write the program in something a bit more platform agnostic.
I can't find the source either on the google code downloads site or in the SVN repo.
Cheers!
Mikil
I have done some further digging and used an AVR ISP programmer that I use to programme many different types of AVR chips and I get some odd results:
1. I try and read what is in the FlashROM and it appears to be empty (all FF's) although there was much activity from the LED's whilst the read is in progress. And this after I have just programmed it with version 2.2!
2. The Lockbits are set differently in the 328 to the 168 - bits 5,6 are 11 so making no restrictions for SPM or LPM accessing the bootloader section and bits 1,2 are 00 so making further programming and verification of the flash and EEPROM disabled in parallel and serial programming.
3. The bootsize on the 328 is set to 256words (1024words on the 168)
4. The reset vector is selected on the 328 whereas boot vector selected on the 168
5 There are also differences on the Brown out and clock frequency/type fuse bits
I am surprised at these differences especially the lock bits.
Can anyone help me or am I confused as to what is going on and this has nothing to do with my using the Config tool?
Should I try Andrew's method to wipe the EEPROM?
regards Peter
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.