Hi Everybody, I'm experimenting with Infineon's XC161CJ-controller on an Infineon SK-XC16x starter kit. Most of my routines work now, except the I2C-routines. Sending of data works OK, but the errors occur when I want to receive data. Has anybody on this forum written I2C-routines for this controller? And if so, are you willing to share them? Thanks in advance. :) Kind Regards, Dennis Ebben
Hi Dennis, I am currently working with the XC161CJ & the I2C Module. I am using the routines generated by 'Dave'. Haven't got it working yet though... Are you willng to share your code ?, maybe we can help eachother out. Regards, Rolf
Hi, I am FAE for Micro in Germany. I got the following feedback from our end costumer and think it may be usefully for you. Concerning the DAvE generated files there seems to be a "ugly" point. I translate the original message: "Concerning the I²C-interface there are two interrupts 'protocoll' and 'data' interrupt." The costumer was wishing only the data interrupt, "BUT DAvE is generating a interrupt handler for data interrupt with a JUMP to PROTOCOLL interrupt !" If you have first look at the generated code this not visible for you, because both interrupt vectors lay directly each one the other in memory. The first 'data interrupt ' mis initialized by the compiler with twice 0xFFFF what is equal to BSET R15, bit 15. If a data interrupt occurs than twice a BSET R15, bit 15 is executed, before the generated ISR handler is called." The costumer had not selected the register bank switch and so the register R15 was not saved (by the way: it was not used by handler routine). "What exactly happened ? All things went fine, but from time to time the most upper bit of R15 was changed to '1', what is not noted the first view, because this bit is used very seldom. Only if the compiler assume (assign ?) in function the register R15 a word variable (this istoo very seldom) the suspectly errors occur." To find this we needed 2 days. Than we noted an other thing. You need under some circumstances a extra dummy access to read back with the I²C-module. OK, that's is all I know about this, but may be it can help you to find the wrong code sequences. MESSAGE: Do not believe the DAvE can all do for you! We at this time work on a DAvE bug list. (Yes we really found some DAvE bugs ) The second: The I²C module was tested - I had contact to the developer and the test engineer, but with the hardware implementation there are some difficulties. Stefan
Hi Dennis, it is very good for me to hear I was able to help you with this code. I had only one additional reserve in background in case of problems with reading back. My costumer was lucky too with this code as I told. It is a little bit pitty that Rolf did not answer. As you know I send him the code too. OK- but important is, that you had solved the problem, so I am quite happy. Stefan
Dear Dennis & Stefan, sorry about the response delay, but I had to focus on some other matters. I have given the code a short glimps, and I think it will be helpful for me when I continue working with the IIC-Code. I got the routine I was working with at the time up and running before I recived your email Stefan, but I am grateful for your assistance,maybe I'll come back to you later regarding this... Best regards, Rolf
Hi Stefan and everybody, sorry for not english language, i have problems with it :-( Hallo, Stefan, ich beschäftige mich momentan ebenfalls mit dem I2C-Modul beim XC161-Controller und habe die gleichen Probleme die in diesem Forum vor einem Monat diskutiert wurden. Es funktioniert zwar, aber mit komischen Effekten. Bisher habe ich weder Application Notes noch funktionsfähige C- bzw. Assembler-Routinen gefunden. Ich habe in Forum gelesen, dass Du einige hattest. Ich wäre Dir sehr dankbar sein, wenn Du mir diese an igoreq@web.de zukommen lassen könntest, weil ich nirgendwo im Internet Hilfe zu diesem Thema finden kann. Vielen Dank im voraus. PS Ich habe keine Deine E-Mail Adresse, deswegen deswegen muß ich diesen Berich im Forum veröffentlichen.
Hallo Igor, ich sende Dir den Low-Level-Treiber zu. Bis jetzt hat er geholfen. DAvE generiert die Routinen uebrigens falsch. Stefan Hi Igor, I send you the low level driver. Up to now it was allways helpfull. By the way DAvE generates wrong routines. Stefan
Dear Mr.Stefan, I have the same problem as here discussed.I use XC161 controller to communicate with EEPROM with IIC.The writing routine runs well and reading routine doesn't.May I share you read routine too?That is for me very helpful. Thank you very much! zhen pei
Dear Zhen Pei, this is the low level routine from Infineon, but no problem to send it to you. Please leave your e-mail address here. I will send it to you. Stefan
Hello Stefan, I am working with the I2C module of the XC161. Could it be possible to publish the low level routines somewhere on the WEB ? Thanks for your help David
Hi David, unfortunately not. But it is no problem to mail it, if you leave your e-mail here. Stefan
Hello Stefan, You can send the I2C routines to this address : davidbrev(at)yahoo.se Thank a lot for your help. David
Hi David, have it done! Check your account. Stefan
Hello Stefan: I'm working with XC167CI, and I'm getting some problems with the I2C routines. I'm only using it to communicate with a 24LC EEPROM, I used SPI and uWire to do this (93 and 95 series EEPROMs) and I2C software implementation is new to me. I'd be gratefull to you if you'd send to me your routines, wich I think will work (more or less) with the XC167CI due to architechtural similarities. My address is alfersi(at)lavhek.com Thanks a lot.
Hi Alberto, no problem. Leave your e-mail here, I will send you asap. Stefan
Sorry Alberto, I was read over your e-mail account. Driver I mailed to you. Check your account. Stefan
Dear Stefan and Friends, I am also working on an I2C – EEPROM(FM24C256) application for XC167, so far I have used Dave generated code but I got into trouble. Writing works fine but reading…not. Stefan, is it possible for me to share your I2C code? My e-mail address is ai(at)home.se With best regards, Atsushi Ishii
Hi Stefan and freinds, I am using the iiC module of the XC161 to communicate to external eeprom. Please can i share you iic files? email:kaleem20@yahoo.com Thanks in advance Kaleem.
Hi Stefan! I'm also working with a XC161 and i didn't get my routines working. Can you please send me the routines. Thank you in advance. email: tinytove@gmx.at
Hi Ludwig, I sent it. Sorry for delay. Stefan
Hello Stefan, i have the same problem XC167 with 24LC16B serial eeprom. would you please send me the routines? Thomas
Hi Thomas, that is no problem, but I need your e-mail address to send it. Best regards - Stefan
Hello Stefan, my email address is thomas.schneider@berger-lahr.com thank you Thomas
Hi Thomas - done !! Stefan
Hi Stefan, could you (or someone who have also the code) please send me IIC-code? best regards, Karl E-Mail:koarl70(at)gmx.at
Hello Stefan: I'm working with XC167CI and want to change my bit banging routines from C 167 CS to the new hardware IIC Module. Reading the treads about this theme, I want to ask you if you could please send me the routines to use the IIC hardware. Thanks a lot! christian.winkler@winkler-urach.de Christian
Hi Karl, hi Christian, Do it in some minutes. Sorry for delay, I was on vacation. Stefan
Stefan, is it possible to share your I2C code? My e-mail address is georg(at)eunet.yu With best regards, Gyoergy Dozsa
I'm working on a Multimaster-system with 2 xc167 connected via i2c bus and i think i have a timing problem becouse the system is not very stable. If anybody got a working multimastersystem it would be nice to share some code with me. Thanks peter.scheuermann@ies-systems.com
Dear Stefan as many others I have problems to get the I2C routines on the XC161CS-32F working. I would appreciate if you could share your code. My email:dhandzic@plantron.se
Hello Dirk, I sent it, please check your account. Stefan
Really nice to see that this topic is still interesting for a lot of people. :)
View all questions in Keil forum