That library set is for the v0.98.02 (minimum). We are in the last few weeks prior to release. Hence, it does not work. And, this is my development area forlibraries which are not supported.
So, do you have a MicroChip Curiorsity Board?
Add, this to USART.h in the interim fix (as SourceForge is under maintenance at the moment).
sub HSerPrintStringCRLF (In PrintData As String, optional In comport = 1)
'PrintLen = LEN(PrintData$)
PrintLen = PrintData(0)
If PrintLen <> 0 then
'Write Data
for SysPrintTemp = 1 to PrintLen
HSerSend(PrintData(SysPrintTemp),comport )
Wait USART_DELAY
next
End If
If you have a Microchip Curiorsity Board please test the library, take a photo and post the results.
I ported the Microchip Curiorsity Board demonstration code but I do not have a Microchip Curiorsity Board but I can think of no reason why the library will not work.
Let me know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's the ticket, GCB example code compiles fine now, however ...
Checking my fresh, still in the box Curiosity, the actual chip shipped with the retail product last year was a PIC16F1619. Compiling for this chip gives me this error...
09:23:55 G+Stool-COMPILE/ASSEMBLE, processing C:\GCB@Syn\G+Stools\makeHEX.bat
Source-File = C:\Users\randa\Desktop\Great-Cow-BASIC-Library-Development-master\CuriorsityBoard\CuriorsityBoardDemo001.gcb
13.4 Sec. <<< WARNINGs / ERRORs while compiling!
Doubleclick on errormessage below to go to sourcecode-line:
CuriorsityBoardDemo001.gcb (555): Error: Variable WDTCON was not explicitly declared
Please advise.
Last edit: Randall Young 2018-02-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did some general prep work with the Microchip C demo code, which compiled and ran without issue, and seems to share exactly logic that you reflected in your project. If need be, I can order the correct part from Digikey, which I am happy to do, but unfortunately I am on holiday next week, and will be away from my lab accordingly.
I also took a moment to review your program, what a nice demo!
Very interesting to compare the clarity and simplicity of the GDB program vs. the C analog. The example code from Microchip covers product all way from the PIC16F15xx, to PIC16F183xx variants. If you would like to test/adapt your code to all the possibilities, just let me know what to get for testing purposes.
I think this is easy to update for the full range of chips. Get a range of chips, so we can test. I have already resolve the 16f1619 issue - caused by different registers on this chip but easily resolved.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have updated the demo - I have added a check for PPS and nonPPS chips, HEFM memory and EEProm chips (I have not sorted the EEPROM, but, this is relatively simple).
I would like to have one demo for a very wide set of chips.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The new code built fine, but upon programming (from MplabX by way of teh PKOB) I get this error messaage in responese... (building for PIC16F1619)
Connecting to Starter Kit on Board...
Currently loaded firmware on Starter Kit on Board
Firmware Suite Version.....01.51.06
Firmware type..............dsPIC33F/24F/24H
Now Downloading new Firmware for target device: PIC16F1619
Downloading AP...
AP download complete
Programming download... The low voltage programming feature requires the LVP configuration bit to be enabled on the target device. Please enable this configuration bit and try the operation again.
IPE gives me the same message.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Setting up to debug serial output, just two wires to send data from Curiosity to the cp2102 USB2TLL adapter.
I'm using MplabX's IPE to burn a specific hex file to the PKOB programmer on the board, be sure to activate the admin mode by typting the password "microchip", to enable the controls to program the chip.
Anyone got a MicroChip Curiorsity Board ?
If yes, let me know. Can you test the code at the URL below?
https://github.com/Anobium/Great-Cow-BASIC-Library-Development/tree/master/CuriorsityBoard
Anobium
Hi!,
I'm catching an error here ...
makeHEX.bat
Great Cow Basic Pre-processing (v0.98.00)
Great Cow BASIC (0.98.01 2017-10-27)
Compiling C:\Users\randa\Desktop\Great-Cow-BASIC-Library-Development-master\CuriorsityBoard\CuriorsityBoardDemo001.gcb ...
Errors have been found:
CuriorsityBoardDemo001.gcb (71): Error: Syntax Error
CuriorsityBoardDemo001.gcb (79): Error: Syntax Error
The message has been logged to the file Errors.txt.
HSerPrint ... CRLF seems to be a problem?
...
That library set is for the v0.98.02 (minimum). We are in the last few weeks prior to release. Hence, it does not work. And, this is my development area forlibraries which are not supported.
So, do you have a MicroChip Curiorsity Board?
Add, this to USART.h in the interim fix (as SourceForge is under maintenance at the moment).
sub HSerPrintStringCRLF (In PrintData As String, optional In comport = 1)
'PrintLen = LEN(PrintData$)
PrintLen = PrintData(0)
If PrintLen <> 0 then
'Write Data
for SysPrintTemp = 1 to PrintLen
HSerSend(PrintData(SysPrintTemp),comport )
Wait USART_DELAY
next
End If
HSerSend(13,comport)
Wait USART_DELAY
HSerSend(10,comport)
Wait USART_DELAY
End Sub
If you have a Microchip Curiorsity Board please test the library, take a photo and post the results.
I ported the Microchip Curiorsity Board demonstration code but I do not have a Microchip Curiorsity Board but I can think of no reason why the library will not work.
Let me know.
Hello,
Yes I do have several, and a free day tomorrow, I will keep you posted.
R.
That's the ticket, GCB example code compiles fine now, however ...
Checking my fresh, still in the box Curiosity, the actual chip shipped with the retail product last year was a PIC16F1619. Compiling for this chip gives me this error...
09:23:55 G+Stool-COMPILE/ASSEMBLE, processing C:\GCB@Syn\G+Stools\makeHEX.bat
Source-File = C:\Users\randa\Desktop\Great-Cow-BASIC-Library-Development-master\CuriorsityBoard\CuriorsityBoardDemo001.gcb
13.4 Sec. <<< WARNINGs / ERRORs while compiling!
Doubleclick on errormessage below to go to sourcecode-line:
CuriorsityBoardDemo001.gcb (555): Error: Variable WDTCON was not explicitly declared
Please advise.
Last edit: Randall Young 2018-02-16
I did some general prep work with the Microchip C demo code, which compiled and ran without issue, and seems to share exactly logic that you reflected in your project. If need be, I can order the correct part from Digikey, which I am happy to do, but unfortunately I am on holiday next week, and will be away from my lab accordingly.
I also took a moment to review your program, what a nice demo!
Very interesting to compare the clarity and simplicity of the GDB program vs. the C analog. The example code from Microchip covers product all way from the PIC16F15xx, to PIC16F183xx variants. If you would like to test/adapt your code to all the possibilities, just let me know what to get for testing purposes.
Last edit: Randall Young 2018-02-16
Thanks for feedback.
I think this is easy to update for the full range of chips. Get a range of chips, so we can test. I have already resolve the 16f1619 issue - caused by different registers on this chip but easily resolved.
I have updated the demo - I have added a check for PPS and nonPPS chips, HEFM memory and EEProm chips (I have not sorted the EEPROM, but, this is relatively simple).
I would like to have one demo for a very wide set of chips.
Here's a list of 20 pin, DIP 16F1XXX,X devices, for reference.
The new code built fine, but upon programming (from MplabX by way of teh PKOB) I get this error messaage in responese... (building for PIC16F1619)
Connecting to Starter Kit on Board...
Currently loaded firmware on Starter Kit on Board
Firmware Suite Version.....01.51.06
Firmware type..............dsPIC33F/24F/24H
Now Downloading new Firmware for target device: PIC16F1619
Downloading AP...
AP download complete
Programming download...
The low voltage programming feature requires the LVP configuration bit to be enabled on the target device. Please enable this configuration bit and try the operation again.
IPE gives me the same message.
Yes, this would happen, in you version of Great Cow BASIC. We need to add LVP=ON to the config. Just added LVP support. Try now.
I will be good to go with these chips the week after ...
PIC16F15345-I/P-ND PIC16F15345-I/P IC MCU 8-BIT 14KB FLASH 20DIP
PIC16F18345-I/P-ND PIC16F18345-I/P IC MCU 8BIT 14KB FLASH 20DIP
PIC16F1829-I/P-ND PIC16F1829-I/P IC MCU 8BIT 14KB FLASH 20DIP
Looks a good list.
Setting up to debug serial output, just two wires to send data from Curiosity to the cp2102 USB2TLL adapter.
I'm using MplabX's IPE to burn a specific hex file to the PKOB programmer on the board, be sure to activate the admin mode by typting the password "microchip", to enable the controls to program the chip.
Clunky but workable...
Last edit: Randall Young 2018-03-04
Here is my current CONFIG setup:
Note I am 16 mhz, not .5 ???
Last edit: Randall Young 2018-03-04
Nice post. Keep up the great work.