Mini210S WINCE6 Win7 64b USB

Hello Everyone,

So I've just bought this little beast, installed wince6 via uSD card,
booted up, and getting ready for software deployment. I also installed two
files: Mini210-CE6-SDK and Mini210-CE6-Suite-1217. However, Windows Mobile
Center will not connect to the device. When I plug the board into my
computer using the provided usb cable, it says Unidentified Device. It goes
to search for drivers via windows update, gets to the install stage, and
ends up with Device Unplugged. I also have a Mini2440, and it works great.
I can program and upload software via VS2008 just fine. Does anyone know
what I've done wrong here?

Thanks!

Hi,

At this point in time the BSP does not support USB Function and so Active
Sync will not work.  Friendly Arm are aware of this but have not given a
commitment for when this feature will be added to the BSP.  

The same issue has been mentioned several times now in recent posts...

Hi,

because the miniUSB driver is not available in WindowsCE 6.0, the Samsung
don't provide it. it will take a long time to develop.

please wait. 

PS: Android is better on Mini210S, you can play it first.

mindee

@BBBB. Oh, so that what the other posts were about. I thought it was for
another issue since I have 210S and not a 210. Is it safe to assume that
people with mini210 are facing the same issue? This is really weird because
the included DVD contains CE6-SDK for Visual Studio, but I can't connect
because of a usb driver. Why even make the SDK in the first place?

@mindee. I tried Android, but it felt sluggish for some reason. Plus, the
application that I've written uses wince...so this is a bummer. Do you
happen to know how long it will take to develop this driver? Why isn't this
 mentioned in the webpage?

They use the same processor so they are almost the same system.

By the way the SDK has nothing to do with drivers for connecting the board
to the computer.  My understanding is that it's for Visual Studio to know
what components you installed in your NK.bin OS file so that when you write
an application it can check (at least to some extent) if your application
uses something that is not present in the OS.

I too was suprised by the driver not working but when I went back to the
webpages about it (Tiny210 and mini210) it does actually not claim to have
this driver supported for WinCE.  It says the hardware has the ability and
the driver for for Android but not WinCE.

But - if you wish to write and deploy apps you can get an activecync like
connection over Ethernet and do it this way.  I've been doing this and it
works fine.  
http://msdn.microsoft.com/en-us/library/ms228708%28VS.80%29.aspx

But you may need to rebuild the OS with activesync components added.

http://www.friendlyarm.net/forum/topic/1663

@BBBB. I don't have the platform builder on my computer, so I can't rebuild
the NK.bin file. Could you send me a copy of the NK.bin with the activesync
 component? You could upload it or ftp or something that you're comfortable
with. I didn't even know that you could upload programs via ethernet...
interesting. Thanks for the explanation!

@NothinRandom.  I'm sorry but my NK.bin has been heavily modified for a
commercial project so I'm unable to do this. Have you tried to get it to
work with Ethernet? Perhaps the ActiveSync components are already present
or maybe you don't actually need them.  

It's probably a good opportunity for you to try installing Platform Builder
and build your image. It builds almost straight away without too much
modifications. You'll learn so more more about the plaform once you know
how to build the OS.

@BBBB Yeah, I went through the steps: Tools->Options->Device
Tools->Devices->Properties->Configure->Use specific IP Address, but no
dice. I didn't check the use fixed port number, but I don't think it
matters. So, with this in mind, I don't think the NK files that came with
the DVD has active sync on it. By the way, where can I get platform
builder? Should I install xp since I'm running on win7?

@BBBB, it works! The speed is so much faster than using USB for some
reason. When I click on connect to device, it connects immediately vs the
USB...take a while to talk. Anyways, thanks for the help. For others with
the same issue, just follow the first link BBBB posted, then go through the
steps I've posted. Finally, I can get some development done.

Send me something and I'll post it on the product pages.

@TheRegnirps: This is taken directly from the link posted by BBBB

