Hello,

error: 'port' undeclared (first use in this function)

It sounds like your display component may have unconnected pins. Check the properties of the component on the panel.

Hello, This is how we configure the clock for our dsPIC E-block board. You could do something similar using a C icon at the start of your program. //Setup configuration for 70MIPs using 8MHz Crystal PLLFBD = 68; // M=70 CLKDIVbits.PLLPOST = 0; // N1=2 CLKDIVbits.PLLPRE = 0; // N2=2 OSCTUN = 0; //Tun...

Hello, Yes the Flash EEPROM is the component you need. The properties for the component should allow you to choose a page in flash memory to assign to store the data. There are then two functions read and write which allows you to read and write a 16-bit value from a 0 indexed location. If you are h...

Hello, If you ever need to know the specifics for a PIC device then the easiest way is to look at the .h file in the compiler pic/include/ directory. For example for the 16F877A I looked at the pic16F877a.h file. Then search the file for the register your interested in, here is the section for the O...

Aha well done, yes that is suprising but good to know.

I can maybe add that into the SPI CAL component so it does that for you before initialising the SPI.

Hi Jorg,

Looking at the code the return 0x800000 means the data is not ready.

Maybe try calling the Forced_Read function before you call the ReadXxx macro and hopefully that will help.

Brilliant thanks Martin, For some reason - hardware SPI doesn't always work on an Arduino AVR has a rather perculiar setup for SPI. When SPI is enabled if the hardware SS pin if left as an floating input or pulled low then this acts as a trigger to allow the SPI to go into slave mode. When this happ...

Hello Jorg,

Many thanks for letting us know.

I beleive I've now solved the problem for you and the latest component should now be available via the library updates.

Hello, I did have another go on Friday and over the weekend. I went through the register initialisers from the library I was using and compared them to the datasheet and they were all over the place in terms of either not matching up the correct number of parameter bytes or calling functions that we...

Hello,

With the I2C timing problem you've highlighted. Please can you confirm the target MCU you're using and also the I2C channel you're using and I'll investigate for you.