Hi Geert, I tried the I2C driver again. Now I have no problem any more, no more crashes can be observed. All I did was to make a new fimage, and now I get from I2C_WRITE the error EI2CBUSNFREE, which is correct, because up to now I have no I2C slaves connected to the foxboard.
I am sorry for the confusion, and I cannot explain what changed between my old and new fimage. At least I cannot tell anything about relevant changes, all I did was to add one directory- and one file- command to the post file. I am pretty sure now, that the kernel crash problem has nothing to do with your code, sorry for that. .................... Thomas Am 02.02.2007 um 05:09 schrieb Geert Vancompernolle: > --- In [email protected], Thomas Treyer <[EMAIL PROTECTED]> wrote: > > > > > When I tried to use "I2C_WRITE", the kernel freezes, all processes > > are stopped and I have to reboot the FOX board. Therefore my simple > > question is, whether you tested the I2C driver with no HW connected. > > If yes, I have a problem in my setup. > > > > Well, to be honest... no, I didn't... > > I'll check it tonight and see where things go wrong at my side. > > Sorry for the possible trouble caused... > > > In both cases I did a I2C_Open () before the code above. Oh, and I > > switched your code to static Major number: > > //#define DYNAMIC_MAJOR_I2CDEV_NUMBER_ALLOC > > #undef DYNAMIC_MAJOR_I2CDEV_NUMBER_ALLOC > > If you don't want the "hassle" of adapting the make mechanism, then > indeed this is the best option. Hence, the reason why I used that > "compiler switch". > > Best rgds, > > --Geert > > > [Non-text portions of this message have been removed]
