Search found 21 matches

The moderator believes your new question to be still on this topic and duly locked the new thread.

I did not understand your 'new' question at all.

Can you kindly re-phrase and post again.

Mi ...

In a previous thread, I asked about the proper form of the I2C slave

++++++++++++++++++++++++++
Locked.

Reason: Duplicate thread on same i2c slave topic.
No posting of new thread every day ...

This forum became worthless over the past ten years. I'm removing my useful code example.

Simplifying #use i2c(slave,sda=PIN_C4,scl=PIN_C3, address=0x30, FORCE_HW)

// create bits for the status items for I2C
#byte SSPSTAT = 0x214 // register address specific to processor
# ...

if(state >= 0x80) //Master is requesting data
{
i2c_write(buffer[address++]);
}

picture of a frame: http://www.80 ...

In the example code for I2C slave, only one byte is read per I2C frame.
ex #INT_SSP
void ssp_interupt ()
{
BYTE incoming, state;

state = i2c_isr_state();

if ...

LIMITS
// ->Data cannot be accesses through the 0x7FFF-0x8000 point. That is that
// all write/read data must be contained within 0x0000-0x07FFF or
// 0x8000-0xFFFF.
// ->Data is not ...

I'm new to PIC programming and have little knowledge.
Thanks.

Read the data sheet for the PIC in its entirety and understand the programming, register, and control architecture. Untill you know ...

Hey buds, its been a while and this code has generated lots of questions. Let me see what I can address here.

First of all, I need to remind you that you need to have a good idea of what goes on in ...

That's cool!

The first assignment in my embedded system design class was just like this.

So, I will be using 4x PLL on a 10 MHz crystal to get 40MHz. The question is: does the new project wizard take this x4 factor into account or am I supposed to type "40,000,000" into the frequency box ...

I think this is a simple question:
I use MPlab version 7.x with the CCS compiler. So I have a project set up with all of my source files and header files. The problem is that when I click complile, ...

This is the driver I wrote for a 512 Mbit (64 Kbyte) microchip i2c EEProm. to be best of my simple testing, it works, as I have used it for a few simple tasks. the chip I used had a 64 byte buffer.
...

but a pointer is a pointer, right?

then wouild this work?:

int16 send_in(char* data, int16 len)
{
char k;
signed int16 size;
int32 wr_ptr, ack_ptr;
int16 address;
...

when send-in calls writenetwork, data should have the value of 0x015F (the location of wr_ptr), however it gets the value 0x0020.

compiler Version 3.207 target chip 18F452

(also, I know that e ...