On 2014-05-16 14:50, Sebastian Kuzminsky wrote: > On 05/16/2014 07:30 AM, Marius Liebenberg wrote: >> Hi >> I am busy with a generic i2c component. I2c has some timing related >> features and I thought that it would make sense to load the component in >> a thread that has a very certain predetermined thread cycle time. This >> way it would be very easy to impliment timeing related features. Is it >> OK to load one's own thread or is the practise not advised. >> P.S. I am testing the code now in a very much slow downed thread in >> order for me to see what happens in Halscope. The production thread >> could have a time of 1us. >> >> Any thoughts? > You can create whatever threads you want, and use them any way you want. > > But i think you will not be able to have a 1us period, that's below the > scheduling jitter of any system i've seen. Well not faster that 1us I should have said. ( i need 10u to 20us) I will be happy with whatever I get as long as it is of known value then I can use parameters to setup every device individually as required. The problem with i2c devices are that they dont all respond in the same fashion or time. So I have to have programmable time-outs per device and maybe some bus arbitration function.
while we are talking about timing, is there an escape mechanism that I must use in case my code is to slow for the cycle? -- Regards /Groete Marius D. Liebenberg +27 82 698 3251 +27 12 743 6064 QQ 1767394877 ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
