i dont think thats a good idea. flash is also the place where the netmf and your programm is.

if they make this aviable, lot of ppl will mess this up.

also, since it has limited write cycles, its a problem.

iam sure _some_ ppl will just write some stupid variable 1000 times a second till the flash block is dead

//edit: iam not pessimistic, but realistic

hmm.

try using > 2mhz as spi clock.

(hmm, well that should be fixed long time ago and not interfere with ethernet.. hmm)

and try using SPI_Devices.xxx

btw: from what i know also 16mhz is max the netduino can do (some division problems or whatnot, iam not sure)

that link doesent have really details

its something like that: you cant use sdio without any licensing stuff, but nothing hinders you to use 32gb sd cards with spi.

its some kind of driver problem with the netmf.

like cw2 wrote a 4.1 driver wich supports larger cards, without sdio.

arduino also supports larger cards per spi. - not sdio - all the free stuff

thats allready included in  the netduino sdk, wich you need/want.

like the pins on netduino are marked like d8 and so on, and you use Pins.gpio_d8 to access it.

(not CPU.Pin. ... secretlabs allready mapped the pins right.. in the Pins. struct )

wow 30$

a dht22 is like 3$

yeah iced is right, the support of dht for netduino is uncool, but still possible.

suggestion:

remove the sensor.enterCommandMode(); and sensor.exitCommandMode(true); for the user.

make it automatically if you call the functions that wants command mode.

nakchak: thats not correct.

sdhc is an indicator for size and speed (like sdhc class 10 is one of the fastest)

sdio is the protocol thats normally used, but the sd cards also

support up to 32gb with spi. like arduino sd libs can do that.

sd and sdhc cards, but not sdxc (wich is the next gen, over 32gb)

(well maybe they are supported - but they come mostly with a new filesystem, see wikipedia)

spi is very much slower than sdio, but it should work. every card supports this

hm, to reflash iam using a cp2102 + max232 - cheapo solution and works great.

when i use the ttl (uart) port from programming i just remove the max232

a note: the cp2102 is like 3$ and a max232 with 4 caps also around 3$ ..

How can i repair it?

with a hammer

(sorry)

try it maybe under linux, if that doesent work, well, theres a programm for formatting sd card (sdformatter or something like that)

if that also doesnt work, maybe its dead, wich i guess cant be from netduino (3.3v is fine for them)

mostly its just old, maybe some damage through esd (do you have a carpet?), or did you write to it some million times?

well, you should use a multi i2c class, its makes it look way nicer.

also:

byte[] data = new byte[bufferSize];
  data[0] = 0x00; // Going to starting address

  for (uint i = 1; i < bufferSize; i += 2)
  {
  data[i] = 0x00;
  data[i + 1] = 0x00;
  }

isent needed

byte[] data = new byte[bufferSize];

sets every item in the array to 0x00 allready

than:

PWM trig = new PWM(Cpu.PWMChannel.PWM_0,60000,10, PWM.ScaleFactor.Microseconds, false);

dont use Cpu.whatever.

its PWMChannels.yourpin

another suggestion: dont use static all the time.

http://pastebin.com/9BBHnWA3 > anti static

yeah nice things for logging.

about motor and esc: wow watercooled and active cooled, guess it allreads has tons of power

i dont think its unexploited. maybe boats not so much, but drones (quadrocopters) are many around, modded with cameras, gps, autopilot and all kinds of stuff.

for  a boat, hmm. you can add a little horn (sound) and some leds

some sensors to check out how rought the water is and stuff like that.

well, for rc stuff i wouldnt mess around with the electronics, id mod/change the stuff allready there -

like a better motor, stronger lipo - cooler tires for a car and so on (sorry dont know boats)

i dont know if there are any with more outputs, but i guess not. its not that big, and the connectors are quite large, so not that much space left

but you can add more than one cable ofc. like i soldered a little board with switching regulators and screw terminals, and than made a fat cable from the supply to this board, so i can use many different voltages of it. - i have the 5v version of the supply, but mostly use 3.3v (-except for some parts that needs 5v or more)

