Feeling Noobish with 12F683

[picster]

Same results in the ZIF socket and in the on-board socket.

Any other ideas? If the 16F88's wouldn't program, I'd at least have a pattern.

Also tried another 12F683, same result.

Steve

[Bruce]

Contact [email protected]

I'm sure they'll get you up & going.

[mackrackit]

Can you post your config seetings from the inc file and the generated hex from you compiler?

[picster]

Can you post your config seetings from the inc file and the generated hex from you compiler?

I use the config settings via meProg options, not in the file itself, and have them set as follows:

Oscillator: INTOSCIO
Watchdog Timer: Disabled
PowerUp Timer: Disabled
MCLR Pin Function: Reset
Brown-out Detect: Disabled
Internal External Switchover: Disabled
Fail-Safe Clock Monitor: Disabled
Code: Not Protected
Data EEPROM: Not Protected


Here's the hex generated:

:020000040000FA
:100000002E288001840AFF3E031D01282928A30110
:10001000A200FF30A207031CA307031C29280330FA
:10002000A100DF3015200928A101E83EA000A109A8
:10003000FC30031C1E28A00703181B28A00764001F
:10004000A10F1B2820182428A01C282800002828DD
:10005000080083130313831264000800073099001B
:1000600083169F0160308F00283085002030840087
:10007000603083120120A03084002030012005165A
:100080000130A300F430082005120130A300F43041
:0400900008203F28DD
:02400E00FC3F75
:00000001FF

Steve

[Darrel Taylor]

Do you have the program Configuration option checked?



Added: And since you are changing the configs manually, unchecking the Update Configuration From File option will make things easier. Won't help the current problem though.

[mackrackit]

I use the config settings via meProg options, not in the file itself, and have them set as follows:

Oscillator: INTOSCIO
Watchdog Timer: Disabled
PowerUp Timer: Disabled
MCLR Pin Function: Reset
Brown-out Detect: Disabled
Internal External Switchover: Disabled
Fail-Safe Clock Monitor: Disabled
Code: Not Protected
Data EEPROM: Not Protected

Here is what you hex says
<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=2914&stc=1&d=122429288 4">
Almost matches. I do not have you setup. Is there a way with you programmer to set the fuses from the inc or in the code?

I am just guessing again

[picster]

Darrel,

I have the item you noted checked, and upload config from file UNchecked. I don't have "Program Fast" checked - but I doubt this would be the problem?

Maybe a bug in the 683 include file? Should I post it for comparison to yours? I haven't edited it or anything, but maybe it's a 2.46 undoc'd bug or something?

Steve

[picster]

Dave,

Not sure about how to set the fuses in code, I've always done it from the EPIC programmer's chip configuration settings window because it's simple.

I'm doing the PICBASIC in microcode studio - so if there's an easy way to set these switches there, I suppose I could try it (but right now I wouldn't know how).

Steve

[mackrackit]

Dave,

Not sure about how to set the fuses in code, I've always done it from the EPIC programmer's chip configuration settings window because it's simple.

I'm doing the PICBASIC in microcode studio - so if there's an easy way to set these switches there, I suppose I could try it (but right now I wouldn't know how).

Steve

This is the best explanation of how to set the fuses in code space.
http://www.picbasic.co.uk/forum/showthread.php?t=543
As usual, pay close attention to the post from Melanie and Mister-E.
Is there a way in the EPIC to turn that option off? I have not used the EPIC.

[skimask]

Same results in the ZIF socket and in the on-board socket.
Any other ideas? If the 16F88's wouldn't program, I'd at least have a pattern.
Also tried another 12F683, same result.
Steve

What version of software/firmware for the EPIC PLUS are you running?

[picster]

using meProg 3.30 - is there firmware for the Epic Plus parallel?