MINI210/TINY210 bootloader on ethernet instead of USBRNDIS

USB Drivers(64bit windows OS) for Friendly-arm supplied board is very bad.
I had mini2440 since 2009, and till now I cannot find 64 bit USB drivers
for that board, and it is same case with all the other boards. Recently I
purchased TINY210 just seeing the specs, but after purchasing this board I
realized that I have done mistake. I saw wince support is available for
this board before purchasing this board, just purchased, but later found
out i can only download image to device using crappy superboot.bin. 


I think majority of the customers using this board are hobbiest or someone
who just want to learn about WinCE or androd/linux. and most of them are
not going to use it for product development. And majority of people use a
home laptop for learning purpose. 

As USB driver not available for frendly-ARM boards for 64 bit OS, we cannot
use it for learning. In my case(kernel and driver development), I want use
kernel debugging which is possible when Device Connects to the Visual
Studio at boot time. And As USB driver and not available I cannot do it to
connect to board for debugging purpose. However I can debug application
using activesync over ethernet when device completely loads.

I need to use these boards for learning Driver development, and not for
application development. frendly-ARM needs focus on providing basic
infrastructure for debugging and downloading first than just adding fancy
MP4 decoder stuffs.

When most of the laptops have unused LAN port, which can be used for kernel
debugging, instead of USB driver, why not just use that.
I initially thought that I can add support for bootloader and ethernet, but
I dont have JTAG bebugger (Exdi interface) to connect to the Device for
bootloader debugging, and without it is very difficult to debug just using
serial debug messages.

I recently purchased TI Beaglebone(ARM cortex a8 processor) and I was able
to port the BSP. I used EVM335x Reference BSP and ported to Beaglebone. It
was because they had eboot with ethernet support. So I can Hook up device
to the spare ethernet port. 

So, I request friendly arm to provide eboot software over ethernet instead
of USB. and also superboot, we dont need it.

Thanks,

You need to learn to search better, there is definitely a 64bit drivers for
the mini2440.

The majority of customers aren't hobbyists, they're OEM, we're just a small
fraction of the customers for these boards. You could however write your
own u-boot port or similar, which is generally what hobbyists end up doing
if the manufacturer/supplier won't do it for you.

I'm still not sure what usb will give you over jtag, why don't you just
purchase the correct tools for the job?  You're happy to spend $150 on a
board but not $20-30 on the tools that will allow you to develop more on it
and probably all of the other boards you might own.

@reggie
Are you sure majority of customers are OEMS?.. and what is the problem in
having eboot instead of superboot for mini210, the standard Microsoft
bootloader for WInCE os.

If you dont understand why we need USB and Jtag support. Please do a proper
research before commenting.. For debugging WinCE platfporm using Jtag we
need EXDI interface(software), for that i think most of Cheaper Jtag dont
have support. I have Jlink and Ulink and Parallel Jtag, unfortunately
cannot use it, as they dont have Exdi interface. 

Assume I am writing a Kernel mode driver for Windows Ce and I want to load
it at Boot time, I cannot debug as my USB driver over which Kernel debugger
is connected for debugging purpose.

@reggie
Tell me Where is 64 bit USB driver for Mini2440, that i can use for
downloading and also debugging over platform builder. If you managed to
find is please post it in forum so that every one is benefited.

I dont want to use uboot..

http://code.google.com/p/supervivi-transfer-tool/downloads/detail?name=S...=

And yes, I'm very sure that most of their customers are not hobbyists :-)

@Reggie

I am aware of this tool its for MINI2440, you can download OS image using
USB, but cannot be used for debugging and using Kernel Debugger. As i
mentioned earlier that without using kernel debugging IT is very difficult
to debug the WinCE drivers. We can use serial output but it is very time
consuming process. sometime you just want to breaking and watch registers
or call stack. It is very hard to achieve, using serial debug.

For mini210 there is no 64 bit drivers. I was suggesting as DM9000 eboot
drivers are already available in davicomm website, so why not just
integrate it with eboot and give us. Once Bootloader is working (eboot),
then things will be easy for us. When Wince Image loads the KITL inteface
is up and KDBG(Kernel debugger) is up and running we can just do any
debugging. We can even break in Kernel loading.  So you can say If someone
wants to work in WinCE, the KDBG is mostneeded. It can be up by JTAG or
KITL(Ethernet or USB or serial). Once KITL communication is up we can use
some of the powerful tools like KernelTracker, CELog etc to debug drivers.
As you know friendlyarm is not only cheap development kit. Recently I heard
RASPBERRY PI ($35) will also get WinCE 7
OS(http://bolingconsulting.com/2012/i-have-a-new-raspberry-pi/).There are
other powerful and Cheaper boards in the market like BeagleBoard and
BeagleBone, they provide STEPLDR and EBOOT Binaries that we can use to
connect to Platform Builder. As BSP for these boards are not open source,
still we can port the Reference BSP to these boards by using the binaries. 

As stated earlier to debug WinCE OS using PlatformBuilder we need exDI
interface, and It is available with few expensive debuggers like lauterback
or RealView ICE. They cost a lot. And Tiny210 there is no JTAG interface
available. So Jtag option is ruled out. 

Integrating Ethernet drivers should not be hard, FriendlyARM
(www.ARM9home.net) are using Trace32 (lauterback) for debugging purpose, so
it will not be hard for them.

So, If any moderator reading this post I request you to provide Ethernet
boot-loader, so that I will help more and more people like me to develop
new things for these community boards.