I've run into the 2K barrier with PIC16F886/PIC16F688/PIC16f690, reading as much as possible on the forums, I decided to attempt to convert to a PIC18F1320.
When I compile, all seems to go well, until I upload it with a PicKit 2. Errors. Then I tried to upload it with the PicKit 2 software.
Upon loading the hex file, the PICKIT software says the HEX file is too big for the chip!
So I decided to start small again, and just do some tests on this chip.
That is when I noticed the pinouts are completely different in the chip data vs the datasheet!
I don't know enough about the chip data to modify it.
Is there an faq on the chipdata files?
Is there a chance this chipdata file can be checked? I only have PIC18F1320's in the 18 series, and I have 3 of them. tested them all…
Kindest Regards,
Dan Damron VE6IBM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The 18f1320 is definitely messed up. All the PortA and PortB are set to zero! I have the 18f1330 and it is O.K. but there is enough of a difference in registers so as to not be usable for the 1320.
Try making a .bak for the 18f1320.dat, then edit the PortA and PortB in the 18f1320.dat file to match the data sheet and save it. So for instance:
RA1,PORTA,0
AN1,PORTA,0
LVDIN,PORTA,0
Becomes:
RA1,PORTA,1
AN1,PORTA,1
LVDIN,PORTA,1
And so forth.
Hope that works for you, or will have to wait for Hugh to re-parse a new .dat file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The pinout data in the file isn't too major, it's only used by GCGB when it's displaying the pinout of a chip. Something that needs dealing with, but not urgently. The chip data file generation program I have works by guessing the pinout based on the number of pins on the chip - generally this works, but in the case of the 18F1320 Microchip have moved a lot of things to different places.
If the program isn't fitting on the 18F1320, it must be over 4k in size! Did your smaller tests work? I have an 18F1320 stashed away somewhere, will try it out myself when I get home.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did try some sample small programs with no luck. They compiled ok, and using PICCMDV2 (I think) it said it uploaded ok.
However, when I load the generated HEX file in PicKit V2, it says it's too big!
I have a demo I'd like to do for tomorrow, and I would LOVE to get this working on a 18F1320.
Thanks HUGE!
Dan Damron VE6IBM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've run into the 2K barrier with PIC16F886/PIC16F688/PIC16f690, reading as much as possible on the forums, I decided to attempt to convert to a PIC18F1320.
When I compile, all seems to go well, until I upload it with a PicKit 2. Errors. Then I tried to upload it with the PicKit 2 software.
Upon loading the hex file, the PICKIT software says the HEX file is too big for the chip!
So I decided to start small again, and just do some tests on this chip.
That is when I noticed the pinouts are completely different in the chip data vs the datasheet!
I don't know enough about the chip data to modify it.
Is there an faq on the chipdata files?
Is there a chance this chipdata file can be checked? I only have PIC18F1320's in the 18 series, and I have 3 of them. tested them all…
Kindest Regards,
Dan Damron VE6IBM
The 18f1320 is definitely messed up. All the PortA and PortB are set to zero! I have the 18f1330 and it is O.K. but there is enough of a difference in registers so as to not be usable for the 1320.
Try making a .bak for the 18f1320.dat, then edit the PortA and PortB in the 18f1320.dat file to match the data sheet and save it. So for instance:
Becomes:
And so forth.
Hope that works for you, or will have to wait for Hugh to re-parse a new .dat file.
The pinout data in the file isn't too major, it's only used by GCGB when it's displaying the pinout of a chip. Something that needs dealing with, but not urgently. The chip data file generation program I have works by guessing the pinout based on the number of pins on the chip - generally this works, but in the case of the 18F1320 Microchip have moved a lot of things to different places.
If the program isn't fitting on the 18F1320, it must be over 4k in size! Did your smaller tests work? I have an 18F1320 stashed away somewhere, will try it out myself when I get home.
I did try some sample small programs with no luck. They compiled ok, and using PICCMDV2 (I think) it said it uploaded ok.
However, when I load the generated HEX file in PicKit V2, it says it's too big!
I have a demo I'd like to do for tomorrow, and I would LOVE to get this working on a 18F1320.
Thanks HUGE!
Dan Damron VE6IBM
Kent_twt4:
I did try that, but it still didn't work for me.
I tried simple programs like
set PORTA.4 on
do
loop
and compiled that hoping I could see something, but alas, to no avail.
Kindest Regards,
Dan Damron VE6IBM