I took the mpk...1525 in the message above and it seemingly got installed. It ended with "Finishing update..." I tried twice. Are you talking about something else?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Excellent. I thought I had updated that MPK. Thanks for patience.
Angel is working on a new release with all these updates. The new release is a huge step forward. It has full support for debugging. I am using the re-release version and the debugger and it is so easy to use.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Someone needs to update the PPS configuration files for the complete chipfamily. I have done this for the 16F17556 ( which I am using ). You could use that as the 76 is a similar layout.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not seeing any of these new chips in the PPS tool (including16F17556). So there must be something else missing in my setup.
There is no hurry from my side, I just want to have things setup for later when I get some time off.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and, the you need the attached file ( because I have not had time to create an MPK. Put in the C:\GCstudio\ppstool\devices folder.
I am working with Microchip regarding PICINFO. Microchip have a broken datafeed. PICINFO will failback to a local copy of the Microchip datafeed - so, hopefully this keeps access to datasheets etc operational. Essentially, we are working around Microchip issues.
I can't get the 16F17576 to work with neither software SPI to GLCD nor software i2C to GLCD.
A LED Blinky works on C.4 and C.5, so the ports are alive.
I'm using a 16F17576 curiosity nano board.
I don't have this demo saved in GCbasic (PT13: PIC16F175xx chip Family - Using SPI and a GLCD) and I don't know where to find it.
I found a similar one with a different number 260: https://github.com/GreatCowBASIC/Demonstration_Sources/blob/main/Vendor_Boards/Great_Cow_Basic_Demo_Board/16F17556_chiprange_demonstrations/260_spi_glcd_using_SSD1331.gcb
It used mixed PortA and PortC, so I changed it to what you used in the demo and set the chip to 16F17576 because that is what is on my curiosity board.
It starts off black for 4-5 seconds, then
blue, red, blue, red, blue...mainly yellow, then a scoll of some pattern then it goes black, once now and then it flicker, flashes some random mess and then black again.
Softare spi is about the same as hardware spi, but slower.
Since this didn't work I tried a simple GLCD_TYPE_SSD1306_64x32 software i2Cprogram with that screen on the same PORTC.4 and C.5.
No reaction.
Switching over to my other new curiosity nano board 18F57Q84. Now the demo program works on SSD1331.
So far only with software SPI. No luck with hardware SPI.
I did setup the PPS for this chip, but I don't know if there are other limitations that I'm not aware of.
I now got the 16F17576 to work. It turns out RC0 and RC1 is not connected (no blinky on them) so I changed to other pins. They are marked <rc0> and <rc1>. I don't understand if there is something I should have done as these are also SOSCI or SOSCO or if there is something that should be set somewhere for this chip.</rc1></rc0>
18F56Q84 is now also working. It was way past bedtime and I should just have given it (and me) a rest or I could have read what the PPStool returned. I would then have seen my mistake in selecting SCL instead of SCK. Sorry about that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used:
GLCD SSD1331 - 16F17576 (curiosity nano board)
CS - RC1
DC - RC0
RES - RC2
SDA - RC5
SCL - RC4
DCC - VTG
GND - GND
As I could not get RC0 and RC1 to output anything,
I changed to DC - RC6 and CS - RC7 and it popped to life.
Notice the markings around < RCO > and < RC1 > . That is different to the other CPORT pins. What it means I do not know.
I tried fiddling with the clock register, but no luck. I don't really know the source of the problem...
Here is a small program that plots on screen and should blink on PortC.0 and PortC.3.
PortC.0 is not an output and does not blink. It seems it is not connected as a general output port. a 10k resistor to VCC and it goes high.
C.3 blinks as expected.
News. PIC16F175xx.
Adding 12 new PICs. Microchip have actually added new PICs. I honestly thought that 8-bit PIC development had ceased. Well I got that wrong.
Also, adding the following to PICKitPlus.
Support for 9 new devices to be added:
PIC16F17524
PIC16F17525
PIC16F17526
PIC16F17544
PIC16F17545
PIC16F17546
PIC16F17554
PIC16F17555
PIC16F17556
and,
PIC16F17574
PIC16F17575
PIC16F17576
If you build does not have these specific chips installed, please see https://sourceforge.net/p/gcbasic/discussion/579125/thread/4c55902b1b/
Last edit: Anobium 2025-12-10
New chipdata files for PIC16F175xx. These are not validated but they will work.
PIC16F17524
PIC16F17525
PIC16F17526
PIC16F17544
PIC16F17545
PIC16F17546
PIC16F17554
PIC16F17555
PIC16F17556
PIC16F17574
PIC16F17575
PIC16F17576
Apply using GCSTUDIO and this will be automatically installed.
Last edit: Anobium 2025-11-30
Hi,
I did the update, but the compiler says:
Error: "No chip data file found for 16F17576"
The same with 16F17524.
I got the "Finishing update..." etc, but no new chips.
GCstudio 17.6.2 Win11
Last edit: Roger Jönsson 2025-12-09
Update with the MPk for your chips. That will load the chip dat files
I took the mpk...1525 in the message above and it seemingly got installed. It ended with "Finishing update..." I tried twice. Are you talking about something else?
Give me a hour. I will check that mpk.
I fiund another 1525 mpk and installed it: mpk_build_1525_16F175xx_chipfilles.mpk
It seems to compile the PIC16F17576.
Excellent. I thought I had updated that MPK. Thanks for patience.
Angel is working on a new release with all these updates. The new release is a huge step forward. It has full support for debugging. I am using the re-release version and the debugger and it is so easy to use.
I found it here: https://sourceforge.net/p/gcbasic/discussion/579125/thread/4c55902b1b/
PIC16F17576 is not in the PPS TOOL etc.
Is that to be expected?
Someone needs to update the PPS configuration files for the complete chipfamily. I have done this for the 16F17556 ( which I am using ). You could use that as the 76 is a similar layout.
I'm not seeing any of these new chips in the PPS tool (including16F17556). So there must be something else missing in my setup.
There is no hurry from my side, I just want to have things setup for later when I get some time off.
I don't know if these should turn up in PICInfo, but they don't. Not one 16F175XX.
You need the new (today updated) MPKs as you are running ahead of the release baseline code.
mpk_build_1528_PICInfo_Update.mpk - https://1drv.ms/u/c/2f87ffe77f3dbec7/IQB7SjB06AJTTJ3i_t7NlSQmAZzhpUFaZfVHzRzphGpS5Os?e=vwnLlD
then, you need https://1drv.ms/u/c/2f87ffe77f3dbec7/IQAlL1eMOdY1S53EpfOwwX7nASjDEqlpm3RgNoSBFNU8D6c?e=heFZPV This has a PICINFO support file.
and, the you need the attached file ( because I have not had time to create an MPK. Put in the C:\GCstudio\ppstool\devices folder.
I am working with Microchip regarding PICINFO. Microchip have a broken datafeed. PICINFO will failback to a local copy of the Microchip datafeed - so, hopefully this keeps access to datasheets etc operational. Essentially, we are working around Microchip issues.
We are working flat out to get the new release out - I need to complete the 16F175xx tutorials as these validates the GCBASIC toolchain. See https://www.youtube.com/playlist?list=PLN9gcw34mhupJx5YotmF0Ao9O63EbQMFf Only 8 more videos to make!!
Looks good!
I just received my SSD1331 in the mail today and here came a new tutorial with that one! -Wow! -What a coincidence!
Just producing the PWM videos ... be there soon. :-)
I can't get the 16F17576 to work with neither software SPI to GLCD nor software i2C to GLCD.
A LED Blinky works on C.4 and C.5, so the ports are alive.
I'm using a 16F17576 curiosity nano board.
I don't have this demo saved in GCbasic (PT13: PIC16F175xx chip Family - Using SPI and a GLCD) and I don't know where to find it.
I found a similar one with a different number 260:
https://github.com/GreatCowBASIC/Demonstration_Sources/blob/main/Vendor_Boards/Great_Cow_Basic_Demo_Board/16F17556_chiprange_demonstrations/260_spi_glcd_using_SSD1331.gcb
It used mixed PortA and PortC, so I changed it to what you used in the demo and set the chip to 16F17576 because that is what is on my curiosity board.
It starts off black for 4-5 seconds, then
blue, red, blue, red, blue...mainly yellow, then a scoll of some pattern then it goes black, once now and then it flicker, flashes some random mess and then black again.
Softare spi is about the same as hardware spi, but slower.
Since this didn't work I tried a simple GLCD_TYPE_SSD1306_64x32 software i2Cprogram with that screen on the same PORTC.4 and C.5.
No reaction.
Then I tried blinky on PORTC.4 and C.5. It works.
Maybe I was a bit early trying out this chip?
Switching over to my other new curiosity nano board 18F57Q84. Now the demo program works on SSD1331.
So far only with software SPI. No luck with hardware SPI.
I did setup the PPS for this chip, but I don't know if there are other limitations that I'm not aware of.
Last edit: Roger Jönsson 2025-12-14
This is not a chip support issue for either chip. The chips has passed all the tests here.
Re the Q84. If software SPI works and hardware SPI fails then PPS is incorrect.
You have selected the clock for I2C and the SDO for SPI.
Should be
~~~
// PIC PPS Tool version: 0.0.6.5
startup InitPPS, 85
define PPSToolPart 18F56Q84
Sub InitPPS
// Add this code segment to your GCBASIC source program
~~~
I now got the 16F17576 to work. It turns out RC0 and RC1 is not connected (no blinky on them) so I changed to other pins. They are marked <rc0> and <rc1>. I don't understand if there is something I should have done as these are also SOSCI or SOSCO or if there is something that should be set somewhere for this chip.</rc1></rc0>
18F56Q84 is now also working. It was way past bedtime and I should just have given it (and me) a rest or I could have read what the PPStool returned. I would then have seen my mistake in selecting SCL instead of SCK. Sorry about that.
I am using RC0 and RC1 in all the tests, so, upload a photo of your chip and overall layout.
I used:
GLCD SSD1331 - 16F17576 (curiosity nano board)
CS - RC1
DC - RC0
RES - RC2
SDA - RC5
SCL - RC4
DCC - VTG
GND - GND
As I could not get RC0 and RC1 to output anything,
I changed to DC - RC6 and CS - RC7 and it popped to life.
Notice the markings around < RCO > and < RC1 > . That is different to the other CPORT pins. What it means I do not know.
Last edit: Roger Jönsson 2025-12-14
I tried fiddling with the clock register, but no luck. I don't really know the source of the problem...
Here is a small program that plots on screen and should blink on PortC.0 and PortC.3.
PortC.0 is not an output and does not blink. It seems it is not connected as a general output port. a 10k resistor to VCC and it goes high.
C.3 blinks as expected.
In the board design files https://ww1.microchip.com/downloads/aemDocuments/documents/MCU08/ProductDocuments/BoardDesignFiles/Curiosity-Nano-Explorer-Pinouts.pdf
the RC0 and RC1 are within parentheses. Does that say something?