Feeling awkward posting so much but to solve my problems I did a clean of gcb and pk2/3 on win 7.
Thing work that didn't.
I clicked the gcb/pk2-3 gui installer...no extract,just opened installer and have their icons.
I connect pk2 and board and pic. connects but no device found.
I flash a prog to same from gcb fine...odd?
I tried pk3 (gcb version also) and it recognised the device but haven't used gcb to prog as no java/xlab.
Unlike win10 on win7 clicking pk3 icon and holding shift and ctrl then right click and then choose run as administrator flashed hex ok but then not closing error.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I reinstalled because of the error in picture. It was happening on unos not nanos.
Now it happening flash hex to nanos not unos. I'm using
REM Call AVRdude for Arduino_Uno bootloader:
REM You will have to confirm the com (communications) port - currently set for com6
"AVRdude\avrdude.exe" -c Arduino -P Com6 -b 115200 -p AT%2 -U flash:w:%1:i
Doing videos to explain would show problems if wanted.
I reinstalled gcb
Installing gcb pickit2 gui it doesn't find pic device on connnected board. other pc is ok.
The nanos give the stk500 error and now on other pc.
I'll reinstall again and leave pk2/3 alone.
The stk500 error going from uno to nano and then other way round is odd.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Reinstalled again. Same nano problem on a 3rd driving servos. stk500/crash. It's still is doing original program fine.
I think all 3 nanos are ok..they were.
I remember posting about this problem with uno/nano and think reinstall was recommended.
This is win7. I tried xloader to flash hex file to nano and that didn't work.
As I said it was a uno proplem. Now other way round.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My unos still work. It's the same avr tools script for both nano and uno. This is a problem. I have 2 other win pcs to try.
The point of a video was show same code flash to 2 unos then not flash 3 nanos.
Why stk500 error when not using it? Like using pk3 and when it ends says pk2 error, which is not explained.
I can't use nano with gcb,why?
Last edit: stan cartwright 2018-03-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Stan We have discussed this before. To summarise ... guessing the baud of the installed bootloader is not fun. Use AVRDUDES , from within the IDE, to determine the correct baud rate. When you have determined the correct baud rate setup the programme batch file. Essentially stop guessing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't realise stk500 was avrdude. I added this line and it flashes ok. Thanks for the baud rate tip. I googled it.
REM Call AVRdude for Arduino_Nano bootloader:
"AVRdude\avrdude.exe" -c Arduino -P Com7 -b 57600 -p AT%2 -U flash:w:%1:i
Odd it worked before. I have no idea how to use avrdude from within the idea.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I came to gcb from picaxe not arduino. Not a clue about arduino programming software.
The baud rate difference using nano with the uno avr tools line could be commented to help others like me. You have to do the same using arduino ide where I found the baud rate. https://www.avrfreaks.net/forum/programming-arduino-nano-avrdude
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No point... the new programming interface removes the programming batch file - I did send you pre-release version but that confused you also. So, before we have a circular conversation (I think this is already a recursive conversation) wait till the next release..... and, see this No point... the new programming interface removes the programming batch file - I did send you pre-release version but that confused you also. So, before we have a circular conversation (I think this is already a recursive conversation) wait till the next release..... and, see this https://sourceforge.net/p/gcbasic/discussion/579125/thread/ca88ae9e/#ec4d you were part of the this thread where Frank restated the bootloader baud rate.
That didn't explain why different unos have different com default...to me. I couldnt make win make them the same, I didn't have a nano then so the arduino baud rate was not a problem then just changeing com ports. so I'm recursing that niggle...again
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sometimes I get unknown device using nano/uno. It seems connecting usb when gcb open I get message but closing gcb and reconnecting, win finds usb arduino. Win is just os to me, a file launcher. error 64 means nothing.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Plug in nano, dedoop win sound as device inserted then error - unknown device....error 64...I think. I shall try to make it happen again and note conditions. As I said ,closed gcb then inserted usb lead and it worked ok. I don't know what win does/doesn't do with usb com ports. Win errors mean nothing to me.
I'll look it up on avr sites.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Feeling awkward posting so much but to solve my problems I did a clean of gcb and pk2/3 on win 7.
Thing work that didn't.
I clicked the gcb/pk2-3 gui installer...no extract,just opened installer and have their icons.
I connect pk2 and board and pic. connects but no device found.
I flash a prog to same from gcb fine...odd?
I tried pk3 (gcb version also) and it recognised the device but haven't used gcb to prog as no java/xlab.
Unlike win10 on win7 clicking pk3 icon and holding shift and ctrl then right click and then choose run as administrator flashed hex ok but then not closing error.
I reinstalled because of the error in picture. It was happening on unos not nanos.
Now it happening flash hex to nanos not unos. I'm using
REM Call AVRdude for Arduino_Uno bootloader:
REM You will have to confirm the com (communications) port - currently set for com6
"AVRdude\avrdude.exe" -c Arduino -P Com6 -b 115200 -p AT%2 -U flash:w:%1:i
What?
First post talks about Pickit and your second about AVR.
Which one is the best one to respond to?
Doing videos to explain would show problems if wanted.
I reinstalled gcb
Installing gcb pickit2 gui it doesn't find pic device on connnected board. other pc is ok.
The nanos give the stk500 error and now on other pc.
I'll reinstall again and leave pk2/3 alone.
The stk500 error going from uno to nano and then other way round is odd.
Please don't . I will post a training video. This is a lot easier.
Reinstalled again. Same nano problem on a 3rd driving servos. stk500/crash. It's still is doing original program fine.
I think all 3 nanos are ok..they were.
I remember posting about this problem with uno/nano and think reinstall was recommended.
This is win7. I tried xloader to flash hex file to nano and that didn't work.
As I said it was a uno proplem. Now other way round.
My unos still work. It's the same avr tools script for both nano and uno. This is a problem. I have 2 other win pcs to try.
The point of a video was show same code flash to 2 unos then not flash 3 nanos.
Why stk500 error when not using it? Like using pk3 and when it ends says pk2 error, which is not explained.
I can't use nano with gcb,why?
Last edit: stan cartwright 2018-03-06
Same nano stk500 error on win10 pc .gcb98.01.
@Stan We have discussed this before. To summarise ... guessing the baud of the installed bootloader is not fun. Use AVRDUDES , from within the IDE, to determine the correct baud rate. When you have determined the correct baud rate setup the programme batch file. Essentially stop guessing.
I didn't realise stk500 was avrdude. I added this line and it flashes ok. Thanks for the baud rate tip. I googled it.
REM Call AVRdude for Arduino_Nano bootloader:
"AVRdude\avrdude.exe" -c Arduino -P Com7 -b 57600 -p AT%2 -U flash:w:%1:i
Odd it worked before. I have no idea how to use avrdude from within the idea.
stk500 is not AVRDUDE. It is a programming interface.
Open up AVRDUDES is it a GUI interface to the command line interface AVRDUDE.
You will have a new interface to programming from the IDE very soon - it will be easier.
I came to gcb from picaxe not arduino. Not a clue about arduino programming software.
The baud rate difference using nano with the uno avr tools line could be commented to help others like me. You have to do the same using arduino ide where I found the baud rate.
https://www.avrfreaks.net/forum/programming-arduino-nano-avrdude
No point... the new programming interface removes the programming batch file - I did send you pre-release version but that confused you also. So, before we have a circular conversation (I think this is already a recursive conversation) wait till the next release..... and, see this No point... the new programming interface removes the programming batch file - I did send you pre-release version but that confused you also. So, before we have a circular conversation (I think this is already a recursive conversation) wait till the next release..... and, see this https://sourceforge.net/p/gcbasic/discussion/579125/thread/ca88ae9e/#ec4d you were part of the this thread where Frank restated the bootloader baud rate.
As with all recursion, recursive conversations can be fun and fustrating... also see https://sourceforge.net/p/gcbasic/discussion/579126/thread/399bd97e/#313f
Last edit: Anobium 2018-03-07
That didn't explain why different unos have different com default...to me. I couldnt make win make them the same, I didn't have a nano then so the arduino baud rate was not a problem then just changeing com ports. so I'm recursing that niggle...again
Sometimes I get unknown device using nano/uno. It seems connecting usb when gcb open I get message but closing gcb and reconnecting, win finds usb arduino. Win is just os to me, a file launcher. error 64 means nothing.
Don't understand. Error 64. Overload.
Plug in nano, dedoop win sound as device inserted then error - unknown device....error 64...I think. I shall try to make it happen again and note conditions. As I said ,closed gcb then inserted usb lead and it worked ok. I don't know what win does/doesn't do with usb com ports. Win errors mean nothing to me.
I'll look it up on avr sites.