DIY Electronics Message Board
Register  |   |   |  Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 5      1   2   3   4   Next   »
newfound

Registered:
Posts: 497
Reply with quote  #1 

Great news! I'm back on the forum board thanks to a reversal of decision by Bob.

I have updates for you!

First, the changes to the 10F entries that I had previously posted DO WORK contrary to what was posted previously by two persons other than myself. I have now tested this myself  as my parts arrived a few days ago.

Want to program the 10Fxxx parts? You can do it right now with the attached chipinfo file!

I have added the 12F508, 509 and 16F505 too. These all work.

Also added and supported right now are the 18Fxx31 family. Someone was asking so I've added them. These do not require any firmware update. Just the new chipinfo file.

The 18F2550, 4550 USB parts. Yep, got them working too. These require a firmware update and I have patched firmware for the K149 and K150. (Not yet for the other progs. )

Also in this boat are the 18F2x20, 4x20, 2x80, 4x80 and others.

Check 'em out

• PIC18F2321 • PIC18F2421
• PIC18F4321 • PIC18F4421
• PIC18F2410 • PIC18F4410
• PIC18F2420 • PIC18F4420
• PIC18F2455 • PIC18F4455
• PIC18F2480 • PIC18F4480
• PIC18F2510 • PIC18F4510
• PIC18F2515 • PIC18F4515
• PIC18F2520 • PIC18F4520
• PIC18F2525 • PIC18F4525
• PIC18F2550 • PIC18F4550
• PIC18F2580 • PIC18F4580
• PIC18F2585 • PIC18F4585
• PIC18F2610 • PIC18F4610
• PIC18F2620 • PIC18F4620
• PIC18F2680 • PIC18F4680

The patch is also good for other 18Fxxx parts. In fact I believe all of them are now supported by the patched firmware.

This patch firmware has been tested by Dave Kerr who also contributed to the addition of some 18Fxxx parts.

I am currently looking at the 12F and 16F parts to see what is not currently supported and what can be added. I may again have to patch the firmware but I have cleared some room inside the 16F628.

Important Notes.

Please understand that my updates apply only to the firmware, not to MicroPro. Just because a device is theorically supported by the firmware, it does not mean that MicroPro will either fully or correctly support it. MicroPro only allows 34 different config word types and there are few PICs that exceed this.

MicroPro is not the greatest piece of software in the world and I do feel that it needs to be replaced in the medium to long term.

Ok, this is enough typing for me in one hit. More later.

Regards,

Jim Robertson
NEWFOUND ELECTRONICS




newfound

Registered:
Posts: 497
Reply with quote  #2 
Oh, be careful. The 10F206 in the chipinfo file with the date 08/05.2005, 11.13AM is designed to work through the zif socket NOT the ICSP port. The other 10Fxxx parts are defined to work through the ICSP port.

My K149A does not have an ICSP so I tested my 10F206  by lifting thesignals from the zif socket. That is why it is defined differently.

You can change it to the ICSP port by looking at the other 10Fxxx parts. There should be two lines to alter:

PowerSequence=VccVpp?
ICSPonly=N

Regards,

Jim

toloookah

Registered:
Posts: 21
Reply with quote  #3 
you mention a firmware change, but don't post the firmware or where to get (for the USB pics)  I assume you mean a change to the chip, and that chipinfo doesnt hold those (I thought) 

can you post it? ^_^

newfound

Registered:
Posts: 497
Reply with quote  #4 

Sorry, there were a few extra lines in the previously uploaded chipinfo file that were for new entries I was planning. These entries were not completed and would cause a syntax error with MicroPro.

The fault as been corrected.

Regards,

Jim


Harry

Registered:
Posts: 13
Reply with quote  #5 
Minor addendum...
18F6520:
must be EEPROMsize=00000400, not 00000100.
newfound

Registered:
Posts: 497
Reply with quote  #6 
Hi Harry,

Accepting that you are technically right the same "error" would present on a number of other 18Fxxx PICs.

However, it is not really an error because, sadly, the existing P18 firmware can only address the first 256 locations of EEPROM space. Any EEPROM address over 0xff will wrap back on to the first 0x0 - 0xff address range as the EEADDRH register never accessed by the firmware.

This is why I have all eeprom sizes set at 0x100 maximum even when there is a larger eeprom present. .

If this chipinfo file is converted for use with the P19 firmware then these EEPROM sizes will need to be corrected, assuming of course, that the P19 firmware doesn't have the same limitation.

Well spotted any way.

Regards,

