how tough would it be to implement separate commands like 12c start, 12cwrite, and 12c stop.
I do alot of stuff with AVR's and BascomAVR, and there are separate commands in there like the above.
I'd figure that youd have to have routines in the interpreter for the start and stop commands anyways, is it possible to jsut have two more commands to access them separately? Is there any way to possibly "poke" anything in the code to generate the start and stop conditions separately? I completely understand you dont want to give out your code (I wouldn't either!) but perhaps some way for moe advanced users to do such things would be wonderful.
I'm basically addressing being able to cause repeat starts and early stops.
With the picaxes able to now send only one data byte, this addition would make darn near every single I2C device out there compatible with the picaxe and expand the functionality greatly!
I do alot of stuff with AVR's and BascomAVR, and there are separate commands in there like the above.
I'd figure that youd have to have routines in the interpreter for the start and stop commands anyways, is it possible to jsut have two more commands to access them separately? Is there any way to possibly "poke" anything in the code to generate the start and stop conditions separately? I completely understand you dont want to give out your code (I wouldn't either!) but perhaps some way for moe advanced users to do such things would be wonderful.
I'm basically addressing being able to cause repeat starts and early stops.
With the picaxes able to now send only one data byte, this addition would make darn near every single I2C device out there compatible with the picaxe and expand the functionality greatly!