1 reply to this topic

[Hugh Hoover]

I'm trying to debug using COM2 through socket5 as a OneWire interface. I've been able to deterministically read a presence bit using 9600 baud - looks nice on the O'scope. Now - I'm trying to read data, and all I'm seeing is ... nada ... I'd like to get my O'scope hooked up, but I need a stable trigger - I was thinking I could simply turn the socket's GPIO pin hi/lo at various times to use as an external trigger. Issue I have is that... how do I specify it? can I just use (Cpu.Pin)24 (the pin number shown in the schematic for GPIO_Socket5)? I've tried that, and the LED for Socket3 turns on, and I have no signal on pin 3 of the socket. I KNOW I'm supposed to use a module for this... but I figure I can convert it when the shield firmware is ready. If I were to use the shield base - how do you create a SerialPort for it?

[Hugh Hoover]

Ah - I found it - the GoSocket GetPhysicalResources response includes the gpio pin. This works.