Jim Robertson
NEWFOUND ELECTRONICS






BruceTElliott

Registered:
Posts: 37
Reply with quote  #7 

Hi Jim,

I take it, that that's the same explanation for limiting the programing area to hex 8000 instead of 10000 for chips like 4620. P18 can't hack it?

 


__________________
Bruce Elliott
newfound

Registered:
Posts: 497
Reply with quote  #8 
Well, it appears to me that there is no provision in the P18 protocol for address counts greater than 0xFFFF.

My recall is that a '0000' count  would be treated as zero by the firmware and not as 0x10000

You can try a count of 0xFFFF and see if that will program all but the last location. 

Bottom line is that honestly I cannot recall why the count is only 0x8000 and it could be just an oversight or maybe I did fine something.
 
I would be as interested as anyone on more testing and data. Sadly, due to the lack of support I have received from the rank and file users I have sort of backed off doing anything more myself.


Regards,

Jim Robertson
NEWFOUND ELECTRONICS


rhm

Registered:
Posts: 3
Reply with quote  #9 

Hello all,

just a quicky, at the top of this thread, you mention inclusion of the PIC18F2525, which sadly(for me) doesn't seem to have made it into the chipinfo file.

 

Are there any plans to include this?

 

Please don't make me have to resort to using the promate... that would be cruel.

 

Cheers

 

Richard

BruceTElliott

Registered:
Posts: 37
Reply with quote  #10 

Hi Jim,

I tried to use 0xFFFF, but that didn't work. Always came up with an error. That's why I changed to http://www.members.aon.at/electronics/pic/picpgm/index.html another cheap programmer, but that one uses low voltage programming. It can program to 0x10000 though. Guess I'll have to wait for P19.

Thanks for the work though. It helped considerably.


__________________
Bruce Elliott
newfound

Registered:
Posts: 497
Reply with quote  #11 
Quote:
Originally Posted by rhm

Hello all,

just a quicky, at the top of this thread, you mention inclusion of the PIC18F2525, which sadly(for me) doesn't seem to have made it into the chipinfo file.

 

Are there any plans to include this?

 

Please don't make me have to resort to using the promate... that would be cruel.

 

Cheers

 

Richard



Well, you can put in a bit of effort and add it yourself and then provide the updated chipinfo file for everyone's use.

I have provided a patch to the firmware that will allow this device to be correctly erased and programmed. Why it would fall to me to add every new device to the chipinfo file I don't know. I have already added many and, for the most, had my efforts ignored.

Regards,

Jim Robertson
NEWFOUND ELECTRONICS
newfound

Registered:
Posts: 497
Reply with quote  #12 
Quote:
Originally Posted by BruceTElliott

Hi Jim,

I tried to use 0xFFFF, but that didn't work. Always came up with an error.
snipped...  Guess I'll have to wait for P19.

Thanks for the work though. It helped considerably.



I may take another look later and see if there is something that can be done to remedy this.

Thanks for your feedback and appreciation.

Regards,

Jim

KitsRUsBob

Registered:
Posts: 419
Reply with quote  #13 
Thanks Jim, for all the help! If you agree that they work, give Jim the feedback and an attaboy! so that he can fix other items. Jim is very technically competent with PIC programmers, having designed one of his own.

But these changes are not official DIY updates.

--Bob



rhm

Registered:
Posts: 3
Reply with quote  #14 

Apologies for my lack of apparent gratitude, I myself, and I am sure most who utillise your software are grateful.

 

I have made some way into creating an 18f2525 entry, see below.

 

I have managed to get it to recognise the device, and to the best of my knowledge, the fuse settings are correct.

 

I have a couple of things I am unsure about.

 

1) the device in the datasheet is stated as being 48K, but micropro wll only allow upto 32K of program memory, so I have set it to 008000

2) I have assumed that erase mode is 6.

3) When I program i get  the following error:

 

Rom Error @ 0x0000

Good 0x0E33

Bad 0x0000

 

do you have any ideas that would help with this?

 

regards

 

Richard

 

Code:
 CHIPname=18F2525

