View previous topic :: View next topic |
Author |
Message |
SkeeterHawk
Joined: 16 Oct 2010 Posts: 31 Location: Florissant, CO
|
Programming Error - UNKNOWN OPTION: parent=723518 |
Posted: Wed Jun 07, 2023 6:56 pm |
|
|
Hello fellow programmers:
I am getting an unusual error when I am trying to program my PIC18F57Q84. It gives the message that I put in the remark line.
Code: |
#include <RegenModule_Config.h>
// Global variable declarations
int Flags = 0, // Register used to keep track of where we are in the program
DisplayFlags = 0, // Register to help keep the different displays "on trac"
LED_Blink = 1, // Register that only uses one bit to make the LED blink
CountdownTimer = 0; // Register that the RTC interrupt routine decrements
//signed int8
//int16
// Other useful Regeneration Module specific functions, definitions and such
#include <RegenModule_I-O.h> // Pin assignments for the IO on this board
//#include <Flex_LCD.c> // LCD Driver for the display
//#include <internal_eeprom.c> // Driver to be able to save above 8-bit values to the internal EEPROM
//#include <RegenModule_Displays.h> // This is the file that holds all of the displays for the system
//#include <RegenModule_Subroutines.h> // Various and assorted functions to keep things moving along
void main()
{
while(TRUE)
{
Output_low(LED_Green);
Output_low(LED_Red);
Output_high(LED_Red);
//TODO: User Code
}
}
|
Here is what is in the "config" file and "I/O" files respectively, which is the only include files:
Code: |
#include <18F57Q84.h>
#device ADC=12
//#FUSES NOWDT //No Watch Dog Timer
#use delay(internal=32000000)
#pin_select SCK1IN=PIN_C3
#pin_select SDI1=PIN_C4
#pin_select SDO1=PIN_C2
#use spi (SLAVE, SPI1, MODE=0, BITS=8, STREAM=SPI_1)
// Definitions for the local I/O pins as specific to the Regen Module application.
#define Analog_SignalIn PIN_A0
#define Aux_Analog PIN_A1
#define Encoder_CS1 PIN_A2
#define Encoder_CS2 PIN_A3
#define Encoder_CS3 PIN_A4
#define Encoder_CS4 PIN_A5
#define Multiplexer_CS PIN_A6
#define RTC_CS PIN_A7
#define SW_Center PIN_B0
#define SW_Left PIN_B1
#define LocalSPI_MISO PIN_B2
#define LocalSPI_CLK PIN_B3
#define LocalSPI_MOSI PIN_B4
#define Aux_IO_1 PIN_B5
//#define ICSP_Programming_Clock PIN_B6
//#define ICSP_Programming_Data PIN_B7
#define LED_Red PIN_C0
#define RTC_INT PIN_C1
#define PumpMasterSPI_MISO PIN_C2
#define PumpMasterSPI_CLK PIN_C3
#define PumpMasterSPI_MOSI PIN_C4
#define LCD_RW PIN_C5
#define LCD_RS PIN_C6
#define LCD_E PIN_C7
#define PumpMaster_CS PIN_D0
#define LED_Green PIN_D1
#define LED_Blue PIN_D2
#define Aux_IO_3 PIN_D3
#define LCD_DB4 PIN_D4
#define LCD_DB5 PIN_D5
#define LCD_DB6 PIN_D6
#define LCD_DB7 PIN_D7
#define LocalSerialOutputClock PIN_E0
#define LocalSerialOutputData PIN_E1
#define Aux_IO_2 PIN_E2
#define SW_Right PIN_F0
#define LocalSerialOutput_HighShiftOut PIN_F1
#define LocalSerialOutput_ShiftOut PIN_F2
#define LCD_Backlight PIN_F3
#define StepperOutput1 PIN_F4
#define StepperOutput2 PIN_F5
#define StepperOutput3 PIN_F6
#define StepperOutput4 PIN_F7
|
I pulled out just about every include that wasn't being used yet, just to get rid of the possibilities. Is this something with the include file for the chip? I can't eliminate that one.
Thanks so much for the input!! I tried two different boards and got the same result, so this is definitely something with the software.
Thanks again! ![Very Happy](images/smiles/icon_biggrin.gif) _________________ Life is too short to only write code in assembly... |
|
![](templates/subSilver/images/spacer.gif) |
temtronic
Joined: 01 Jul 2010 Posts: 9168 Location: Greensville,Ontario
|
|
Posted: Wed Jun 07, 2023 8:00 pm |
|
|
Maybe go back to the basic, simple, 'toggle an LED at 1Hz' program ??
If that works, build up from there ?? |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Wed Jun 07, 2023 11:11 pm |
|
|
Critical unsaid thing here _compiler version_?. |
|
![](templates/subSilver/images/spacer.gif) |
SkeeterHawk
Joined: 16 Oct 2010 Posts: 31 Location: Florissant, CO
|
|
Posted: Wed Jun 07, 2023 11:28 pm |
|
|
Ttelmah wrote: | Critical unsaid thing here _compiler version_?. |
Great question. Sorry for not posting
It is version 5.114. _________________ Life is too short to only write code in assembly... |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Thu Jun 08, 2023 12:53 am |
|
|
The other thing I should have asked is 'which programmer'?.
I suggest the first thing to do is try running the programmer separately.
So assuming it is a CCS programmer, run CCSLoad. Try programming from
this. You may well then get an error message that is more informative. |
|
![](templates/subSilver/images/spacer.gif) |
SkeeterHawk
Joined: 16 Oct 2010 Posts: 31 Location: Florissant, CO
|
|
Posted: Thu Jun 08, 2023 2:24 am |
|
|
Ttelmah wrote: | The other thing I should have asked is 'which programmer'?.
I suggest the first thing to do is try running the programmer separately.
So assuming it is a CCS programmer, run CCSLoad. Try programming from
this. You may well then get an error message that is more informative. |
That was a great suggestion! Thank you! Yes, this is a CCS ICD-U64. I will make sure that it's firmware is updated and give it a try in the morning.
Thanks again for the feedback!
Jonathan _________________ Life is too short to only write code in assembly... |
|
![](templates/subSilver/images/spacer.gif) |
SkeeterHawk
Joined: 16 Oct 2010 Posts: 31 Location: Florissant, CO
|
|
Posted: Thu Jun 08, 2023 1:33 pm |
|
|
I have an update to this thread that I would like to share.
It turns out that I had to update the CCS Loader software as well as updating the firmware on the programmer. When I tried to program it using the CCS Loader as @Ttelmah suggested, it did give more information, by throwing up a TON of error windows on top of each other. I had to force it to shut down from Device Manager. Going back in, I tried to manually select the PIC18F57Q84 to get it started, and it wasn't on the list. That was my clue. I updated everything about my ICDU64, and it will now program without the error. The code still isn't acting right, but that is what "debugging" is for.
Thank you SO MUCH for your input!! I am no longer "dead in the water", woo hoo!! _________________ Life is too short to only write code in assembly... |
|
![](templates/subSilver/images/spacer.gif) |
Ttelmah
Joined: 11 Mar 2010 Posts: 19358
|
|
Posted: Fri Jun 09, 2023 1:47 am |
|
|
Grin.
It looks like we may now know that parent=723518, is code for a particular
version of 'device not supported'....
Now for your debugging.
Worth being aware, that some of those newer chips have complexities like
slew rate limiting on the pins, and open collector drives. Worth checking if
the chip has these, and if so, that they are correctly setup before trying
to do I/O.... |
|
![](templates/subSilver/images/spacer.gif) |
|