Hallo
Thank you for your great work, and the website
i have downloaded the files and followed your advices in !info.txt
my question now:
i have replaced
i2c.c and i2c.h in
/devboard-R2_01/os/linux-2.6/arch/cris/arch-v10/drivers
and
etraxi2c.h in
/devboard-R2_01/os/linux-2.6-tag--devboard-R2_01/include/asm-cris/etraxi2c.h
with your new files right ?
done: configure and make
flash the board with option -f , restart, OK.
but on next cat: no i2cdynamic, still i2cgvc
Do i have to :
-----------snip---------------
Summary
* Rename the following files:
/devboard-R2_01/packages/filesystem-R1_2_1/Makefile
into
/devboard-R2_01/packages/filesystem-R1_2_1/Makefile-original
..
-----------snip---------------
from the wiki site, isn't that done with the actions from !info.txt ?
when i run my programm it comes to the line
--------------snip---------------------
void writePCF8574(int pout)
{
printf( "Dev: - Action: writePCF8574 : %i \n", pout );
unsigned char pcf8574value = 0x05;
I2C_DATA i2cdata_pcf8574;
struct timespec pcf8574_tv;
/* 1 sec */
pcf8574_tv.tv_sec = (time_t)1;
pcf8574_tv.tv_nsec = (long)0;
i2cdata_pcf8574.slave = 0x40;
i2cdata_pcf8574.wlen = 1;
i2cdata_pcf8574.wbuf[ 0 ] = 0xF0;
if ( EI2CNOERRORS != ioctl( fd_i2c, _IO( ETRAXI2C_IOCTYPE,
I2C_WRITE ), &i2cdata_pcf8574 ) )
---------------snip--------------------------
i get this error:
# IRP: c00f1920 SRP: c00f1caa DCCR: 00000400 USP: 9fa9bc1c MOF: 00000000
r0: c01863a4 r1: 00000007 r2: b0000038 r3: c01863a4
r4: c01863a4 r5: 00000003 r6: b0000038 r7: b0000038
r8: 00000034 r9: 0000008e r10: 00000065 r11: 00000031
r12: 00000002 r13: 000000c4 oR10: 00000065 sp: c1a99c04
R_MMU_CAUSE: 355f3001
Process i2cgvct (pid: 112, stackpage=c0452540)
Code: c2 cb 6b d6 c2 d3 6d 96 06 30 81 92 (ff) 20 81 92 4c 96 3d 93 c0
9b c2 9b
-----------------------------------------------------
Also i get an error
i2cexamplegvc.c:9:27: error: asm/i2c_errno.h: No such file or directory
i2cexamplegvc.c:10:26: error: asm/etraxi2c.h: No such file or directory
when i try to compile the sample.
so i use the headers local, ok ?
and the option I2C_USES_PB_NOT_PB_I2C
where do i set this? where is the right config.in ?
and is it right you use pins
PB6 (pin 38-J6) pin 1 <-> SDA (pin 1)
PB7 (pin 37-J6) pin 2 --> SCL (pin 2)
when the option is set ?
i hope the questions are not to stupid,
but after tracking down this i2c issue from bitbang to this
i am a bit tired, confused, and on time pressure.
i am not a pro (now ;) in advanced linux mechanics.
cat /proc/devices
i get a device i2cgvc
in the list. and on dmesg there is:
I2C driver v2.2, (c) 1999-2004 Axis Communications AB
==> Improvements done by Geert Vancompernolle - December 2006
I2C Major: 123 / I2C Name: i2cgvc
I assume thats not your updated driver ? (Date)
which headerfiles do i use to compile for this driver ?
best regards
werner
--- In [email protected], "Geert Vancompernolle"
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> As I mentioned a while ago (see thread
> http://tech.groups.yahoo.com/group/foxboard/message/3020), I was busy
> studying and possibly trying to improve the current version of the I2C
> driver.
>
> Well, I've just finished reworking the I2C driver. The changes are
> quite drastical. The changes result in a faster driver and now it can
> cope with all possible cases (at least, the ones that I know of...).
>
> The driver has been tested on several I2C components (see further) and
> there are more to come...
>
> I've created a zip file that contains the following items:
>
> - a PDF file describing the changes, showing DSO plots and giving in
> detail the timings of the current I2C implementation.
>
> - a new I2C error header file i2c_errno.h (see PDF file for some
> explanation)
>
> - the changed i2c.h header file
>
> - the changed etraxi2c.h header file
>
> - the new I2C source file
>
> - an example file which has been used to test the I2C driver on the
> following devices:
> * NVM 24C32
> * PCF8574
> * PCF8591
>
> - Makefile to use for the example code.
>
> - switches header file to activate one or more of the tested components.
>
> Those interested can have a look over here:
>
> http://tech.groups.yahoo.com/group/foxboard/files/GeertVc
>
> All suggestions/improvements/remarks are welcome.
>
> I would especially ask John Crispin to have a look at the driver (John
> knows what I'm talking about...)
>
>
> Best rgds,
>
> --Geert
>
