Compiling under Windows 10

[Skipweasel]

I used GCB some years ago under either XP or W7 - can't remember which.

Now I've come to use it again under Windows 10 I can't find where the .hex file ends up. I've looked in the GCB folder and all subfolders, and I've searched the whole C drive for compiled.hex.

Is this a permissions thing? Is W10 preventing the compiler from writing to the root of C:\ and if so, what on earth do I do about it?

I've searched for existing discussions but can't find any. Thanks - skipweasel.

[Anobium]

Hi,

Is thîs a new download and installation using the installer? if I assume yes, and, you have used the IDE then the hex file is in the same place as the source GCB file.

[Skipweasel]

Yes, and it isn't. Perhaps I'll uninstall and try it all again. Thanks for answering - I'll check back later with an update.

[Skipweasel]

OK, I've uninstalled and reinstalled it, and I've tried letting it choose its own location and also forcing it to use ProgramFiles(x86) and still nothing.

Let me just check I'm doing the right thing.

• I'm dropping the .gcb file onto gcbasic.exe
• A DOS box appears, "Compiling xyz" then vanishes.
• An html file appears in the original folder.
• No .hex file appears. I've even made sure "hidden files" are shown.
• Any ideas?

[Anobium]

Please use the IDE interface.   You do not need to drag and drop onto the exe anymore.

[Skipweasel]

OK, that did it. I was just following the instructions!

Thanks for your help.

[Anobium]

Pleasure. Enjoy the latest build.

[Skipweasel]

I'm getting there. I can get the Pickit 3 to talk to a 16F628, but not to an 18F25J10.

There's always tomorrow. Might be an idea to fix the instructions.

[Anobium]

We will gladly take feedback on the installation process. Please drop me a personal message so I can get the feedback. We improve, of course.

re the 18f25j10. This may be as simple as an Pk3 default installation not supporting this device. We have included an updated version of pk3 in your installation and a set of pk3 driver files. See your installation ..\GCB@Syn\PicKit3GUI and ..\GCB@Syn\PicKit3GUI\Updated DAT file for the update .dat files. We have included a set of different .dat files for supportability and stability. There are also a later set to be found here .

[William Roth]

You can easily tell if 18F25J10 is supported by the Pickit3 GUI that ships with the latest release of Great Cow Basic.

Connnect the Pickit 3 to USB Port.
Open the GUI.
Select Device Family > 18F_J_
Select Programmer > Manual device select
Device: Select part ... Scroll down the list and look for 18F25J10

If it is in the list then it should be supported by both PK2 and PK3 GUIs.

If still no communication then check the following.

I am assuming that PIC has external 3.3v Supply connected and that 18F25J10 is 28 Pin DIP and that no other device (Display, etc) Except PK3 is connected to PIC /breadboard.

1. Vdd to PIC is 3.3V ( 5V will damage this chip)
2. 10K Pullup from 18F25J10 MCLR to 3.3V Vdd ( See datasheet figures 2-1 & 2-2)
3. PK3 Pin1 (Arrow ) to 18K25J10 MCLR - Pin1
4. PK3 Pin2 to 3.3v Vdd
5. PK3 Pin3 to Gnd
6. PK3 Pin4 to 18F25J10 PGD (Pin 28)
7. PK3 Pin5 to 18F25J10 PGC (Pin27)
8. Make sure that PIC Vdd is tied to PK3 Vdd ( Pin2)
9. Make sure that PIC Gnd is tied to PK3 Gnd ( Pin3)
10. Make sure that Vdd is corredtly bypassed. (Datasheet 2.2.1)

The default setting for PK3 is that power is supplied to the PIC by a source other than the PK3.
Check Power supply for noise. Filter if necessary
Is the Chip already programmed? IF so does the program run when chip is powered up?

If all this fails to get PIC to communicate with PK3 (GUI) ...

1. Open PK3GUI > Tools > Revert to MPLAB mode > Close GUI
2. Download MPLAB X 3.30 and Install IPE. (Yes this is a pain !)
3. Make sure PIC is powered with 3.3v. (Use voltmeter to verify)
4. Open IPE > select correct family & Chip > Apply/Connect.

If still no go. then either chip is blown/bricked or voltage/connection problems.

Good Luck - William