12f675_fuse_about_to_blow!

[LEDave]

First off, many thanks for the replies Bob & Joe, very much appreciated I can assure you.

So programming these devices in 'C' and Assembler is out and using PIC-BASIC seems the way to go right?

A few more questions then if I may.

1/ Can I still use my PICkit1 Flash Starter kit to load / run and test my programs even using PIC-BASIC (I'd hate to think I'd bought the kit for nothing). Or do I have to buy another evaluation board from Melabs as well as the program / compiler?

2/ Just to make sure here, PIC-BASIC isn't included in my Microchip PICkit is it?

3/ Will the PICBASIC PRO™ Compiler Demo from Melabs allow me to run and create a HEX code for the program that Joe posted for me? And can I then load the HEX code into my PICkit Starter Kit and into a 12F675 chip?

I hope all my questions make sense and thanks for your time everyone.

LEDave

[mackrackit]

So programming these devices in 'C' and Assembler is out and using PIC-BASIC seems the way to go right?

Most of us here think PBP is the way to go Mix a little ASM in now and then and you will be able to do just about anything you can think of.

1/ Can I still use my PICkit1 Flash Starter kit to load / run and test my programs even using PIC-BASIC (I'd hate to think I'd bought the kit for nothing). Or do I have to buy another evaluation board from Melabs as well as the program / compiler?

All Pic Basic Pro is for is to make a HEX file. You will not need to buy another programmer until you out grow the PICkit1. Then get the PICkit2.

2/ Just to make sure here, PIC-BASIC isn't included in my Microchip PICkit is it?

No, it is not. All the PICkit is for is to take a HEX file and place it on the chip.

3/ Will the PICBASIC PRO™ Compiler Demo from Melabs allow me to run and create a HEX code for the program that Joe posted for me? And can I then load the HEX code into my PICkit Starter Kit and into a 12F675 chip?

Yes. I still use my PICkit1 now and then.

[LEDave]

mackrackit

Thanks for the speedy reply.

Have I got this right? I can use the "PICBASIC PRO™ Compiler Demo from Melabs" and make some simple 12F675 projects without having to buy anything else.

And then, when I get more confident I can buy the BASIC or PRO-programmer / compiler.

Or do I have to buy the BASIC-programmer / compiler now before I can go any further.

LEDave

[mackrackit]

Unfortunately the demo will not work with the 675, but the PICkit1 will work with most any 14oin or 8pin PIC.

Demo version PIC® MCU support:

PIC12F683, 16F627(A), 16F628(A), 16F84(A), 16F688, 16F690, 16F87, 16F88, 16F870, 16F871, 16F872, 16F873(A), 16F874(A), 16F876(A), 16F877(A), 16F882, 16F883, 16F884, 16F886, 16F887

And the demo is limited to 31 lines of code.

Yes, try before you buy. That is what the demo is for.
In my opinion if you are going to stay with MCU programming, get the pro version.

[LEDave]

mackrackit

So if I buy the 'pro version' I can use my PICkit1 to load the hex file into my projects?

[mackrackit]

Yes.

PBP will generate the HEX. Then you will use the PICkit1 software to load the HEX onto the PIC. The PICkit does not care who or what makes the HEX.

[LEDave]

mackrackit

So if I buy the 'pro version' I can use my PICkit1 to load any HEX files I create into my projects?

What about the program Joe S wrote for me in this thread (Is it written in PICBASIC) how do I turn that into a HEX file and run it on my PICkit?

Oop's sorry for double posting I lost my way there for a second.

Also interesting website of yours.

All very confusing right now but I'll get there.

LEDave

[LEDave]

So if I buy the 'pro version' I can use my PICkit1 to load any HEX files I create into my projects?

What about the program Joe S wrote for me in this thread (Is it written in PICBASIC) how do I turn that into a HEX file and run it on my PICkit? Will my MPLAB IDE convert it?

Oop's sorry for double posting I lost my way there for a second.

Also interesting website of yours.

All very confusing right now but I'll get there.

