DIY Electronics Message Board
Register  |   |   |  Latest Topics
 
 
 


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

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

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?

 



Actually, I've just taken a closer look and in fact 0x8000 is correct for the 18F4620 as the RomSize in the chipinfo file is a WORD count and therefore half of the expected 0x10000 which is a byte memory size.

So micropro  is good for 18Fxxx code space sizes up to 64K bytes.

Regards,

Jim Robertson
NEWFOUND ELECTRONICS
newfound

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

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



Program size will need to specified as =006000 and this should allow the whole 48K bytes to be programmed.

See my previous post for an explanation.

Regards,

Jim Robertson
NEWFOUND ELECTRONICS
BruceTElliott

Registered:
Posts: 37
Reply with quote  #18 

Hi Jim,

thanks. I should have paid better attention. I remember just looking at the memory sizes in MicroPro while programming, and they were in bytes. Now I can let Bob work in peace. Thank you.


__________________
Bruce Elliott
BruceTElliott

Registered:
Posts: 37
Reply with quote  #19 

Hi Jim,

 

I've been trying the 18F4680 but can't get it to erase correctly.

CHIPname=18F4680

INCLUDE=Y

SocketImage=40pin

EraseMode=4

FlashChip=Y

PowerSequence=VccVpp1

ProgramDelay=10

ProgramTries=1

OverProgram=1

CoreType=bit16_B

ROMsize=008000

EEPROMsize=00000400

FUSEblank=0600 1F1F 8003 0085 C00F E00F 400F

CPwarn=N

CALword=N

BandGap=N

ICSPonly=N

ChipID=0E80

 

