Hi,
I want do my little part for the success of the new Release for Great Cow.
For the new Homepage I collect FAQ entries.
Of course you had suffered from Compiler Messages and Errors yourself where you had searching for the reason only to find it was so simply if only you had known before the Reason.
I give an example what I mean
(Please keep in mind, English is not my Motherlanguages so be so kind and correct any txpos as well)
Q. What is good practice in terms of the Windows instaltion folder?
A. The default for a Full IDE package is C:\GCB@SYN but you could consister C:\GCB@SYN[GCB Version] such as C:\GCB@SYN\V0_98_00 and when you upgrade such as C:\GCB@SYN\V0_99_00
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes if enough suggestions coming in, sorting it in Categogies are very fine. Most people are using search anyway.
So far I do have only 2 Q: any more, folks?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q. What version of Windows is supported?
A. All versions from Windows XP have been proven to operate as expected. Issues have been seen with industrial Windows XP.
Q. What distribution of Linux is supported?
A. {someone answer!}
Q. What version of .NET is required for Great Cow Graphical BASIC?
A. Windows versions have the pre-requisite of .NET 3.5.
Q. What Apple OS Windows emulators are supported?
A. ???
Q. What Inux OS Windows emulators are supported?
A. ???
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q. How do change my IDE installation to ....
A. Make my fonts larger.....
A. Make the Help NOT go to full screen....
A. [add more IDE hints and tip]....
Last edit: Anobium 2017-09-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q. The compiler locks up when compiler.
A. If you are using Windows kill the gcbasic.exe, then, examine your source code and locate the source of the lock-up (may need to edit your source code) - then, report the errot cause to the Great Cow BASIC forum.
Q. What is the compiler? The Great Cow BASIC compiler converts your source code to assembler for your specific chip. The Great Cow BASIC compiler is the digitisation of the combined knowldge of the Great Cow BASIC community - this core capabilty is the insights of assember for the chip architecture, the core support libraries and the accessory library.
The Great Cow BASIC compiler is wrriten in Freebasic.
Last edit: Anobium 2017-09-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q: I used "On Interrupt PortBChange call My_Interrupt_handle" But the Interrupt Routine will never be triggered
A: Look at your used Chip, i. E. for PIC18F25K22 only PortB.4 -> PortB.7 are useable for Interrupting due changing in state. Using other Ports will never trigger
Did You enable Interrupt with IOCB4 -> IOCB7 ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q: I an trying to use "On Interrupt PortBChange Call My_Interrupt_Handler" but, the Interrupt Routine (My_Interrupt_Handler) is not triggered, Why?
A: Look at the datasheet for the specific microcontroller, i. e. a PIC18F25K22, look for the 'Interrupt-On-Change' (IOC) specification. The PIC18F25K22 shows PortB.4 to PortB.7 are useable for IOC. Therefore, you must use PortB.4 to PortB.7 for IOC all the other ports will never trigger the interrupt.
So, in your user code you must set the Interrupt with IOCB4 to IOCB7, as shows below:
Set IOCB4 On
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q:Is there an IDE for Linux?
A: Are here any Linux users?
I am using Geany, with a little config it is really well suited, while not in the same class as the excellent GCB@SYN
I the forums there are some older threads about Linux IDE, but how is the state in 2017?
Last edit: bed 2017-09-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q:What are the requirements for Linux for installing and using Great Cow Basic?
AYou need a recent Linux (32 or 64 Bit System) installed on a not too old Computer. FreeBASIC 1.05 or newer must be installed (because the Great Cow Basic Compiler will be build with it) rar or unrar for unpacking the Source and rsync is used by install script.
Last edit: bed 2017-09-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A1: When an '#IfDef' statement is set, it is important that the 'Then' word is not included as part of the statement or the Define will not be correctly interpreted.
I don't use linux...except rpi because I have to :)
Sometimes my programming errors make the win GCB stop working and windows asks to shut down program. but that's known...a feature..don't write duff code :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q I am compiling my code and the process is not completing. What processes do I need to kill?
A ( we need answers for Windows and Linux)
Q My code keeps locking up the compiler. What do I do as I cannot see why?
A Take a copy of your and try to isolate the issue. Remove code until you have the essence of the issue. Then, post a question to the Forum... you may have discovered a bug.
A UPGRADE to latest version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
not a gcb problem
Q. Why does my Pickit3 not recognise my chip?
not a gcb problem
Q. What are the programmer Great Cow BASIC supports?
pk2 from the ide or avr via usb and bootloader .that comes if you use uno board.
I don't know about just a 328p chip and flashing like pic icp.
pk3 needs microchip files and java with gcb and it's hassle.
Q. What is the best programmer?
arduino doesn't need one. Fake pk2,3 depending on pic works fine for me. I don't want to use mplab.
Q. What is a good chip to choose?
welcher schlüssel ist am besten? :) For hobbyist a 328p or pic equivalent but ott for flashing a led.
Q. How do I setup my programmer?
A copy of microchip in circuit progammer how to would be useful as I had to search for it.
Q. What is the minimum setup in my lab to get started?
cheap pc/laptop win 7,10 and programmer and micro controller on a board to program and run (or use zif socket board).....then solder station,tools,oscilloscope,angle poise lamp with magnifier, lots of free time.
many questions,many answers. A beginners hard ware programming guide using GCB anyone? It's taken for granted that a user would have that sorted before using GCB but I started with a uno so no problem.
If I was using several pics then a universal board would be nice else use a zif socket board that pickit plugs into then a board to test. I'm thinking low cost solutions.
Hope no one minds my comments.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is my hack at the answers. Please feel free to correct/edit etc.
Q. Why does my Pickit2 not recognise my chip when I use the Windows Application or the command line utilties?
Let us assume you have the microcontroller attached to the PicKit2.
A. The PicKit2 may not recognised you microcontroller because of:
1. Microchip not longer provides support for the PicKit2 programmer.
2. Microchip not longer provides support for the PicKit2 Windows Application and the command line utilities - the source code has been published by Microchip.
3. The supporting microcontroller devicefile database for the PicKit2 is no longer supported by Microchip. The full list of Microchip Pickit2 microcontrollers can be found in the PICkit 2 Programmer/Debugger Readme File.
4. The internal architecture of some of the Microchip microcontrollers released since 2009 require a PicKit3 and the use of MPLAB-IPE (see the FAQ on MPAB-IPE).
However, all is not lost when using a PicKit2 - but, if your selected Microchip microcontroller needs a PicKit3... go get one.
The Great Cow BASIC team, specificially Bill Roth, has updated the the supporting microcontroller database using the PICkit2 Devicefile Editor. The Great Cow BASIC updated PICkit2 microcontroller devicefile database now supports a wider range and some of the newer microcontrollers. However, there are microcontrollers that are not supported by the updated PICkit2 microcontroller devicefile database and you will need a Pickit3 for these chips.
The Great Cow BASIC team also have included in the distribution an updated version of PicKit2 which includes an updated microcontroller devicefile database.
The PICkit2 Devicefile Editor is a also included in the distribution so, you can adapt the microcontroller devicefile database to meet you own needs.
Summary
The PicKit2 supports a wider range of microcontrollers when updated with the Great Cow BASIC microcontroller devicefile database (see your installation folders) and the constraints of the microcontroller internal architecture may mean you need a PicKit3 with the PicKit3 Windows Application or a PicKi3 using MPLAB-IPE.
The PicKit2 software is included in your installlation with the supporting scripts.
Q. Why does my Pickit3 not recognise my chip when I use the Windows Application or the command line utilties?
Let us assume you have the microcontroller attached to the PicKit2.
A. The PicKit3 may not recognised you microcontroller because of:
1. Microchip not longer provides support for the PicKit3 Windows Application and the command line utilities - the source code has been published by Microchip.
2. The supporting microcontroller devicefile database for the PicKit3 is no longer supported by Microchip. The full list of Microchip Pickit2 microcontrollers can be found in the PICkit 3 Programmer/Debugger Readme File.
3. The internal architecture of some of the Microchip microcontrollers released since 2009 require a PicKit3 and will be required to use MPLAB-IPE.
However, all is not lost when using a PicKit3.
The Great Cow BASIC team, specificially Bill Roth, has updated the the supporting microcontroller database using the PICkit2 Devicefile Editor. The Great Cow BASIC updated PICkit2 microcontroller devicefile database now supports a wider range and some of the newer microcontrollers. The PICkit2 microcontroller devicefile database is the same database for the PicKit3! Result.
The Great Cow BASIC team also have included in the distribution an updated version of PicKit3 which includes an updated microcontroller devicefile database.
The PICkit2 Devicefile Editor is a also included in the distribution so, you can adapt the microcontroller devicefile database to meet you own needs.
Summary
The PicKit3 supports a wide of microcontrollers when updated with the Great Cow BASIC microcontroller devicefile database (see your installation folders) and the constraints of the microcontroller internal architecture may mean you need a PicKit3 and MPLAB-IPE
The PicKit2 software is included in your installlation with the supporting scripts.
Q. What is MPLAB-IPE?
A. MPLAB Integrated Programming Environment (IPE) is a software application that provides a simple interface to program a Microchip microcontroller. MPLAB-IPE uses the MDB (Microchip Debugger) Core and MPLAB X IDE framework to provide all the programming capabilities for all Microchip programmers. It essentialy is the latest programmer from Microchip.
MPLAB-IPE is a fully supported application from Microchip. It supports the following programming hardware.
You WILL need to use MPLAB-IPE for many of the latest Microchip Microcontrollers. You currently no choice [needs validation] as the latest Microchip Microcontrollers use programming scripts (within the programming hardware a PicKit3 for instance) and we are unable to codify these scripts in the PICkit2 Devicefile Editor (see PicKit2 and PicKit3 faqs).
Q. What are the programmer Great Cow BASIC supports?
A. Great Cow BASIC support any programmer as Great Cow BASIC produces a HEX file that any programmer should be able to use but Included in the installation are the following applications to support programming a microcontroller.
1. Pickit2 command line utility - integrated into the IDE supporting scripts with an updated microcontroller devicefile database.
2. Pickit2 Windows GUI. A complete installation of the PicKit2 with an updated microcontroller devicefile database. You can use the . Pickit2 Windows GUI directly from this folder.
3. Pickit2 Windows Installation Package. The installation folders includes an updated microcontroller devicefile database but you must manually copy the microcontroller devicefile database to your installation folders.
4. Pickit3 Windows Installation Package. The installation folders includes an updated microcontroller devicefile database but you must manually copy the microcontroller devicefile database to your installation folders.
5. AVRDude and AVRDudess. An Open Source programmer and Windows GUI application to programmer AVR microcontrollers.
6. WinPICPgm. The WinPICPgm Development Programmer Software is a free and simple In-System-Development Programmer Software for the Microchip PIC microcontrollers. The programmer software is available with a Graphical User Interface (GUI) and a Command Line interface
7. Microchip XPressLoader. A simple command line utility to support the Microchip Xpress Board.
8. TinyBootLoader+. An Open Source programmer and Windows GUI application to programmer Microchip and AVR microcontrollers. This a specific release for Great Cow BASIC and the Great Cow BASIC have developed bootloaders for many microcontrollers - this is a great option to reduce a dependency on MPLAB-IPE.
9. Micronucleus. A command line utility to support the Micronucleus range of AVR products.
pk2 from the ide or avr via usb and bootloader .that comes if you use uno board.
I don't know about just a 328p chip and flashing like pic icp.
pk3 needs microchip files and java with gcb and it's hassle.
Q. What is the best programmer?
A. Depends on your selected microcontroller type and the microcontroller architecture.
This list is a summary as there are lots of options, this list is not extensive and is not intended to be complete - but, beware..... if you use a Microchip microcontroller released after 2009 it is highly likely that your choice is ONLY a PicKit3.
Microchip and AVR (yes, you can program an AVR with a Microchip type programmer.. how did they get the AVR bootloader onto the AVR microcontroller in the first place)
1. PicKit2 - and the 100's of excellent clones
1. PicKit3 - and the 100's of excellent clones
1. PICPgm USB Programmer
1. PICPgm LVISP Programme
1. JDM Programmer
1. Tait Classic PIC Programmer
1. Olimex PIC-PG2 (JDM based)
1. Olimex PIC-PG3 (28pin, 40pin)
1. Velleman-Kit K8048
1. El Cheapo PICmicro Programmer
1. Microchip AN589 Programmer
1. FT232Adapter-Programme
1. GPIO Programmer (Raspberry Pi)
1. And, many more....
Remember. Lots and lots of AVR devices come with a bootloader. You do not need a programmer typically for these devices you just need a serial port.
arduino doesn't need one. Fake pk2,3 depending on pic works fine for me. I don't want to use mplab.
Q. What is a good chip to choose? welcher schlüssel ist am besten? :)
For hobbyist a Atmel AVR 328p/Ardunio UNO or pic a Microchip PIC18F2520 but for flashing an LED try the AVR Micronucleus board or a Microchip Xpress board.
Q. How do I setup my programmer?
A copy of microchip in circuit progammer how to would be useful as I had to search for it.
This is a wide ranging question. The sheer number of programmers available make this question very hard to answer.
Advice - if you are struggling and after 15 minutes you are not programming using a PicKit post the Great Cow BASIC forum.
Q. What is the minimum setup in my lab to get started?
A. A computer with Windows 7 or greater. A programmer and microcontroller on a board to program and run (or use zif socket board).....then, add a solder station, tools, oscilloscope, angle poise lamp with magnifier and lots of free time.
many questions,many answers. A beginners hard ware programming guide using GCB anyone? It's taken for granted that a user would have that sorted before using GCB but I started with a uno so no problem.
If I was using several pics then a universal board would be nice else use a zif socket board that pickit plugs into then a board to test. I'm thinking low cost solutions.
Hope no one minds my comments.
Last edit: Anobium 2017-09-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A lot of corrections to Stan's posting.
This is my hack at the answers. Please feel free to correct/edit etc.
(a lot of knoledge, hints and Wisdom appears)
I will this put in a own sub page, so much Text destroys a FAQ.
It's better placed in a knoledge DB or so.
Last edit: bed 2017-09-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A. In most cases, this is not a problem of the programmer software, but, a problem of the programmer hardware or the connection to the microcontroller.
Some hints, tips and tricks which can be used for troubleshooting such problems.
• Check all Vdd (supply voltage) and Vss (0v) pins of the microcontroller have to be connected to the corresponding power supply pins.
• Each Vdd pin should be connected to a decoupling capacitor, i.e. a capacitor between Vdd and VSS. The capacitor shall be placed as close as possible to the Vdd pin. A typical value for a decoupling capacitor is 100nF.
• For Low-Voltage programmers, make sure that the PGM pin of the microcontroller is tied to ground via a pull-down resistor (~10k).
• For High-Voltage programming, it also might be necessary to connect the PGM pin to GND. So if programming fails, try to connect the PGM pin to ground via a 10k resistor.
• Microcontrollers that can be programmed either in High-Voltage or Low-Voltage mode may make problems during programming in High-Voltage mode if the LVP bit (Low Voltage ICSP Enable bit) in the configuration memory is enabled. Also, if you program a microcontroller the first time, the LVP bit (Low Voltage ICSP Enable bit) in configuration memory is set, i.e. LVP enabled. Issues also happen when using the MCLR pin is used as Input I/O pin.
If the LVP configuration fuse is enabled, PGM should be held low to prevent inadvertent entry into LVP mode.
• If you are using a High-Voltage programmer, make sure that the programming voltage on MCLR pin is within the voltage thresholds specified in the programming specification of the microcontroller to be programmed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Q: Where can I see how big my Program is, how much memory/eeprom/ RAM it uses etc.
A: Easy: look at the Compilation Report in your current project folder. The File with the html extension is what you searching for.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I want do my little part for the success of the new Release for Great Cow.
For the new Homepage I collect FAQ entries.
Of course you had suffered from Compiler Messages and Errors yourself where you had searching for the reason only to find it was so simply if only you had known before the Reason.
I give an example what I mean
(Please keep in mind, English is not my Motherlanguages so be so kind and correct any txpos as well)
Typical Errors
Q: foobar.gcb (nn): Error: Invalid variable name: 0THEN:
A: carefully search downwards for missing end if, the Error line nn is not the real Reason!
If you have such things for me, please post it here.
I'll collect them and fill the new FAQ for the new Homepage.
Thank You
What a good idea.
We could categorise as follows - please revise/discuss as you please
Q. What is good practice in terms of the Windows instaltion folder?
A. The default for a Full IDE package is C:\GCB@SYN but you could consister C:\GCB@SYN[GCB Version] such as C:\GCB@SYN\V0_98_00 and when you upgrade such as C:\GCB@SYN\V0_99_00
Yes if enough suggestions coming in, sorting it in Categogies are very fine. Most people are using search anyway.
So far I do have only 2 Q: any more, folks?
Q. What version of Windows is supported?
A. All versions from Windows XP have been proven to operate as expected. Issues have been seen with industrial Windows XP.
Q. What distribution of Linux is supported?
A. {someone answer!}
Q. What version of .NET is required for Great Cow Graphical BASIC?
A. Windows versions have the pre-requisite of .NET 3.5.
Q. What Apple OS Windows emulators are supported?
A. ???
Q. What Inux OS Windows emulators are supported?
A. ???
Configuration
Q. How do change my IDE installation to ....
A. Make my fonts larger.....
A. Make the Help NOT go to full screen....
A. [add more IDE hints and tip]....
Last edit: Anobium 2017-09-20
Compiling
Q. The compiler locks up when compiler.
A. If you are using Windows kill the gcbasic.exe, then, examine your source code and locate the source of the lock-up (may need to edit your source code) - then, report the errot cause to the Great Cow BASIC forum.
Q. What is the compiler? The Great Cow BASIC compiler converts your source code to assembler for your specific chip. The Great Cow BASIC compiler is the digitisation of the combined knowldge of the Great Cow BASIC community - this core capabilty is the insights of assember for the chip architecture, the core support libraries and the accessory library.
The Great Cow BASIC compiler is wrriten in Freebasic.
Last edit: Anobium 2017-09-20
Q: I used "On Interrupt PortBChange call My_Interrupt_handle" But the Interrupt Routine will never be triggered
A: Look at your used Chip, i. E. for PIC18F25K22 only PortB.4 -> PortB.7 are useable for Interrupting due changing in state. Using other Ports will never trigger
Did You enable Interrupt with IOCB4 -> IOCB7 ?
Improved
Q: I an trying to use "On Interrupt PortBChange Call My_Interrupt_Handler" but, the Interrupt Routine (My_Interrupt_Handler) is not triggered, Why?
A: Look at the datasheet for the specific microcontroller, i. e. a PIC18F25K22, look for the 'Interrupt-On-Change' (IOC) specification. The PIC18F25K22 shows PortB.4 to PortB.7 are useable for IOC. Therefore, you must use PortB.4 to PortB.7 for IOC all the other ports will never trigger the interrupt.
So, in your user code you must set the Interrupt with IOCB4 to IOCB7, as shows below:
Set IOCB4 OnThanx, I update the Faq from time to time.
Q:Is there an IDE for Linux?
A: Are here any Linux users?
I am using Geany, with a little config it is really well suited, while not in the same class as the excellent GCB@SYN
I the forums there are some older threads about Linux IDE, but how is the state in 2017?
Last edit: bed 2017-09-21
Q:What are the requirements for Linux for installing and using Great Cow Basic?
AYou need a recent Linux (32 or 64 Bit System) installed on a not too old Computer. FreeBASIC 1.05 or newer must be installed (because the Great Cow Basic Compiler will be build with it) rar or unrar for unpacking the Source and rsync is used by install script.
Last edit: bed 2017-09-22
I'm in daubt shall I integrate http://gcbasic.sourceforge.net/help/_frequently_asked_questions.html
in the new Homepage, or shall I take over a short form of Qestions and link for detailed Answers to http://gcbasic.sourceforge.net/help/_frequently_asked_questions.html
?
Are there other Forum users reading this? How is your opinon?
Q: Why does my #IfDef Define not work?
A1: When an '#IfDef' statement is set, it is important that the 'Then' word is not included as part of the statement or the Define will not be correctly interpreted.
This should work:
This won't work:
[The #Define is misinterpreted as: #IfDef MyDefinitionthen]
A2. It seems not to be possible to encase an entire SubRoutine (or SubRoutines) within an '#IfDef' statement.
This should work:
This won't work:
[The SubRoutine seems never to compile]
@mkstevo, thanks!
@all: more cool Q&A please. I'll update the prelive Homepage nearly daily with the results of this Thread
I don't use linux...except rpi because I have to :)
Sometimes my programming errors make the win GCB stop working and windows asks to shut down program. but that's known...a feature..don't write duff code :)
If we examine Stan's post there is gold.
Q I am compiling my code and the process is not completing. What processes do I need to kill?
A ( we need answers for Windows and Linux)
Q My code keeps locking up the compiler. What do I do as I cannot see why?
A Take a copy of your and try to isolate the issue. Remove code until you have the essence of the issue. Then, post a question to the Forum... you may have discovered a bug.
A UPGRADE to latest version.
Here again some Qs
* Q. Why does my Pickit2 not recognise my chip?
Q. Why does my Pickit3 not recognise my chip?
Q. What are the programmer Great Cow BASIC supports?
Q. What is the best programmer?
Q. What is a good chip to choose?
Q. How do I setup my programmer?
Q. What is the minimum setup in my lab to get started?
(Out from a chat)
Who has a Answer, pleas repeat the Q also.
I'm think for a first FAQ I have enough input, then
But don't hesitate to post further.
Q. Why does my Pickit3 not recognise my chip?
not a gcb problem
Q. What are the programmer Great Cow BASIC supports?
pk2 from the ide or avr via usb and bootloader .that comes if you use uno board.
I don't know about just a 328p chip and flashing like pic icp.
pk3 needs microchip files and java with gcb and it's hassle.
Q. What is the best programmer?
arduino doesn't need one. Fake pk2,3 depending on pic works fine for me. I don't want to use mplab.
Q. What is a good chip to choose?
welcher schlüssel ist am besten? :) For hobbyist a 328p or pic equivalent but ott for flashing a led.
Q. How do I setup my programmer?
A copy of microchip in circuit progammer how to would be useful as I had to search for it.
Q. What is the minimum setup in my lab to get started?
cheap pc/laptop win 7,10 and programmer and micro controller on a board to program and run (or use zif socket board).....then solder station,tools,oscilloscope,angle poise lamp with magnifier, lots of free time.
many questions,many answers. A beginners hard ware programming guide using GCB anyone? It's taken for granted that a user would have that sorted before using GCB but I started with a uno so no problem.
If I was using several pics then a universal board would be nice else use a zif socket board that pickit plugs into then a board to test. I'm thinking low cost solutions.
Hope no one minds my comments.
A lot of corrections to Stan's posting.
This is my hack at the answers. Please feel free to correct/edit etc.
Q. Why does my Pickit2 not recognise my chip when I use the Windows Application or the command line utilties?
Let us assume you have the microcontroller attached to the PicKit2.
A. The PicKit2 may not recognised you microcontroller because of:
1. Microchip not longer provides support for the PicKit2 programmer.
2. Microchip not longer provides support for the PicKit2 Windows Application and the command line utilities - the source code has been published by Microchip.
3. The supporting microcontroller devicefile database for the PicKit2 is no longer supported by Microchip. The full list of Microchip Pickit2 microcontrollers can be found in the PICkit 2 Programmer/Debugger Readme File.
4. The internal architecture of some of the Microchip microcontrollers released since 2009 require a PicKit3 and the use of MPLAB-IPE (see the FAQ on MPAB-IPE).
However, all is not lost when using a PicKit2 - but, if your selected Microchip microcontroller needs a PicKit3... go get one.
The Great Cow BASIC team, specificially Bill Roth, has updated the the supporting microcontroller database using the PICkit2 Devicefile Editor. The Great Cow BASIC updated PICkit2 microcontroller devicefile database now supports a wider range and some of the newer microcontrollers. However, there are microcontrollers that are not supported by the updated PICkit2 microcontroller devicefile database and you will need a Pickit3 for these chips.
The Great Cow BASIC team also have included in the distribution an updated version of PicKit2 which includes an updated microcontroller devicefile database.
The PICkit2 Devicefile Editor is a also included in the distribution so, you can adapt the microcontroller devicefile database to meet you own needs.
Summary
The PicKit2 supports a wider range of microcontrollers when updated with the Great Cow BASIC microcontroller devicefile database (see your installation folders) and the constraints of the microcontroller internal architecture may mean you need a PicKit3 with the PicKit3 Windows Application or a PicKi3 using MPLAB-IPE.
The PicKit2 software is included in your installlation with the supporting scripts.
Q. Why does my Pickit3 not recognise my chip when I use the Windows Application or the command line utilties?
Let us assume you have the microcontroller attached to the PicKit2.
A. The PicKit3 may not recognised you microcontroller because of:
1. Microchip not longer provides support for the PicKit3 Windows Application and the command line utilities - the source code has been published by Microchip.
2. The supporting microcontroller devicefile database for the PicKit3 is no longer supported by Microchip. The full list of Microchip Pickit2 microcontrollers can be found in the PICkit 3 Programmer/Debugger Readme File.
3. The internal architecture of some of the Microchip microcontrollers released since 2009 require a PicKit3 and will be required to use MPLAB-IPE.
However, all is not lost when using a PicKit3.
The Great Cow BASIC team, specificially Bill Roth, has updated the the supporting microcontroller database using the PICkit2 Devicefile Editor. The Great Cow BASIC updated PICkit2 microcontroller devicefile database now supports a wider range and some of the newer microcontrollers. The PICkit2 microcontroller devicefile database is the same database for the PicKit3! Result.
The Great Cow BASIC team also have included in the distribution an updated version of PicKit3 which includes an updated microcontroller devicefile database.
The PICkit2 Devicefile Editor is a also included in the distribution so, you can adapt the microcontroller devicefile database to meet you own needs.
Summary
The PicKit3 supports a wide of microcontrollers when updated with the Great Cow BASIC microcontroller devicefile database (see your installation folders) and the constraints of the microcontroller internal architecture may mean you need a PicKit3 and MPLAB-IPE
The PicKit2 software is included in your installlation with the supporting scripts.
Q. What is MPLAB-IPE?
A. MPLAB Integrated Programming Environment (IPE) is a software application that provides a simple interface to program a Microchip microcontroller. MPLAB-IPE uses the MDB (Microchip Debugger) Core and MPLAB X IDE framework to provide all the programming capabilities for all Microchip programmers. It essentialy is the latest programmer from Microchip.
MPLAB-IPE is a fully supported application from Microchip. It supports the following programming hardware.
• MPLAB ICD 3 In-Circuit Debugger
• MPLAB PICkit2 Debugger/Programmer
• MPLAB PICkit3 Debugger/Programmer
• MPLAB PM3 Programmer
• MPLAB REAL ICE Emulator
• Licensed PKOB Starter Kits
You WILL need to use MPLAB-IPE for many of the latest Microchip Microcontrollers. You currently no choice [needs validation] as the latest Microchip Microcontrollers use programming scripts (within the programming hardware a PicKit3 for instance) and we are unable to codify these scripts in the PICkit2 Devicefile Editor (see PicKit2 and PicKit3 faqs).
Q. What are the programmer Great Cow BASIC supports?
A. Great Cow BASIC support any programmer as Great Cow BASIC produces a HEX file that any programmer should be able to use but Included in the installation are the following applications to support programming a microcontroller.
1. Pickit2 command line utility - integrated into the IDE supporting scripts with an updated microcontroller devicefile database.
2. Pickit2 Windows GUI. A complete installation of the PicKit2 with an updated microcontroller devicefile database. You can use the . Pickit2 Windows GUI directly from this folder.
3. Pickit2 Windows Installation Package. The installation folders includes an updated microcontroller devicefile database but you must manually copy the microcontroller devicefile database to your installation folders.
4. Pickit3 Windows Installation Package. The installation folders includes an updated microcontroller devicefile database but you must manually copy the microcontroller devicefile database to your installation folders.
5. AVRDude and AVRDudess. An Open Source programmer and Windows GUI application to programmer AVR microcontrollers.
6. WinPICPgm. The WinPICPgm Development Programmer Software is a free and simple In-System-Development Programmer Software for the Microchip PIC microcontrollers. The programmer software is available with a Graphical User Interface (GUI) and a Command Line interface
7. Microchip XPressLoader. A simple command line utility to support the Microchip Xpress Board.
8. TinyBootLoader+. An Open Source programmer and Windows GUI application to programmer Microchip and AVR microcontrollers. This a specific release for Great Cow BASIC and the Great Cow BASIC have developed bootloaders for many microcontrollers - this is a great option to reduce a dependency on MPLAB-IPE.
9. Micronucleus. A command line utility to support the Micronucleus range of AVR products.
pk2 from the ide or avr via usb and bootloader .that comes if you use uno board.I don't know about just a 328p chip and flashing like pic icp.
pk3 needs microchip files and java with gcb and it's hassle.
Q. What is the best programmer?
A. Depends on your selected microcontroller type and the microcontroller architecture.
This list is a summary as there are lots of options, this list is not extensive and is not intended to be complete - but, beware..... if you use a Microchip microcontroller released after 2009 it is highly likely that your choice is ONLY a PicKit3.
Microchip and AVR (yes, you can program an AVR with a Microchip type programmer.. how did they get the AVR bootloader onto the AVR microcontroller in the first place)
1. PicKit2 - and the 100's of excellent clones
1. PicKit3 - and the 100's of excellent clones
1. PICPgm USB Programmer
1. PICPgm LVISP Programme
1. JDM Programmer
1. Tait Classic PIC Programmer
1. Olimex PIC-PG2 (JDM based)
1. Olimex PIC-PG3 (28pin, 40pin)
1. Velleman-Kit K8048
1. El Cheapo PICmicro Programmer
1. Microchip AN589 Programmer
1. FT232Adapter-Programme
1. GPIO Programmer (Raspberry Pi)
1. And, many more....
Remember. Lots and lots of AVR devices come with a bootloader. You do not need a programmer typically for these devices you just need a serial port.
arduino doesn't need one. Fake pk2,3 depending on pic works fine for me. I don't want to use mplab.Q. What is a good chip to choose?
welcher schlüssel ist am besten? :)For hobbyist a Atmel AVR 328p/Ardunio UNO or
pica Microchip PIC18F2520 but for flashing an LED try the AVR Micronucleus board or a Microchip Xpress board.Q. How do I setup my programmer?
A
copy of microchip in circuit progammer how to would be useful as I had to search for it.This is a wide ranging question. The sheer number of programmers available make this question very hard to answer.
Advice - if you are struggling and after 15 minutes you are not programming using a PicKit post the Great Cow BASIC forum.
Q. What is the minimum setup in my lab to get started?
A. A computer with Windows 7 or greater. A programmer and microcontroller on a board to program and run (or use zif socket board).....then, add a solder station, tools, oscilloscope, angle poise lamp with magnifier and lots of free time.
many questions,many answers. A beginners hard ware programming guide using GCB anyone? It's taken for granted that a user would have that sorted before using GCB but I started with a uno so no problem.If I was using several pics then a universal board would be nice else use a zif socket board that pickit plugs into then a board to test. I'm thinking low cost solutions.Hope no one minds my comments.
Last edit: Anobium 2017-09-24
I will this put in a own sub page, so much Text destroys a FAQ.
It's better placed in a knoledge DB or so.
Last edit: bed 2017-09-24
Q. I am still having problems programming!???
A. In most cases, this is not a problem of the programmer software, but, a problem of the programmer hardware or the connection to the microcontroller.
Some hints, tips and tricks which can be used for troubleshooting such problems.
• Check all Vdd (supply voltage) and Vss (0v) pins of the microcontroller have to be connected to the corresponding power supply pins.
• Each Vdd pin should be connected to a decoupling capacitor, i.e. a capacitor between Vdd and VSS. The capacitor shall be placed as close as possible to the Vdd pin. A typical value for a decoupling capacitor is 100nF.
• For Low-Voltage programmers, make sure that the PGM pin of the microcontroller is tied to ground via a pull-down resistor (~10k).
• For High-Voltage programming, it also might be necessary to connect the PGM pin to GND. So if programming fails, try to connect the PGM pin to ground via a 10k resistor.
• Microcontrollers that can be programmed either in High-Voltage or Low-Voltage mode may make problems during programming in High-Voltage mode if the LVP bit (Low Voltage ICSP Enable bit) in the configuration memory is enabled. Also, if you program a microcontroller the first time, the LVP bit (Low Voltage ICSP Enable bit) in configuration memory is set, i.e. LVP enabled. Issues also happen when using the MCLR pin is used as Input I/O pin.
If the LVP configuration fuse is enabled, PGM should be held low to prevent inadvertent entry into LVP mode.
• If you are using a High-Voltage programmer, make sure that the programming voltage on MCLR pin is within the voltage thresholds specified in the programming specification of the microcontroller to be programmed.
I suppose to have all above taken over now.
Q: Where can I see how big my Program is, how much memory/eeprom/ RAM it uses etc.
A: Easy: look at the Compilation Report in your current project folder. The File with the html extension is what you searching for.
Q: Where comes the Name Great Cow Basic from?
I found same Question in the Forum, but no answer from the Origin Author