Hi, the following devices are in the sub directory devices in pps tool folder:
llpic18f25k*-rw-r--r-- 1 bed bed 114662 Feb 5 2019 pic18f25k20_description.xml-rw-r--r-- 1 bed bed 189902 Feb 5 2019 pic18f25k22_description.xml-rw-r--r-- 1 bed bed 325365 Feb 5 2019 pic18f25k40_description.xml-rw-r--r-- 1 bed bed 688856 Feb 5 2019 pic18f25k42_description.xml-rw-r--r-- 1 bed bed 182858 Feb 5 2019 pic18f25k50_description.xml-rw-r--r-- 1 bed bed 394472 Feb 5 2019 pic18f25k80_description.xml-rw-r--r-- 1 bed bed 961336 Feb 5 2019 pic18f25k83_description.xml
If I want select "pic18f25k50" it is not visible and so not selectable within the pps tool
This is in Linux and Windows the same behavior.
What does this mean?
I don't think those particular chips support PPS: the XML files are used by MCC for setting clock speed, PWM, serial etc. so there are XML files for chips without PPS.
I'll have a proper look tomorrow when I'm at a desktop PC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've just checked - the xml file for PIC18F25K50 doesn't contain any information on PPS settings.
The PPS Tool will open the file, but if the data isn't there it won't get added to the dropdown list.
I've checked the datasheet too - it doesn't mention PPS in there either so it's not an error by whoever compiled the xml files (has been known to happen...)
There are some PICs that support PPS, but the PPS Tool cannot handle the settings because it is done in a non standard way. The ones I know about are listed in the help file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There are some PICs that support PPS, but the PPS Tool cannot handle the settings because it is done in a non standard way.
Oh, so I have to read the Datasheet :-) Ok Thank you
Careless as I am, I thought that similar type designations like 18F25K20 and 18F25K50 resemble very much. There I have lost ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm gonna have to cry a little. I hope you'll forgive me. I'm frustrated!
I made a few mistakes when creating a circuit board.
The worst part is that I chose the wrong MCU.
Circuit is based on a PIC18F25K20. with 2 I2C modules, relays etc.
Because there were delivery problems with the supplier and I didn't want to wait 1 week, I took the PIC18F25K50 :-(
The start-up was a fiasco, nothing works, except continuous beeping from the buzzer.
The PIC18F25K50 is not the big brother of the PIC18F25K20!
The 25K50 has no hardware I2C, which is not so tragic by itself, but pins 14 /15 cannot be configured as I/O inputs, so I can't use the board.
(With the 25K20 this would be possible, by the way.)
It would be possible to re-solder tracks, but in a case of mental derangement I used a SSOP and not SOIC.
This makes the spaces between the traces so filigree that it would be impossible for me to make the necessary changes even with a microscope.
However, I have 1 - 2 little things anyway, which I would like to change in the layout.
Fortunately, the financial loss is limited. Unfortunately this means waiting about 4 weeks again when I have the new layout finished.
Conclusion: It is better to always look at the data sheet of a replacement MCU and study it before deciding on a type.
Last edit: bed 2019-10-29
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've done simlar things, but it's a lot easier to fix with PDIP packages.
Could you resolder the traces away from the chip where they are more spread out?
Is it really 4 weeks lead time for a PIC18F25K20?
RS (in the UK) have them in stock and can deliver next day - they are a bit more expensive than other suppliers though https://uk.rs-online.com/web/p/microcontrollers/0564214/
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The deliver delay was, because I designed with wrong package :-( Never mind, a lesson I had to learn ;-)
Normal soic and sdip are in stock :-) Anybody interested in 6 * PIC18F25K50 SSOP?
:O)
No chance to get on the traces, and a way to small anyway. There are 2 minor errors too, so I decide to make it again :-)
They make pics deliberately difficult to use because microchip are sadists! :)
Apart from dev boards with usb,I only use a 18f25k22 which is fast and lots of ram but seems only 2 a to d pins...but it's pins are fixed so no pps tool needed...sigh of relief.
I've never been frustrated when programming because all my programs work first time with no problems.....honest :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, the following devices are in the sub directory devices in pps tool folder:
If I want select "pic18f25k50" it is not visible and so not selectable within the pps tool
This is in Linux and Windows the same behavior.
What does this mean?
Last edit: bed 2019-10-28
I don't think those particular chips support PPS: the XML files are used by MCC for setting clock speed, PWM, serial etc. so there are XML files for chips without PPS.
I'll have a proper look tomorrow when I'm at a desktop PC.
Ok, thank you in advance :-)
I've just checked - the xml file for PIC18F25K50 doesn't contain any information on PPS settings.
The PPS Tool will open the file, but if the data isn't there it won't get added to the dropdown list.
I've checked the datasheet too - it doesn't mention PPS in there either so it's not an error by whoever compiled the xml files (has been known to happen...)
There are some PICs that support PPS, but the PPS Tool cannot handle the settings because it is done in a non standard way. The ones I know about are listed in the help file.
I'm gonna have to cry a little. I hope you'll forgive me.
I'm frustrated!
I made a few mistakes when creating a circuit board.
The worst part is that I chose the wrong MCU.
Circuit is based on a PIC18F25K20. with 2 I2C modules, relays etc.
Because there were delivery problems with the supplier and I didn't want to wait 1 week, I took the PIC18F25K50 :-(
The start-up was a fiasco, nothing works, except continuous beeping from the buzzer.
The PIC18F25K50 is not the big brother of the PIC18F25K20!
The 25K50 has no hardware I2C, which is not so tragic by itself, but pins 14 /15 cannot be configured as I/O inputs, so I can't use the board.
(With the 25K20 this would be possible, by the way.)
It would be possible to re-solder tracks, but in a case of mental derangement I used a SSOP and not SOIC.
This makes the spaces between the traces so filigree that it would be impossible for me to make the necessary changes even with a microscope.
However, I have 1 - 2 little things anyway, which I would like to change in the layout.
Fortunately, the financial loss is limited. Unfortunately this means waiting about 4 weeks again when I have the new layout finished.
Conclusion: It is better to always look at the data sheet of a replacement MCU and study it before deciding on a type.
Last edit: bed 2019-10-29
I've done simlar things, but it's a lot easier to fix with PDIP packages.
Could you resolder the traces away from the chip where they are more spread out?
Is it really 4 weeks lead time for a PIC18F25K20?
RS (in the UK) have them in stock and can deliver next day - they are a bit more expensive than other suppliers though https://uk.rs-online.com/web/p/microcontrollers/0564214/
The deliver delay was, because I designed with wrong package :-( Never mind, a lesson I had to learn ;-)
Normal soic and sdip are in stock :-) Anybody interested in 6 * PIC18F25K50 SSOP?
:O)
No chance to get on the traces, and a way to small anyway. There are 2 minor errors too, so I decide to make it again :-)
Last edit: bed 2019-10-29
They make pics deliberately difficult to use because microchip are sadists! :)
Apart from dev boards with usb,I only use a 18f25k22 which is fast and lots of ram but seems only 2 a to d pins...but it's pins are fixed so no pps tool needed...sigh of relief.
I've never been frustrated when programming because all my programs work first time with no problems.....honest :)
You're a joker. :-)
Most of the time the problem is sitting in front of the screen, so also here ;-)