Interpret to Picbasic Code ¿?!!

[Dave]

Well, I'm no C wisard but the lines 114,115 are defines for what looks like 2 variables called "msb" and "lsb". These are defined as unsigned 8 bit variables. Now with out any more code I can only quess that line 120 is taking the "msb" variable and doing a left shift 4 places and adding the "lsb" variable being right shifted by 4 places together then placing the result into "chip->vcell". Thats my take on it...

[Ryan7777]

It's been a while, but I'd agree about

u8 msb;
u8 lsb;

as being declarations of those variables in each function and what they will hold.

Those whole thing just looks like it's reading in I2C data, and maybe swapping the bit order?

Man, it's been so long since I had to work with something like that.

[Art]

chip->vcell = (msb << 4) + (lsb >> 4);

This is already basic on the right side of the equal sign,
on the other side it’s addressing an element of a structure (a list)
which can be done with any PBP array with a variable index like:

var word vcell
var byte/word chip[size]

...

chip[vcell] = value or sum

I don’t know why they are doing it, the four bytes that roll off each end would be discarded in both languages (not carried).

For both of these, this is a call to a function (subroutine in basic):

msb = max17040_read_reg(client, MAX17040_VCELL_MSB);

You have not posted the function, but I assume it’s the lower level I2C function (I2CREAD/WRITE...).

The parameters in brackets are arguments passed to the function as input which would be the address.
The return value is when is written into the value to the left of the equal sign for calling the function.
The basic subroutine would read a variable for the EEPROM address that was set by the main loop,
and set another variable with the result data, later read by the main loop that called the subroutine.

In PBP the I2C commands would probably be just the same written inline with the main program loop.
In the C code the functions might be an eyesore to throw at the bottom of your page.