Search found 40 matches

That seems to have solved the issue for the most part. I'm still getting the occasional erroneous reading, but no where near the amount I was getting before.

void write_ee(int8 v1, int8 v2) // Overloaded (int8 version)
{
write_eeprom(v1, v2); // location, data
fClear();
}

void write_ee(int8 v1, int16 v ...

Having to do modifications to someone else's code is always a difficult job. In this situation you are really unlucky as it looks like the code was written by a beginner.
Well the previous coder was ...

I'm using compiler version 4.016 and the 2401.c that comes with it, unmodified.

The reason I have a the ext_eeprom_ready tests is so that if the chip isn't ready to receive, it would just loop inde ...

I'm attempting to create a backup routine to store values from and then restore to my EEPROM, by using a 24LC01B external chip.

However, I'm getting erroneous 0xA0 and 0xA1 (the start and stop bits ...

Ok, let me explain.

As I said in my opening post, I have a 3 digit, 7 segment display. Now, I can display any number of characters to it, and have a working menu system that makes use of four push ...

That code appears to be written to make use of an LCD.

I don't understand what you mean by modal. The hardware for this menu I understand, it's simply the software that I'm having some concerns about, since my switch statement becomes quite elaborate, wit ...

I have a display comprised of a 3 character, 7 segment display. The UI i'm building into the product at the moment is based around a switch/case statement, where, by pressing a button, a value increme ...

After some more digging, and excessive use of the simulator, I've narrowed my problem down to one command, in so far as I can tell.

void fIncrement(signed int16 vPrimary, signed int16 vCPrimary ...

signed int16 v1;
int16 *v2 = &v1 ;

v1 = -1;

So *v2 is really a pointer.
v2 contain the addresses of v1.
*v2 give the value of v1;

What you've written above should be r ...

Even if i use it as an int16, it still loses the leading 8 bits of the data.

What I think is happening, is the contents is being cast to an int8, and then recast to an int16.

I'm currently dealing with some pointers and I've ended up with the following scenario:

Variable v1 is a signed int16, and contains -1 or 11111111 11111110.
Variable v2 is a signed int16 also.

...

Whilst the code you posted allows me more flexibility when it coems to handling different data types, my grasp of C isn't enough for me to totally understand what you wrote.

So it may be more versa ...

The application is thus:

I'm writing a subroutine which handles increments in a range for a temperature sensing and handling unit.

The subroutine works for both fahrenheit and celsius scales, be ...