Search found 32 matches

Agreed, this error is usually caused by a curly bracket missing in the previous function.

Because of a compiler directive oversight, the #int_rda2 was never being called and the default interrupt handler was being called instead.

Compiler Version 4.120

I am using a PIC33FJ256GP710 device and when it is sent a character on the serial port (UART2) the device will reset during the reset cause as RESTART_TRAP_CONFLICT.

The UART is set up as a stream: ...

Thanks for the tip, it turns out that the SPI module must be disabled before the mode is changed.

Updated the code and the result to show the value before writing....

I am trying to write the SPI2CON1 register, and it is not accepting the value written to it:

#fuses XT, PR_PLL, NOCOE, NOWRTB, NOPUT, NOWRTSS, NOPROTECT, NORSS, NOWDT, NOWINDIS

#FUSES NOWRT ...

Found a workaround,

It seems that as long as I do not call spi_setup() or spi_setup2() anywhere in the code then it works fine with manually setting the bits and enabling the hardware. The spi_read ...

int8 i8_digit1, i8_digit2, i8_digit3, i8_digit4;
int16 i16_sourcenumber = 0xABCD;

i8_digit1 = (int8)( i16_sourcenumber & 0x000F );
i8_digit2 = (int8) ...

Hmm... Still no go even when configuring the registers directly. Weird thing is that it is working if changed to SPI1, but does not seem to have an effect on SPI2 no matter what configuration bits are ...

Have you considered getting Microchip to load in a boot loader?

Then you can use USB / Serial to program the units on the production line, and if your application changes, it's easy to just start p ...

Thanks!

I'll give it a try here and let you know what happens.

I am having an issue with the idle clock level during the SPI setup, code used to initialize and send a character is below. When initialized, the idle clock level stays low.

//******************* ...

I see that the pic is continually resetting

And a reason for you saying WHY you think it is continually resetting would be helpful as well...

ie: "I see that the pic is continually resettin ...

Think I know what you mean... You can use the Timer to generate an interrupt every second and then call your scanning routine from the interrupt.

See the CCS example files for the timer code exampl ...

With respect to:

ON(LEDR);
Delay_ms(1000);
OFF(LEDR);

Does the LED change state at powerup?

If you meter the pins to the PIC, can you see the signal changing?
...