And a lot more pins ...
You don't need to connect any more pins then the shield uses. You just have to wire it up yourself. The module can be used either in bus mode, or SPI.
--Dave
Dave's Content
There have been 8 items by Dave (Search limited from 26-April 23)
#2592 Cheaper Ethernet option?
Posted by
on 21 September 2010 - 10:37 PM
in
General Discussion
You don't need to connect any more pins then the shield uses. You just have to wire it up yourself. The module can be used either in bus mode, or SPI.
--Dave
#2555 Cheaper Ethernet option?
Posted by
on 20 September 2010 - 08:54 PM
in
General Discussion
Right now Cutedigi has them for sale for $25. http://www.cutedigi....1ea707987da5b4.
You can also use the Wiznet module which has everything on it for about $25 as well, which is what I'm using to prototype it.
http://www.sparkfun....roducts_id=9473
--Dave
#2210 Netduino Tutorial - Multithreading (Methods with Parameters)
Posted by
on 13 September 2010 - 06:26 AM
in
General Discussion
Actually since you're not using the value returned you could do something like this, and do it all in one line of code....
--Dave
public void Pulse(int onTime, int offTime, bool onFirst, uint repeat)
{
new Thread(() => doWork(onTime, offTime, onFirst, repeat).Start();
}
--Dave
#1966 W5100 Driver
Posted by
on 08 September 2010 - 09:18 PM
in
Netduino 2 (and Netduino 1)
I have a W5100 module, not shield, hooked up on a proto-board to see how it works. I'm in the process of writing a set of managed classes to work with it, I'll post it when it's done and tested.
Unlike the Fez stuff, it will use the interrupt, and implement all the async stuff.
I wasn't going to say anything till it was done, but since someone else is looking at using the chip, I figured I would let you know that it was in progress.
The chip doesn't seem to work according to spec, and I'm trying to figure out why. The SPI timing diagrams that they have in their app note, seem to be wrong.
For example to read a register on the chip the following works as it should:
However doing a 4 byte write, to write a value to the register does not work. You have to do four one byte writes. This should not work, since raising SS should clear the input sequence.
In about a week or so, since I have to work on what I get paid for, as well, I should have something to upload to the board.
--Dave
Unlike the Fez stuff, it will use the interrupt, and implement all the async stuff.
I wasn't going to say anything till it was done, but since someone else is looking at using the chip, I figured I would let you know that it was in progress.
The chip doesn't seem to work according to spec, and I'm trying to figure out why. The SPI timing diagrams that they have in their app note, seem to be wrong.
For example to read a register on the chip the following works as it should:
snip... var outbuf = new byte[3]; var inbuf = new byte[1]l oputbuf[0] = 0x0f; outbuf[1] = //high byte of address; outbuf[2] = //low byte of address; spi.WriteRead(outbuf, inbuf, 3); snip...The correct value is read from the register.
However doing a 4 byte write, to write a value to the register does not work. You have to do four one byte writes. This should not work, since raising SS should clear the input sequence.
In about a week or so, since I have to work on what I get paid for, as well, I should have something to upload to the board.
--Dave
#1081 where is the .net micro framework documentation?
Posted by
on 22 August 2010 - 07:52 PM
in
General Discussion
bryancostanich,
That's good to know, as I prefer local help too. I didn't know about that option in the Visual Studio 2010 installer. Thanks!
Chris
There is also a free plug-in in the visual studio gallery that gives you the old VS2008 style help. Get it at: http://visualstudiog...ed-cbcbebe04a20
--Dave
#314 Firmware build issues
Posted by
on 12 August 2010 - 06:34 PM
in
Netduino 2 (and Netduino 1)
It's standard CDC, but Windows will need you to point it to the INF file. It's in the Atmel "program files" directory.
If you're running 64-bit Windows, you'll need to start your computer with driver signing disabled. Or on Windows 7 64-bit, run Windows XP Mode and use SAM-BA there (which is what I do on my computer--it works nicely).
Does that get you pointed in the right direction?
Chris
Windows 7 XP Mode, is a virtual running XP. It has access to the hosts hardware? Didn't know that. I'll give it a try.
Thanks,
--Dave
#281 Firmware build issues
Posted by
on 12 August 2010 - 03:48 AM
in
Netduino 2 (and Netduino 1)
3. Erase your Netduino completely, flash the GCC-compiled TinyBooter using SAM-BA, and then deploy the GCC-compiled TinyCLR via MFDeploy. We've exposed an "erase pad" directly underneath D0 on the Netduino. To erase your Netduino, plug a jumper wire into the 3V3 or 5V power header and touch the "erase pad" for 220ms+ (and then disconnect all power from your Netduino to give it a full reset). Be very careful not to touch any other leads with the 5V/3V3 power
Chris
Is there any special USB driver you need to use SAM-BA? It doesn't see the board.
--Dave
#132 Ethernet Shield?
Posted by
on 08 August 2010 - 09:04 PM
in
Netduino 2 (and Netduino 1)
Chris,
Have you seen this shield? http://www.micro4you...d/prod_119.html
Since NETMF porting kit does have source code for the enc28j60, it seems like it wouldn't be that hard to integrate into the HAL.
If I were to try this myself, it would be nice to know what ARM compiler you used to build your port. The source zip doesn't have any documentation with it.
Thanks,
--Dave
