ClearChain » serial http://www.clearchain.com/blog -= Daily Happenings =- Wed, 05 Oct 2011 23:02:52 +0000 en hourly 1 http://wordpress.org/?v=3.2.1 Solution: Belkin F5U409 USB to Serial Converter in 64bit Windows 7/Vista/Mac OSX 10 http://www.clearchain.com/blog/posts/how-to-use-a-belkin-f5u409f5u409-cu-usb-to-pda-serial-converter-in-visawindows-7-64bit-mac-osx-10 http://www.clearchain.com/blog/posts/how-to-use-a-belkin-f5u409f5u409-cu-usb-to-pda-serial-converter-in-visawindows-7-64bit-mac-osx-10#comments Fri, 10 Dec 2010 13:40:38 +0000 Benjamin Close http://www.clearchain.com/blog/?p=835 This article details how to use a Belkin FSU409 USB to Serial Converter under Windows Vista/Windows 7 64bit]]>  

(Note: Mac Users may want to skip to the bottom)

After a number of years my old Windows Vista 32 bit installation was a little worse for ware. Having a laptop capible of 64 bit I decided to upgrade to Window 7 64 bit. After a fresh install of Windows 7, I began the process of installing drivers for the hardware I had. It wasn’t until I came to my trusty Belkin USB to Serial (RS232) converter, aka PDA adapter that I encountered a problem.

After visiting Belkin‘s website and looking up the driver page for the convertor, I discovered that Belkin didn’t support both Vista 64bit and Windows 7 64 bit.  Here’s the details from their knowledge base page (can’t link it due to thier website design):

“Is the F5U409 USB PDA Adapter compatible with vista 64 bit?
No, this product is not compatible with vista 64 bit. It is compatible with Vista 32 bit computers. We do however have a similar adapter which is compatible with Vista 64 bit, you can use part F5U257 (USB-to-Serial Adapter).”

What a rip off? Not only doesn’t Belkin support their old hardware they try and get me to buy their new hardware!

Being a computer system administrator and programmer by trade, I knew there would be no physical reason the device would not work under a 64 bit operating system. It was down to Belkin not wanting to spend the time or money to update the driver. In most cases, it would simply be a recompilation of the existing driver.

Hence I began searching to see if anyone had got the device working. There was lots of webpages/forum posts about how people failed. Lots of posts indicating it’s not supported, even an official microsoft page indicating it’s not supported under Microsoft Windows 7. Then there were a few posts indicating to try various different drivers, most seem to relate to either the Prolific or FTDI chip/chipset which apparently exists on other models of the Belkin adaptors (F5U109?) and with other USB/RS232 converters and hence works with some other drivers. But sadly nothing about the Belkin F5U409 adaptor.

Hence I figured enough is enough. I had previously found a website where someone had pulled the adaptor apart to determine if the chipset was an FTDI chipset. Sadly it wasn’t it was instead a Philips P87C52X2BA  microcontroller seemed to be used. Hence I did a lot of searching for that particular chip in google, all with no luck. Eventually I thought hmm, lets just see if we can find another USB232 converter that used a Philips chip.

Magic Control Technologies U232-P9 Adaptor

It was then that I found the MCT U232-P9 DB-9 Serial Adapter High Speed 230K USB SERIAL RS-232. This device used the “P87C52 – 80C51 8-bit microcontroller and PDIUSBD12 made by NXP Semiconductors founded by Philips.” It was perfect the chip matched. I hence spent quite a while working out who MCT were. It turns out that MCT stands for Magic Control Technologies. On the MCT website, on their driver page they had drivers for their USB/Serial convertor and they support Visa, Windows 7, 32bit & 64bit. So I downloaded the driver U232-P9 Driver.(Click Here for a Local Mirror incase MCT remove it)

I then crossed my fingers and installed it. After a quick reboot I plugged in my Belking F5U409 adaptor and it was detected! A quick check. It worked!

So to Belkin who wanted to force me to buy yet another product – support your products!

As a bit of an ironic twist, I later began cleaning up the original installed Belkin driver (I had tried the Vista 32bit version with no success). It was then that I discovered that Belkin don’t even write their own drivers but use Magic Control Technologies drivers!  (You can find this by right clicking on the u2sxp.sys file that Belkin installs to C:\Program Files(x86)\Belkin\F5U409\Driver\u2sxp.sys and clicking the details tab). So not only are they not updating the drivers, they didn’t write them in the first place!

