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.

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?

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.

after multiple attempts, i still couldn't get it. after flashing, MFDeploy wouldn't see it. Just kept saying "No Connection". I did use the RS232 version, and am using my USB=>serial cable.

turns out if i used mfdeploy.exe from the 4.1 sdk, it worked. 4.2 didn't, and older ones didn't.

but either way, i have a copy of mfdeploy from the 4.1 sdk msi, and i used that and all is well.

thanks again for your help.

i belive i spoke too soon.

once i got the TinyBooterDecompressor.bin flashed, it never asked me about locked regions. i power cycled it, and have not been able to connect to it again. bought a new USB/RS232 cable, used serial port from PC, nothing works.

methinks i just got a dud or killed it somehow.

you are a dang genius!

or i'm an complete idiot.

either way, thanks for clearing me up on that. took the board to work and used a normal serial cable, and it responds now. i totally misunderstood what i had purchased.

i appreciate your quick response, professionalism, and obvious thorough knowledge of the product. across these forums, i can see how much help you have been to users of all levels.

thank you.

Thanks for the response. I was hoping that I had just done something stupid.

The FTDI can be set to either 3.3 or 5V. it came from the factory 3.3, and I set the jumper to 5V. When plugged into USB power, i read 5V across the FTDI VCC and Gnd pins.

I've tried power several different ways. I currently have it powered from the FTDI on pin 21, and grounded to the FTDI on pin 23.

I've rebooted, and tried several computers and several USB cables. I plug in the mini, then launch SAM-BA.

This is a brand new mini. I plugged it into the breadboard and followed the instructions here:

http://forums.netdui...y-instructions/

i was able to change the deployment port to TTL UART (before i changed the FTDI board to 5V). so it was responding. until i applied the 5V to the erase pad.

I have no computers that have a serial port, so i can't test with a standard RS232 connection.

My circuit seems pretty simple. I'm not sure how else to troubleshoot this.

I guess I could try to order a different FTDI cable?

Thanks.

Hi.

I have a Netduino mini, and everything was working fine. I decided to update to 4.2

I followed the instructions here:

http://forums.netdui...-v420-update-1/

Everything was fine until I erased it. I applied 5V to erase pad, turned it off, then turned it back on (5V regulated to pin 21). 

I have an FTDI Basic breakout board at 5V:

CTS => GND

GND => GND

RX => Pin1

TX => Pin2

SAM-BA tells me "Connection Fatal /  Communication Error".

I've switched the TX/RX wires (pins 1 and 2), supplied 9V to pin24 instead of 5V to pin21. still no luck. i measure 5V on pin 21 when supplying 9V to 24. I've tried pin 23 and 4 for the ground wire of the FTDI. I measure 5V on the FTDI also.

I can see the Tx LED flash on the FTDI when SAM-BA is trying to connect. About 1 Hz. Then it times out.

I've tried using SAM-BA v2.8.

I've tried different jumper wires and a different breadboard. But I get no response from the mini.

I've tried erasing again with 5V multiple times.

Anyone have any ideas? By trade, I'm a .NET developer and like the idea of sicking with that language, and would rather not go back to arduino if i can avoid it. but for $30, i have not even gotten a blinking LED sample running on this mini. 

Thanks.