What is the difference between rommon and u-boot in network devices? I'm reading some device documentation and i can't quite tell what is the difference.
Rommon is Cisco bootloader for their Router devices
while U-boot is a very generic bootloader for lots of embedded device
both U-boot and Rommon support tftp
U-boot Support sntp nfs while Rommon dont
u-BOOT may not support booting of raw vmlinux image but ROMMMON(rom on monitor) has support for loading and booting the raw vmlinux image.
Related
I would like to write a linux driver for a piece of hardware that has an FTDI (0403:6001) built in. There is a driver for Windows.
I was able to sniff the usb-traffic using wireshark and a virtual machine. Like this, I could filter out the serial messages sent, but don't know how to configure baudrate etc. Also, the default values from pyserial do not work.
Is there a way to read out the configuration of the FTDI from the USB sniffs?
when an FTDI is attached to linux machine the kernel modules ftdi_sio and usbserial are loaded
source code is in https://github.com/torvalds/linux/blob/master/drivers/usb/serial/ftdi_sio.c and https://github.com/torvalds/linux/tree/master/drivers/usb/serial
if you want to talk to the FTDI chips directly you can use the libftdi library on linux https://www.intra2net.com/en/developer/libftdi/
for sniffing the USB protocol communication of an FTDI chip with wireshark see this : https://www.wireshark.org/lists/wireshark-bugs/201511/msg00579.html
you have to load usbmon kernel module for sniffing the FTDI https://wiki.wireshark.org/CaptureSetup/USB
There's a sample provided for CDC compliant USB devices here. Are vendor-specific USB devices supported too? Or are CDC compliant USB devices the only ones supported in Metro apps?
Your help is much appreciated!!
Vendor specific USB to UART bridge devices will not be supported under CDC, only a USB CDC class device would be supported in that case.
However, since Microsoft has opened up a USB API you could still access vendor specific devices. The downside here is that the devices will not look like a COM port, you would need to use the Windows.Devices.Usb namespace to access the device directly through it's USB protocol. This means that the vendor for a specific device would need to publish their protocol, or you could reverse engineer or use the Linux source as an example of what the setup packets for certain commands should look like.
Since you're using an FTDI converter you can get the device protocol information from their Linux Source (this is from 3.13 kernel) and use this to access the device through Windows RT.
FTDI might support Win RT in the future (today is 2014-Apr-15), you can ask for a beta driver here:
Windows RT Driver
For a hobby project I wish to develop some stuff for a WinCE 6.0 device. Ideally, I would have an activesync connection to debug from Visual Studio. The OS appears to have all the prerequisites in place, but I'm not sure about the transport. What are my options?
The device has a USB port which can be used to connect e.g. flash drives for mp3 playback, so this seems to be a USB host port. Can I use this to obtain an activesync connection? I guess using a usb-to-serial cable on both pc and WinCE device could work. Or is there a RNDIS way perhaps?
If possible I rather not disassemble the unit, but if my chances of finding a USB client port or wired ethernet are nonzero I could consider that. Any thoughts?
You can not use USB host port for Activesync connection.
But if it is USB OTG (Both host and client) port, you can use activesync using USB OTG or USB Client functionality.
Your BSP should support USB Serial Client functionality (Search SYSGEN_USBFN_SERIAL sysgen variable in catalog items).
Also, your USB driver (lower level driver) should support USB Client functionality.
ActiveSync will work on a serial cable, so the idea of using an USB-to-serial adapter may work. But you need to have drivers for it in the OS image. There are some CDC drivers and FTDI provides drivers for their chips. You may be able to load them on the device, copying them using a USB thumbdrive and modifying the registry using a registry editor for windows CE, but that's not granted. Windows CE also supports RNDIS compatible USB to ethernet adapter but honestly I don't know if any device of this kind is currently available on the market. If your device has wi-fi connectivity you can skip using ActiveSync and debug over the network.
Can MVAPICH2 be installed on a normal ethernet network other than InfiniBand or other HPC networking technology?
The very first line on the MVAPICH2 web site reads:
MVAPICH2 (MPI-3 over OpenFabrics-IB, OpenFabrics-iWARP, PSM, uDAPL and TCP/IP)
Then from the list of supported interfaces:
TCP/IP-CH3: The standard TCP/IP interface (provided by MPICH2) to work with a range of network adapters supporting TCP/IP interface. This interface can be used with IPoIB (TCP/IP over InfiniBand network) support of InfiniBand also. However, it will not deliver good performance/ scalability as compared to the other interfaces.
Therefore - yes.
com0com is a great program to have virtual serial ports.
My question: is there any library which I can use for simulating serial ports (COM, USB and so on) programmatically in my application without install extra software for such virtual devices?
something like making virtual device in user space?
OS: Windows
Free Virtual Serial Ports by HHD Software Ltd is good for you (License Freeware).
Excerpt:
This device driver implements the functionality of the virtual serial
port device. It operates in user mode space, unlike most other device
drivers, making the system more stable and secure.
Read more.
All similar software use a special kernel mode driver. It is not possible create a virtual COM port from user space.