5 replies to this topic

[coose]

hi,

 

i'm trying to do a pizeo buzzer on PWM_3, and I'm getting nothing. when moving to PWM_2 (and moving the wire from pin 20 to 19), it works fine.

 

is there anything special about PWM_3 that i need to be aware of? is it possible I have a dead pin?

 

i'm certain my trivial circuit is correct, as it works on my Netduino 1, and works on PWM_2.

 

thanks.

[Chris Walker]

Hi coose, Three things: 1. Use the PWMChannels.PWM_PIN_## enumeration, rather than PWM_3. That will make sure you're aligned with the proper pin. 2. If you can drive a signal high/low on that pin using OutputPort, the pin is fine. [We check each pin after manufacturing as well.] 3. Are you running the latest production firmware (4.2.2.2)? Chris

[coose]

I changed to use PWMChannels.PWM_PIN_20 and no luck.

Then i tried to blink an LED declaring this pin as an output port:

OutputPort x = new OutputPort(Pins.GPIO_PIN_20, false);while (true){	x.Write(!x.Read());	Thread.Sleep(100);}

This doesn't work. Driving it off of another pin (i.e. 15) works fine. I'm moving the wire to match the pin defined in code (I've made this dumb mistake before...but not this time).

 

It's reporting TinyCLR build 4.2.0.0 and Bootloader build v4.2.0.1

 

I didn't know there was a 4.2.2.2 available?

[Chris Walker]

Hi coose, Do pins GPIO_PIN_16 through GPIO_PIN_19 work for you? If so, can you try reflashing your board with 4.1 firmware? It's possible that the board has been damaged--but I'd like to isolate any potential firmware issue for you first. Chris

[coose]

16 - 19 work fine. I'll flash 4.1 and see what happens.

[coose]

Looks like it's a dead pin. No response with PWM or OutputPort on 4.1 either.

Thanks for your help.

 

Now if only I had considered that before I spent hours trying to debug a silly buzzer. Seriously...hours.