jdsmith

I have not tried it yet, but in .NET MF 4.2 (you'd need to update to 4.2.0 RC1 firmware), there are new Directory.EnumerateFiles(...) and Directory.EnumerateDirectories(...) static methods that should work even for large amount of entries. For more detailed information, please have a look at CodePlex issue 671 (resolved with changeset 12496).

Thanks! I'll give it a try.

I think I'm having the same issue jd - did you ever solve the flow control problem? I'm staying back at 19200 baud for the time being and the board seems to work fine but I would like the extra speed.

James,

I have flow control on, and I'm running @ 38400 without issues. In my applications, I'm rarely receiving requests. I'm mostly POSTing and GETting. As such, my use case might not be applicable to you. The trickiest thing with the WiFly board, in my opinion, is getting it in and out of command mode at the right time(s).

Thanks. Tried the whole setup on a Win XP machine. Still no dice. I assume that what's supposed to happen after I erase the board and install the Atmel tools is that. when I plug in the board via USB, the board will load with the Atmel drivers? That's not what's happening, and if I look at the driver properties of the Unknown Device that appears in Device Manager when I plug in my (probably dead) board, the Hardware Id is something like USB\UNKNOWN. Looks like I have to call this one done. Thanks, again, for the suggestions.

SAM-BA 2.09 on Win7-64 for me. 2.10 didn't work.

Cool. Is there an archived version of 2.09 somewhere?

Hi jdsmith,

[Also, SAM-BA is a bit harder to work with on 64-bit Windows 7. I personally installed Windows XP Mode and use it from inside there...works well.]

Chris

Thanks, Chris. I'm pretty certain I've followed Dan's/other's instructions, and still no luck. I've definitely erased the board, or at least I followed the "plug a wire in to the 3.3v slot/touch the gold pad" steps many times. I haven't tried on a computer running straight-up XP (yet), but I did try a 32-bit version of Windows 7 this afternoon. I made it a little farther but got a blue screen when trying to install the ATMEL Test Board driver. I also tried running in XP compatibility last night, but the USB device would not show up in the XP device manager. Maybe that's an indicator the board is dead. Rebooted dozens and dozens of times. I also tried your recommendation in another thread of booting Win7 into "allow unsigned driver" mode, but that didn't seem to have an effect.

To recap, when I plug the N+ board in via USB, Windows pops a toast message saying Windows can't recognize the USB device. The PWR and LED lights on the N+ stay lit up. If I look in device manager, I see an "Unknown Device" under the USB node (I don't see a corresponding COM port under the Ports node). I've tried installing the SAM-BA CDC driver (this is outlined in the SAM-BA readme file), but one of two things happens: blue screen (in the case of 32-bit Win7) or a message saying the driver isn't compatible with the version of Windows I'm running (I consistently see this message in Win7 64; I saw the message in Win7 32, but it was reversed...the message said the driver wasn't made for the 32-bit version of Win 7; I believe the driver compat issue has something to do with the SAM-BA install which seems smart enough to know when it's running in XP mode and install the XP-compatible drivers).

Should I have to install the ATMEL driver? Or is that an indicator of a more serious problem with the board?

JS