LEDave

[mackrackit]

Yes, the code Joe wrote is in done in PBP.

BASICS....
When you get your PBP CD there will be a program there called Micr Code Studio (MCS). This is where you will write your code. You can use other editors but MCS is probably best for starters.

Copy Joe's code into MCS or write your own. There are config fuses that need set, Joe did not include that but we can go over that when you are ready.

Once you are happy with the code there is e a "button" in MCS to click and PBP runs to compile the code into HEX. The HEX is saved in your project directory.

The PICkit1 has software of its own. Open that and open the HEX created by PBP using MCS. There will be a "Write" button in the PICkit software. ( you already know about that I guess).

My web site is a work in progress. I hope it will help someone along the way.

[LEDave]

"There will be a "Write" button in the PICkit software. ( you already know about that I guess)."

Yes I've managed to load / erase and reload the demo HEX programs.

So I need to save up some pennies then for the pro-version, all fascinating stuff though and I will get there.

Like Arni, I will be back.........!

Many thanks

LEDave

[HenrikOlsson]

Hi Dave,
I'll expand a bit on what's already been said. Not because any of it is wrong, just trying to help you get the picture.

This is basically how the code gets from PBP syntax to a .hex file in your chip:
IDE -> Compiler -> assembler -> device programmer -> PIC

1) IDE. Integrated Development Enviroment (a fancy word for a text editor on steroids) This is where you actually write your PBP program, it can be Notepad or MicroCode Studio, which is included with PicBasicPRO when you buy it. The later is recomended but not needed.

2) Compiler. This is PicBasicPro - it compiles or "translates" your BASIC statements and commands into assembly language that can then be converted to a .hex file by the...

3) Assembler. There are two assemblers available, one comes with PBP and one comes with MPLAB. There are times when one needs to use the one over the other but lets not get into that at the moment. The assembler is what takes the assembler listing that the compiler produced and generates a .hex file that can be programmed into the PIC by the....

4) Device programmer. This is the hardware devices and it's associated software used to get the .hex file fromt tha harddrive on the computer into the actual PIC chip. As you probably can see here it doesn't know or care how you got that .hex file.


This may sound like a lot but if you use the MicroCodeStudio IDE it all happens behind the scene. You type in your BASIC program and hit the compile button and out comes a .hex file ready to be programmed into your PIC by the PICKit1 or any other device programmer supporting the PIC-chip you're using.

If you're lucky the PicKit1 is even directly supported by MicroCodeStudio. IF that is the case you don't even need to launch the PicKit1 software to get the .hex file into the chip - MicroCodeStudio handles that for you as well. One single click get you from BASIC code in the IDE to a programmed chip.

/Henrik.

[Archangel]

Yes, the code Joe wrote is in done in PBP.

BASICS....
When you get your PBP CD there will be a program there called Micr Code Studio (MCS). This is where you will write your code. You can use other editors but MCS is probably best for starters.

Copy Joe's code into MCS or write your own. There are config fuses that need set, Joe did not include that but we can go over that when you are ready.

Joe did not include those, because the "DEFAULT" config located in the 12F675.inc file will work and I did not want to add to his confusion, rather just to demonstrate how simple PBP really is, but I digress, Dave (mackrackit) is right, Configs are something you will have to deal with, regardless of your choice of compiler.
In a nutshell _ _ _ You write a program in C or PBP and compile it into an assembly program, the Assembler, I E MPASM, turns it into a HEX File and your PICKit stuffs it into the PIC. And If you wrote it right then your PIC is Fat, Dumb and Happy Doing what you ordered it to do. And yeah, I know the demo does not support the 675, so 2 bucks? gets you a 12F683 which it does support. As for your programmer, it will stuff the hex from any of the methods available as long as it supports the chip you have chosen. My first programmer was a JDM clone from an eBay seller in Bulgaria for $8.00 US, used Iprog, or PonyProg or one of those freebie programs to operate it. The best part about PBP is this forum, nobody here will steer you wrong intentionally.