Finally, if your a Mac OSX 10 user you might also want to check the Magic Control Technologies driver page as drivers exist for you as well – shame on you Belkin.

]]> http://www.clearchain.com/blog/posts/how-to-use-a-belkin-f5u409f5u409-cu-usb-to-pda-serial-converter-in-visawindows-7-64bit-mac-osx-10/feed 72 Using Serial Devices in FreeBSD / How to set a terminal baud rate http://www.clearchain.com/blog/posts/using-serial-devices-in-freebsd-how-to-set-a-terminal-baud-rate http://www.clearchain.com/blog/posts/using-serial-devices-in-freebsd-how-to-set-a-terminal-baud-rate#comments Fri, 08 Jan 2010 00:33:56 +0000 Benjamin Close http://www.clearchain.com/blog/?p=674 Recently I was working on a php command line program that required access to a serial port. Initially developed under Linux the program was then shifted to it’s permanent location on a FreeBSD server. This is where we first started having problems. Initially we discovered the server didn’t have a native serial port. We fixed [..more..]]]> Recently I was working on a php command line program that required access to a serial port.

Initially developed under Linux the program was then shifted to it’s permanent location on a FreeBSD server. This is where we first started having problems. Initially we discovered the server didn’t have a native serial port. We fixed this using a USB to serial converter/dongle (FTDI Chipset). This was fine as FreeBSD has the ufdti kernel module. Upon loading the module new devices appears in /dev

crw-rw----  1 uucp  dialer    0, 157 Oct  6 08:39 /dev/cuaU0
crw-rw----  1 uucp  dialer    0, 158 Oct  6 08:39 /dev/cuaU0.init
crw-rw----  1 uucp  dialer    0, 159 Oct  6 08:39 /dev/cuaU0.lock
crw-rw-rw-  1 root  wheel     0, 154 Jan  8 10:50 /dev/ttyU0
crw-------  1 root  wheel     0, 155 Oct  6 08:39 /dev/ttyU0.init
crw-------  1 root  wheel     0, 156 Oct  6 08:39 /dev/ttyU0.lock

We attempted to connect to our device using screen (screen /dev/ttyU0 115200) and everything worked as expected. We could send AT commands to the device all ok.
We then stopped screen and ran our php program. It ended up hanging on a fgets call to the serial port. This is really strange we though.
Next we queried the port to find out what baud rate it was set at:

>stty -f /dev/ttyu0
speed 9600 baud;
lflags: echoe echoke echoctl
oflags: tab0
cflags: cs8 -parenb

Strange we thought as we’d just connected with screen at 115200. Under linux we use screen to set the baud rate, all other programs accessing the port use the port at 115200. So what had set it back to 9600 baud?
We tried to use stty to set the speed:

>stty -f /dev/ttyU0 speed 115200
>stty -f /dev/ttyu0
speed 9600 baud;
lflags: echoe echoke echoctl
oflags: tab0
cflags: cs8 -parenb

What on earth was happening? We set the speed to 115200 but directly quering the port again indicated it was still at 9600 baud? At this point we were perplexed.
Eventually we found the solution. The newer FreeBSD terminal drivers provide the *.init devices, in this case /dev/ttyU0.init . These devices indicate the terminal settings to be applied to the terminal when the device is closed. Whilst Linux leaves the device in the same state the last program put the port into, FreeBSD restores the terminals state to what ever is specified in the init file. So a quick command:

> stty -f /dev/ttyU0.init -icanon -isig -echo echoe echok echoke echoctl -icrnl -ixany -imaxbel ignpar -opost -onlcr -oxtabs cs8 -parenb -hupcl clocal

And then to check:

> stty -f /dev/ttyU0
speed 115200 baud;
lflags: -icanon -isig -echo echoe echok echoke echoctl
iflags: -icrnl -ixany -imaxbel ignpar
oflags: -opost -onlcr -oxtabs
cflags: cs8 -parenb -hupcl clocal

Excellent. The terminal was now configured exactly how we wanted. We ran the program and it worked like a charm!

]]> http://www.clearchain.com/blog/posts/using-serial-devices-in-freebsd-how-to-set-a-terminal-baud-rate/feed 1