Netduino home hardware projects downloads community

Jump to content


Photo

Getting started with Netduino Mini (early instructions)


  • Please log in to reply
39 replies to this topic

#21 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 11 June 2012 - 03:44 AM

Hello!
I just found the time to confirm that my new (well new to here) Netduino Mini works. After mounting it on a breadboard and connecting it accordingly to a USB device, I borrowed the MiniUSB one that's for the Arduino Mini. I then wired it accordingly: Power on the USB device was connected to the +5 and ground positions. The TX and RX on the USB end went to the Netduino, and then made sure that Putty saw it, with regards to the settings. And hit the ESC key. I then got this blurb:


Netduino Mini

1. TTL UART (COM1)
2. RS232 UART (COM2)

Which transport (1 or 2)? 1

Switching transport to TTL UART (COM1)...
.NetMF v4.1.2821.0
NetduinoMini, Build Date:
Feb 14 2011 00:59:53
ARM Compiler version 400902

TinyCLR (Build 4.1.2821.0)

Starting...
Created EE.
Started Hardware. t?ÔÊMSdbgV1qt?ÔÊMSdbgV1wKft?ÔÊMSdbgV1eâ¦t?ÔÊMSdbgV1cPt?ÔÊMSdbgV1i$Kt?ÔÊMSdbgV1oǽt?ÔÊMSdbgV1MvÊ8t?ÊMSdbgV1K<?t?ÔÐÊMSdbgV1A°'7t?ÔÐ
ÊMSdbgV1GSÑ0t?ÔÐ
ÊMSdbgV1Uú't?ÔÐ
ÊMSdbgV1Y<ü(t?ÔÊMSdbgV1_ß
/t?ÔÊMSdbgV1^xt?ÔÊMSdbgV1t?ÔÊMSdbgV1þwt?ÔÊMSdbgV1pt?ÔÊMSdbgV1ÒÈgt?ÔÊNo debugger!
Create TS.
Loading start at 134134, end 1462d4
Attaching file.
Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA)

Attaching file.
Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA)

Attaching file.
Assembly: Microsoft.SPOT.Hardware (4.1.2821.0) (1752 RAM - 11440 ROM - 7371 METADATA)

Attaching file.
Assembly: Microsoft.SPOT.Hardware.SerialPort (4.1.2821.0) (512 RAM - 3488 ROM - 1543 METADATA)

Attaching file.
Assembly: Microsoft.SPOT.IO (4.1.2821.0) (740 RAM - 4620 ROM - 2522 METADATA)

Attaching file.
Assembly: System.IO (4.1.2821.0) (1548 RAM - 13292 ROM - 5862 METADATA)

Attaching file.
Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) (256 RAM - 1108 ROM - 491 METADATA)

Attaching file.
Assembly: SecretLabs.NETMF.Diagnostics (4.1.0.0) (180 RAM - 440 ROM - 166 METADATA)

Loading Deployment Assemblies.
Attaching deployed file.
Assembly: NetduinoMiniTransportSelector (1.0.0.0) (244 RAM - 1168 ROM - 310 METADATA)

Resolving.

Total: (8788 RAM - 75308 ROM - 41878 METADATA)


Total: (8788 RAM - 75308 ROM - 41878 METADATA)

Ready.It's all good I believe. Except for one question, am I up to date on firmware for it?

Edited by Dr Who, 11 June 2012 - 04:42 AM.


Doctor Who
"This signature does not exist!"

#22 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 June 2012 - 09:59 AM

Hi Dr Who, Yes, that is correct. You can either use RS232 on the "BASIC Stamp compatible" pins or a USB-TTL adapter. BTW, great name :) Chris

#23 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 12 June 2012 - 04:52 AM

Hello!
Thank you Chris. Your instructions on how to change a Netduino program such as blinky from running on the basic device to the mini simply by changing one referenced hardware library were right on the money. Although the properties tab also needs to be checked to make sure its set accordingly to accommodate a proper delivery of code otherwise an error will be flagged. It wanted me to check the hardware. I did and then checked the properties tab. Then it worked and I'm running.

I did this for the program code:
            // write your code here
            OutputPort led = new OutputPort(Pins.GPIO_PIN_20 , false);

Inside the braces of course. I randomly chose that pin, and I was off.....

