SB70LC I2C2Serial example not working
Posted: Wed May 14, 2014 10:56 am
Hello everyone.
Before I ask my question, yes I did search the forums and I couldn't find an answer.
Preliminaries :
Running an SB70LC development board with a static ip address.
Connected via Ethernet and USB for the serial debugging output.
I can see bootup and printf/cout work on the serial output through MTTTY.
OS is Windows 8.1.
I am running the I2C2Serial example code and it is not working for the Multi-master I2C (I didn't try the single, but if it doesn't work in Multi we can't use this board).
The problem is that I cannot get stdin to work to input the I2C slave address. gets, fgets, and cin all do not work when I type into MTTTY. This is probably something stupid that I'm overlooking.
Troubleshooting steps that I've already taken :
Use fgets and cin.
Debug and Release builds both show the same behavior.
cout, printf all work and I can see the output.
When in Debug, stepping over gets or fgets just hangs.
Changing the flow control in MTTTY to software and trying the above.
I've read any and all Netburner documentation that I can find about how stdin is mapped.
My suspicion is that stdin is being mapped somewhere else, incorrectly.
Does anyone have any suggestions or solutions?
If I cannot get stdin working for this board for debugging, then this is a no-go condition on using this board for our system.
Thanks
Before I ask my question, yes I did search the forums and I couldn't find an answer.
Preliminaries :
Running an SB70LC development board with a static ip address.
Connected via Ethernet and USB for the serial debugging output.
I can see bootup and printf/cout work on the serial output through MTTTY.
OS is Windows 8.1.
I am running the I2C2Serial example code and it is not working for the Multi-master I2C (I didn't try the single, but if it doesn't work in Multi we can't use this board).
The problem is that I cannot get stdin to work to input the I2C slave address. gets, fgets, and cin all do not work when I type into MTTTY. This is probably something stupid that I'm overlooking.
Troubleshooting steps that I've already taken :
Use fgets and cin.
Debug and Release builds both show the same behavior.
cout, printf all work and I can see the output.
When in Debug, stepping over gets or fgets just hangs.
Changing the flow control in MTTTY to software and trying the above.
I've read any and all Netburner documentation that I can find about how stdin is mapped.
My suspicion is that stdin is being mapped somewhere else, incorrectly.
Does anyone have any suggestions or solutions?
If I cannot get stdin working for this board for debugging, then this is a no-go condition on using this board for our system.
Thanks