This leaves the Boot ROM area 0000-07FF unerased. The EEPROM is also not erased. Can you help me there? (I'm using, just to be sure, the patch and CHIPINFO from the links you posted today).

Thank you in advance.


__________________
Bruce Elliott
newfound

Registered:
Posts: 497
Reply with quote  #20 


From the PM3 readme file.

Quote:
- Some parts have been found to require a capacitor across VDD
and VSS in order to program the part correctly in the socket.
This is needed to slow down the VDD rise time which is needed
for the part to get correctly into the proper test mode. A
10uf capacitor has been found to work fine for this situation.
The parts affected are:

PIC18F2525   PIC18F2585

Other parts that may have the same issue are:

PIC18F2410   PIC18F2420   PIC18F2455   PIC18F2480
PIC18F2510   PIC18F2515   PIC18F2520   PIC18F2550
PIC18F2580   PIC18F2610   PIC18F2620   PIC18F2680
PIC18F4410   PIC18F4420   PIC18F4455   PIC18F4480
PIC18F4510   PIC18F4515   PIC18F4520   PIC18F4525
PIC18F4550   PIC18F4580   PIC18F4585   PIC18F4610
PIC18F4620   PIC18F4680


I have seen the same problem with the 4620 on my WARP-13.

Nothing more I can do.

Regards,

Jim

P.S. The eeprom size should be 0x100 not 0x400 for reasons discussed before.

rhm

Registered:
Posts: 3
Reply with quote  #21 

Hi all,

Cheers for the info regarding the PIC18F2525, I've started looking at it again, and I can now get it to program and run. It still gives me the same errors on verification.

The listing I posted earlier can be used with the ROM size set to 6000 and the erase mode to 4 as Jim suggested.

 

If anyone can shed any light on the verification errors

Quote:

Rom Error @ 0x0000

Good 0x0E33

Bad 0x0000

then it would be appreciated, but in the mean time, It can be used for development purposes.

 

Regards

 

Richard

Garrick

Registered:
Posts: 36
Reply with quote  #22 
Is the PIC16F913/914/916/917 supported? Or is the programming algorithm similar to one of the other chips?

Thanks,

Garrick

Quote:
Originally Posted by newfound

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

tetsujin

Registered:
Posts: 34
Reply with quote  #23 
Hey,

I'm using a K149 with this firmware and attempting to program 18F4550's - but it doesn't seem to be working.  When I try to read the chip ROM I get all zero's.  Got any suggestions?

(EDIT): It seems that when I programmed the 16F628 with the new firmware, I didn't get the EEPROM data on there, probably...  I'm going to have to correct that and then see if that helps...  This happened because I merged the patch using Micropro, then saved the result to a new HEX file, and then programmed from the HEX file using another tool.  (Micropro didn't save the EEPROM data into the HEX file it created...)

It seems that didn't do the trick...

(EDIT): Seems likely that this was due to a bug in my picpro.py script which I used to interface with the programmer...
gus

Registered:
Posts: 5
Reply with quote  #24 
Hi Jim (newfound).

I am scratching my head trying to make sense of the firmware/chipid files mentioned in your first posting.

I have the Kit 128, so it possibly does not apply. I also have some 18F4550's looking for some action.

I was hoping for a pointer to the firmware (if it now exists for K128), or at least an indication that it simply will not exist.

For the record, I have not been able to track a link to the firmware (page) anywhere. Am I blind?

gus

tetsujin

Registered:
Posts: 34
Reply with quote  #25 
Quote:
Originally Posted by gus
For the record, I have not been able to track a link to the firmware (page) anywhere. Am I blind?


Here is the post in which he provides the link to the firmware patch...  As far as I know there's no patch for the 128 or 182.  I patched my '149 but I've pretty much given up on trying to program the '4550 with it as I've had no luck at all...
gus

Registered:
Posts: 5
Reply with quote  #26 
Thanks a bunch

gus
KM6VV

Registered:
Posts: 10
Reply with quote  #27 
Hi Jim,

I downloaded the 180K ChipInfo file, but didn't see the 18F4620.  I did see 18F8620, 18F6620, and 18F2620.  How similar are they?

Or is there a newer ChipInfo file?

Thanks,

Alan  KM6VV

specialk

Registered:
Posts: 8
Reply with quote  #28 

Jim/newfound,

I just wanted to thank you for your contributions to the Kits-R-Us PIC programmers.  I look forward to a patch for the K128 (and I'm looking forward to programming the PIC18F2550!) and I wanted to let you know how much of an asset to the community you are.  Thanks!

 

-special [k]

peu

Registered:
Posts: 3
Reply with quote  #29 
Hi, after reading for a while about the patches for 18F4550, I programmed the 628a with the merged code, replaced the chipinfo.cid file with the one provided here.

Then I compiled an USB example from pbp 2.46 with no errors using mpasm.

Then I went to the programmer to program the pic. Everything goes smooth but at the finish I receive this error:

Fuse Error 0x300002
Good 0x0F1F
Bad 0xF1F


After the error I clear micropro and then read the contents of the PIC and they seem to be OK.

Just for testing something, after I read the PIC I write the just readed code to the chip again and it writes OK with no errors.


I dont have my test bed ready for testing it with the PC yet, so I cant know for sure if the app works.





Any idea?


Thanks in advance
dickchuck

Registered:
Posts: 9
Reply with quote  #30 

First of all,

 

Jim, I am pretty new to this forum but obviously you kick ass.  I don't know why you would have been barred in the past from offering help when it is apparent that the DIY efforts are focused on new products.  Not to knock anybody.

 

As for me, I still have no luck programming my 18F6621. Having no better idea, I tried your P18 firmware patch/chipinfo updates.  I got the same result.  The only difference between the chipinfo files was a change of CORE_TYPE from 16Bit_C to 16Bit_B.  I don't know what that means really, but I tried it both ways (just in case) with the same result. 

 

To be sure, THIS IS NOT A COMPLAINT!!!  I was just wondering, have you ever successfully programmed an 18F6621?  Or do you know anyone who has?  I can't find anyone on the planet who has done it with a DIY programmer.  I am about to switch to EPIC or other programming device if I can't get this worked out.  Time is money you know...

 

Thanks again for all past and future additions to the knowledge base here!

 

-Rick

Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.

Thank you for visiting.