Now to work on more complicated ones. Presumably the TW lines on the bottom (TWD and TWCK) are for I2C style communications?


Doctor Who
"This signature does not exist!"

#24 Stefan

Stefan

    Moderator

  • Members
  • PipPipPip
  • 1965 posts
  • LocationBreda, the Netherlands

Posted 12 June 2012 - 05:31 AM

Now to work on more complicated ones. Presumably the TW lines on the bottom (TWD and TWCK) are for I2C style communications?

According to http://www.netduino....omini/specs.htm : pins 9-10: I2C SDA, SCL :)
"Fact that I'm a moderator doesn't make me an expert in things." Stefan, the eternal newb!
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs

#25 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 12 June 2012 - 06:19 AM

According to http://www.netduino....omini/specs.htm : pins 9-10: I2C SDA, SCL :)



Hello!
Yes exactly. According to the Atmel supplied data sheet, the pair are indeed considered to be compatible, just need to be programmed accordingly. I figured that once I get an idea of my intended project, I'll be mating a TI I/O device that uses that style of communications to it, probably their PCF8574A part, or the PCF8575 one. It actually depends on what I have in mind.....


To be honest it simply depends on what that will be. I've enclosed copies of the data sheets for those two parts. Oh and thank you for your fast answer.

Attached Files



Doctor Who
"This signature does not exist!"

#26 Pankaj21

Pankaj21

    Member

  • Members
  • PipPip
  • 10 posts

Posted 27 February 2013 - 06:56 PM

Netduino Mini - Cannot get menu on pressing escape!

 

Connected Mini to FTDI Basic -> (pin 24 to 9V, pin 23 to gnd, pin 23 to FTDI Gnd, pin 11 to FTDI TX, Pin 12 to FTDI RX) FTDI is on 3.3V

I get all the boot messages on putty all upto the ready message. Thereafter it freezes and does nothing whether I press escape or any other key. So I dont get the menu to change the default port to TTL UART 

 

 

Any ideas what could be wrong?

 



#27 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 28 February 2013 - 05:06 AM

Hi Pankaj21,

Connected Mini to FTDI Basic -> (pin 24 to 9V, pin 23 to gnd, pin 23 to FTDI Gnd, pin 11 to FTDI TX, Pin 12 to FTDI RX) FTDI is on 3.3V I get all the boot messages on putty all upto the ready message. Thereafter it freezes and does nothing whether I press escape or any other key. So I dont get the menu to change the default port to TTL UART    Any ideas what could be wrong?

Is this a new Netduino Mini? Where did you buy it? It sounds like the deployment port may already be on the TTL UART...if you're getting the boot messages. Try pinging it from MFDeploy (after disconnecting from your terminal program). Chris

#28 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 04 September 2014 - 06:40 AM

Hi guys, 

 

just following getting started directions for my new mini from here (thanks Fabien!): http://fabienroyer.w...-netduino-mini/

 

And after opening terminal, Esc key does nothing. MF deploy ping fails. When I hit Esc (or any key), the RX light on the breakout board blinks.

 

I am using one of these to connect: http://www.ebay.com/...=STRK:MEBIDX:IT

 

a new device appears on COM13 when I plug in the USB cable. 

 

Anything else I can try to get this running? 

 

thanks!



#29 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 07 September 2014 - 08:02 AM

Any ideas? Do I have a bricked mini?

 

I have an Arduino Pro Mini that I just tried with the same FTDI cable, connected immediately without any issues, got Blinky working on it.



#30 baxter

baxter

    Advanced Member

  • Members
  • PipPipPip
  • 415 posts

Posted 07 September 2014 - 06:21 PM

I would try to update your firmware. Select the TTL zip file since you haxe a TTL cable.
http://forums.netdui...-v420-update-1/



#31 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 07 September 2014 - 08:56 PM

I would try to update your firmware. Select the TTL zip file since you haxe a TTL cable.
http://forums.netdui...-v420-update-1/

 

I could try that, but the board does not respond to pings in MFDeploy. 



#32 baxter

baxter

    Advanced Member

  • Members
  • PipPipPip
  • 415 posts

Posted 08 September 2014 - 01:50 AM