INCLUDE=Y
SocketImage=28Npin
EraseMode=6
FlashChip=Y
PowerSequence=VccVpp1
ProgramDelay=10
ProgramTries=1
OverProgram=1
CoreType=bit16_B
ROMsize=008000
EEPROMsize=00000100
FUSEblank=0700 1F1F 8300 0085 C00F E00F 400F
CPwarn=N
CALword=N
BandGap=N
ICSPonly=N
ChipID=0CC0
LIST1 FUSE1 "Oscillator Enable" "Disabled"=FFFF "Enabled"=DFFF
LIST2 FUSE1 "Oscillator" "RCO2RA6"=FFFF "HSPLL"=FEFF "ECO2RA6"=FDFF "ECO2 CLK Out"=FCFF "RC"=FBFF "HS"=FAFF "XT"=F9FF "LP"=F8FF
LIST3 FUSE2 "Brownout Voltage" "2.0V"=FFFF "2.7V"=FFFB "4.2V"=FFF7 "4.5V"=FFF3
LIST4 FUSE2 "Brownout Detect" "Enabled"=FFFF "Disabled"=FFFD
LIST5 FUSE2 "Powerup Timer" "Disabled"=FFFF "Enabled"=FFFE
LIST6 FUSE2 "Watchdog Postscale" "1:128"=FFFF "1:64"=FDFF "1:32"=FBFF "1:16"=F9FF "1:8"=F7FF "1:4"=F5FF "1:2"=F3FF "1:1"=F1FF
LIST7 FUSE2 "Watchdog Timer" "Enabled"=FFFF "Disabled"=FEFF
LIST8 FUSE3 "CCP2 Mux" "Enabled"=FFFF "Disabled"=FEFF
LIST9 FUSE4 "Background Debug" "Disabled"=FFFF "Enabled"=FF7F
LIST10 FUSE4 "Low Voltage Program" "Enabled"=FFFF "Disabled"=FFFB
LIST11 FUSE4 "Stack Overflow Reset" "Enabled"=FFFF "Disabled"=FFFE
LIST12 FUSE5 "BOOT ROM Protect" "0000-01FF Disabled"=FFFF "0000-01FF Enabled"=BFFF
LIST13 FUSE5 "ROM Protect" "0200-1FFF Disabled"=FFFF "0200-1FFF Enabled"=FFFE
LIST14 FUSE5 "ROM Protect" "2000-3FFF Disabled"=FFFF "2000-3FFF Enabled"=FFFD
LIST15 FUSE5 "ROM Protect" "4000-5FFF Disabled"=FFFF "4000-5FFF Enabled"=FFFB
LIST16 FUSE5 "ROM Protect" "6000-7FFF Disabled"=FFFF "6000-7FFF Enabled"=FFF7
LIST17 FUSE5 "EEPROM Protect" "Disabled"=FFFF "Enabled"=7FFF
LIST18 FUSE6 "BOOT Table Write Protect" "0000-01FF Disabled"=FFFF "0000-01FF Enabled"=BFFF
LIST19 FUSE6 "ROM Table Write Protect" "0200-1FFF Disabled"=FFFF "0200-1FFF Enabled"=FFFE
LIST20 FUSE6 "ROM Table Write Protect" "2000-3FFF Disabled"=FFFF "2000-3FFF Enabled"=FFFD
LIST21 FUSE6 "ROM Table Write Protect" "4000-5FFF Disabled"=FFFF "4000-5FFF Enabled"=FFFB
LIST22 FUSE6 "ROM Table Write Protect" "6000-7FFF Disabled"=FFFF "6000-7FFF Enabled"=FFF7
LIST23 FUSE6 "EEPROM Table Write Protect" "Disabled"=FFFF "Enabled"=7FFF
LIST24 FUSE6 "CONFIG Table Write Protect" "Disabled"=FFFF "Enabled"=DFFF
LIST25 FUSE7 "BOOT Table Read Protect" "0000-01FF Disabled"=FFFF "0000-01FF Enabled"=BFFF
LIST26 FUSE7 "ROM Table Read Protect" "0200-1FFF Disabled"=FFFF "0200-1FFF Enabled"=FFFE
LIST27 FUSE7 "ROM Table Read Protect" "2000-3FFF Disabled"=FFFF "2000-3FFF Enabled"=FFFD
LIST28 FUSE7 "ROM Table Read Protect" "4000-5FFF Disabled"=FFFF "4000-5FFF Enabled"=FFFB
LIST29 FUSE7 "ROM Table Read Protect" "6000-7FFF Disabled"=FFFF "6000-7FFF Enabled"=FFF7

newfound

Registered:
Posts: 497
Reply with quote  #15 
Nice effort.

EraseMode=4

See how that goes.

I see no reason why you cannot specify codesize as 0xC000. Once you have the device erasing and programming correctly you can try this. Remember that you need to quit MicroPro and reload it so it will read the changes to the chipinfo file.

Regards,

Jim
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Thank you for visiting.