unlisted chip 16F1824 and ICSP question

[comwarrior]

ok, i wanted to use the 16F1824, i checked my programmer (pickit2 compatible).
What i forgot to do is to check is if it's supported by pbp2.60a, and their is no inc files for it.
however, mpasm has an inc file...

So, first question, how do i get PBP and MCS to 'recognise' the 16F1824? is it as simple as copying mpasm's inc file into pbp directory? or as pain in the but as having to create my own?

Secondly...
i recommended the melabs U2 programmer to a friend as the bee's knees... but the chip is not listed on the U2 programmer, and yet, it's listed on mine. Suffice it to say, this is a tad embarrassing since my programmer cost my 1/4th of the price of the U2...

so, why is it listed on mine and not the U2?
Is it something to do with the VPP programming voltage?
I've seen reference to VPP being ~13V and on the 16F1824 it seems to be 9V, if i've read the datasheet correctly?

This opens up a bucket load of questions like if i build a voltage limiter for the VPP line, how do i get the U2 programmer to recognise the 16F1824, or can i select the 16F1826 just for programming?

Help is always appreciated.

[mister_e]

AFAIK Even If you could create an INC file, the compiler just don't know its exitencce... so you need to wait untill they add it to the supported list... or program the beast in ASM ;)

So if the PIC is not supported, why on earth their PIC(tm) Programmer should suport that?

I think once they release PBP(tm of MicroEngineering Lab inc) support, you'll have it included in the PIC(tm) programmer.

[comwarrior]

Ok, so why are some pic16 chips 'supported' and others not?
Surely all the PIC16's use the same set of commands? so then it's just the hardware config that needs to be changed, hence the inc files...
So why not leave this open so that users that roughly know what they are doing can make their own inc's for unsupported chips? Perhaps Melabs could have a 'submition' page that we could submit our 'working' inc's to melabs and then they could include them once approved...

[mister_e]

I hear you, I can't comment but only state my speculations (from here all my speculations about that are over). I would suggest you to send an e-mail to Melabs, maybe they already have something workable or a patch release date.

[comwarrior]

ERROR: Unable to find -p<pic> processor file 16F1824.BAS


this indicates to me that the compiler can do the 1824...
It's bed time now (2AM) so tomorrow i think i'm going to create the inc and bas files and see what it does...

Unless anyone else has more info?

[Darrel Taylor]

Microchip is continually creating new parts, and it takes time to examine each one, find the changes they've made and adjust the compiler accordingly.

Just making new .inc .bas .bal files is not always good enough to be able to use a new chip.
They move registers and bits around at will and PBP has to account for the changes.
They don't publish a list of "Things that are Different", so every chip must be evaluated and tested separately.

There's a large number of chips that will be added in the 2.60B patch. (almost ready for release)
The 16F1824 is one of them.

All of those chips are also being added in the latest melabs Programmer software v. 4.40. (this week)

[mister_e]

Voices of heaven spoke... Amen to that ;)

BTW, Congrats for your new job Darrel.

[Darrel Taylor]

Thanks Steve.
I'm on top of the world.

Well, literally ... we're at 6100 ft elevation. :)

It's good to see you back again.

[mister_e]

On the top of the world :eek: I see, it answer my question about the new look of your cat
<IMG SRC="http://silverjacket.typepad.com/photos/uncategorized/2007/06/14/icanhasplanet.jpg">

:D

[comwarrior]

thanks DT, you da man! ;)

[HankMcSpank]

In my blissfully ignorant world of what goes on 'under the hood' ("there be scary stuff lurking that way") , I've simply selected an 161823 in PICBASIC when actually using a 16f1824 .....works for me! (that said, I'm only using a small amount of codespace)

I can't be held accountable if your sofa suddenly spontaneously combusts if you try this too (I'm still paying off the last one)