Follow this page:
http://msdn.microsoft.com/en-us/library/ms228708%28VS.80%29.aspx. 

To prepare the device for connecting

Using whatever connection with the device you have, copy the following
files to the \Windows\ folder on the device. These files are located on the
development computer by default at \Program Files\Common Files\Microsoft
Shared\CoreCon\1.0\Target\wce400\<CPU>.

Clientshutdown.exe

ConmanClient2.exe

CMaccept.exe

eDbgTL.dll

TcpConnectionA.dll

From the command prompt on the device, run conmanclient2.exe.

Determine the IP address of the device.

To prepare Visual Studio for connecting

On the Visual Studio Tools menu, click Options, then click Device Tools,
and then click Devices.

Select Windows CE Device, and then click Properties.

To the right of the Transport box, click Configure.

In the Configure TCP/IP Transport dialog box, select Use specific IP
address, and then type the device IP address.

Close the dialog boxes.

A message box might appear prompting you to reset your device. If so, a
soft reset is sufficient.

The FriendlyARM engineers jumped on this and it is on the ARMWorks
downloads page at andahammer.com. Check the July Updates section where it
has a name lime WinCE6Ether210 or something like that.

@TheRegnirps: They put the wrong version of Conman Client on there. I think
they put the ARMV4 instead of the ARMV4I because it says "The version of
Conman Client running on the device is incompatible with the desktop."

I've fixed the USB OTG driver for Windows CE 6.  I've submitted it to
FriendlyArm to test and they should release it with their next BSP update. 
Hopefully this will be soon.

Is it me or did they released the .nk files that don't have CAB installer
and HIVE-based memory? I can't install anything. Also, the board resets
every time I boot up; I lose everything.

Hi,

I guess you have difference expectations about the supplied nk.bin then
FriendlyArm.  They are just as a proof that the BSP source works when
building - but then it's up to you to set it up and build the version you
actually need.

It's very simple process to add CAB installer support, Hive registry is
fairly straightforward too but I'd admit a fraction harder.  But to do
these things you need to install platform builder into VS2005.

You can freely download Platform Builder as a 6 month trial from Microsoft.
 And there are easily discovered websites showing how to install it on a 64
machine as I had to do.

I'd suggest installing it and it will help with your understanding of the
WinCE platform no end but of course you will need to devote a little time
to learn how to use the tools.  But then you will  be able to add the
capabilities you need to your nk.bin image.

@BBBB What would I do without you?

Hi, 

the MiniUSB driver is available now, and the new ISO file will be available
  next week, just wait.

mindee

and, thanks @BBBB, he help us to resolved this issue.

mindee

Hi Mindee,

Has this issue been address? I went on the ftp last night and saw the new
iso dvd that contains the nk file for mini210 dated 07/25/12. Is this the
latest one?

Do I need the device hooked up in order to build the bsp? I have one error,
and I can't figure out how to fix it to save my life!

IS MiniUSB Driver available now with new ISO?.

Yes it is now.

Why not just add Eboot Support on Ethernet instead of USB RNDIS. As most of
the developers (Hobbyist) like me have laptop with Windows 7 64 bit OS.
Laptop is normally is connected to home network using Wifi and Ethernet
port is ways free. so We can just hook up to MINI210 to this free Ethernet
port and use fro WinCE KITL intefrace instead of USB RNDIS Driver.

I was using Mini2440 from 2009, there also I had the same issue 64 bit OS
driver is not available. and Friendly arm is not willing to develop USB
driver, the Best reason they provide SAMSUNG is not providing 64 bit
driver. 

We dont need USB OTG driver for our development(hobby) purpose, JUST add
the ethernet support for download and debugging (kernel debugging ).

FA have shipped pre-built driver for the USB OTG named "fa_usbfn.dll" and
included it as additional file. The source code still not functioning but I
have fixed the OTG driver. The source code is very badly written and there
are too many bugs. I think it is Samsung's engineer fault when they try to
develop SMDKV210 BSP.