i suggest getting at least the 5v version and step it down.

a pc power supply has 3.3,5 and 12v - but its also way bigger and iam sure has more loss

edit: all across the house is bad with low voltage and higher current. it generates loss and heat.

thats why we use 220v here in the houses, to not burn the cables.. like a 500watt device is fine with 220v, but with 5v or so the cables would melt (or be way way bigger )

not very fast. but you can use pwm, wich can be faster than arduino

Where is the cpu pin 13 then?

 

check the uC's datasheet.

and than compare it with the netduino shematics.

i guess its not broken out, but youll never know.

(these uC's can have some 100 of pins, and the little netduino only has a few broken out)

i just wanted to add: did you erase it with 3.3v ? erasing with 5v may damage the uC.. maybe not the first time, but if you do it a 100 times ...

Cpu.Pin.GPIO_Pin13 is the problem. thats the reference to the hardware pins, like pin13 on the uC itself.

use Pins.yourpin and it will work (like you did for the onboard_led)

[font="arial, helvetica, sans-serif;"]SecretLabs.NETMF.Hardware.Netduino is for all gen2 boards, the other for the gen1.[/font]

[font="arial, helvetica, sans-serif;"]they changed the naming for the gen2 boards so its in line, all have the same namespace there (normal and plus - and the ones that will follow sometime too)[/font]

your wireing seems strange.

you have to use pin 1, 2 and 3

you are using 2,3 and gnd.

(yes ok you have to connect both gnd's together if you use a external power supply)

you flash the tinybooter via samba over the rs232 port (pin 1,2 and 3) with 12v.

depending on wich booter you flash you can than flash the netmf with either 12v rs 232 or 3.3v uart (pin 11 and 12)

i like diptrace a lot. it has tons of components, you can try it out for 30 days free, and if you like, the cost is cheap.

it also has a 3d rengering thingy, so you can kinda look what your pcb's might look when finished (thou not all stuff has 3d modules aviable, so its just empty.) its also at least as easy than fritzing, but way easier to route (by hand) and more precize)

iam about to order 10 pcb's from itead. its incredible cheap.

(i turned component render off ...)

https://www.dropbox...._b_3d_front.png

https://www.dropbox....p_b_3d_back.png

hmpf...

https://www.dropbox..../serialport.png

real spi ports are million* times faster. - they do that in hardware what you do in software, and that a lot faster than you can

set the pins in software.

the 595 is a quasi spi device, so its made for that.

also, what you do seems way more complicated than what i explained (with my spi and 595 class)

best to forget about your doubts (where did they came from?) and just trust me.

while (true){    Debug.Print("done");}

wow that looks mean

add s leep 1 at least

there are some things not so correct.

first: the 595 can only supply around 90ma total, so max 3 pins can reach the 35ma.

since you use 8 it gets split over all (like 10ma per pin) - its not healthy for the ic todo that.

than: you open and dispose the output ports, dont do that. let them open the whole time.

also, whats your main loop doing? if it ends it may give odd results.

and why are you bitbanging spi? (and in a even strange way ...)

use hardware spi, its way faster. and dynamic

connect it like that:

https://netmftoolbox...pported devices

in the link in my sig is a good multispi class, and ill add my 74hc595 drivers.

use it like: IC74HC595 hc = IC74HC595(latch, SPIModule-1-or-whatever-you-wanna-use);

hc.WriteData(0xFF); // turn all leds on

hc.WriteData(0x00); // turn all leds off

edit: btw, that circ-05 used 350ohm resistors, on the cathode side (negative) and the leds are connected with anode (positive) to the 595's - thats the way id do it also, ou should also do it like that, not 2 resistors and get the correct value.

hanzibal: hehe your driver looks like mine

but i have a suggestion: when you handly the interrupt like you do you get an odd number. filter it before

to get wich pin actually changed

iam no teacher.

and there is so much info about this iC, i googled "pcf8574 netduino" and there are tons of helpfull samples/tutorials (the first is good, the second and 4th )

your adressing is correct.

its a very good and common iC for input (for output id use a 74hc595, cos its much much faster..)