Did you first try to erase it by applying 5V to the gold ERASE pad? It's located at the top on the right hand side.
Flashing instructions after erasing are here toward the bottom of the page,
http://forums.netdui...-v420-update-1/



#33 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 08 September 2014 - 06:00 AM

Just tried the erase pad - same results. blank screen in Putty, MFDeploy ping fails.



#34 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 13 July 2015 - 12:26 AM

After several months, trying this again :-). Reset my mini by applying 5v to the gold erase pad, attempted to connect via SAM-BA and it says "no valid processor found". 

 

I am connecting via FTDI breakout USB cable in 3.3V mode:

- ground to pin 23

- 3.3V to pin 21

- RXD from breakout board to pin 11

- TDX from breakout board to pin 12

 

 

Any thoughts?



#35 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 13 July 2015 - 04:33 AM

After several months, trying this again :-). Reset my mini by applying 5v to the gold erase pad, attempted to connect via SAM-BA and it says "no valid processor found". 

 

I am connecting via FTDI breakout USB cable in 3.3V mode:

- ground to pin 23

- 3.3V to pin 21

- RXD from breakout board to pin 11

- TDX from breakout board to pin 12

 

 

Any thoughts?

 

Well yes. When uploading fresh firmware to the little guy, the user needs to connect to the RS232 points at RS232 levels. The FTDI breakout produces TTL: or CMOS compatible output levels. So you'd need USB to RS232 adapter to do that. I normally use one for the Basic Stamp gang to make it work since its within four solar diameters of the specifications in the FTDI datasheet for just such a design. It also expects 5v at the positive voltage connection when working. The TTL management connections are fine for sending it the firmware for TTL stuff although you might need to do the same thing as you just did for the regular fresh firmware for it.

 

I expect Chris will chime in with appropriate things as soon as he's around.



Doctor Who
"This signature does not exist!"

#36 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 13 July 2015 - 06:51 AM

Well yes. When uploading fresh firmware to the little guy, the user needs to connect to the RS232 points at RS232 levels. The FTDI breakout produces TTL: or CMOS compatible output levels. So you'd need USB to RS232 adapter to do that. I normally use one for the Basic Stamp gang to make it work since its within four solar diameters of the specifications in the FTDI datasheet for just such a design. It also expects 5v at the positive voltage connection when working. The TTL management connections are fine for sending it the firmware for TTL stuff although you might need to do the same thing as you just did for the regular fresh firmware for it.

 

I expect Chris will chime in with appropriate things as soon as he's around.

 

Thanks Dr. Who. I looked in another thread and it seems that I need one of these adapters: http://www.amazon.co...s/dp/B0000VYJRY

 

Since I've erased my ND Mini, I need to get the bootloader flashed using 232 connection via SAM-BA....makes sense now. 



#37 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 13 July 2015 - 07:14 AM

This may be a noob question, but is there any reason to get the USB to RS232 Keyspan adapter vs cheaper options like these?

 

http://www.ebay.com/...=item1e94234865

 

http://www.ebay.com/...=item2354b31764



#38 Dr Who

Dr Who

    Advanced Member

  • Members
  • PipPipPip
  • 261 posts
  • LocationNYC

Posted 13 July 2015 - 02:36 PM

Plenty actually.

Most of those eBay adapters use the Prolific chipset, and sadly they aren't reliable. There are histories of people having to spend more time with the adapter then with their projects.

 

The chipset behind the Keyspan design already a known object. Those two are unknown. I also chose in my explanation the one made by Parallax because its exactly what the designers at FTDI had in mind when designing a USB to Serial (RS232) adapter. The firm (FTDI) also sells an adapter along the same lines, however a DB9 connector will be needed that mates with the chosen adapter.



Doctor Who
"This signature does not exist!"

#39 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 14 July 2015 - 12:05 AM

Dr. Who is wise :)

Yeah, RS-232 adapters vary a lot in quality, especially USB to RS-232 adapters: I typically always recommend the Keyspan 19-HS.

Chris

#40 FourT2

FourT2

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts
  • LocationSeattle, WA

Posted 14 July 2015 - 12:10 AM

Thanks guys! Yeah I have one of the Prolific adapters and I spent about an hour messing with the drivers before deciding to give up on it. Keyspan it is then.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.