Active Topics

 


Reply
Thread Tools
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#11
Are there specific USB/Serial chipsets that work with this setup?

gLobster:
What USB/serial adapter are you using?Is it GEMBird, from the screenshot?
__________________
machinegrid.com
 
gLobster's Avatar
Posts: 203 | Thanked: 47 times | Joined on Jun 2007 @ St.Petersburg, Russia
#12
Yes. I only replace connector to miniA-USB with shorted 4 and 5 pins.
 
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#13
I finally got around to testing this... some success but some wierdness. I think it is some kind of terminal setting or maybe because I am using "screen".

I have an N800 with OS2008.
I loaded the usbserial drivers and ftdi driver into the kernel with no problem.
I manually put the N800 into host mode with "echo host > /sys/devices/platform/musb_hdrc/mode"
I get the same error message above about missing file system but I ignore it.
I then connected the USB serial adapter to another computer that I know has a working serial port.
At the N800 terminal, I type "screen /dev/ttyUSB0 57600,cs8,-ixon,-ixo" to get a terminal session at 57600 8 data bits, 1 stop bit, no parity, no flow control.
Characters typed on the N800 are received on the other computer as extended ascii character garbage with umlauts, accents, and weird symbold. However characters typed on the other computer are received just fine and displayed on the N800.

1. What terminal program (besides screen) are you using to access the serial port? Where can I get it?
2. Is there some character set settings on the N800 terminal that maybe is telling it to use extended ascii?

David
Any ideas?
__________________
David Smoot
 
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#14
Although you may have done it, on the PC side is your baud rate setting right and N81 with no flow control?

I also have an FTDI chip, but I'm waiting on my cable.
__________________
machinegrid.com
 
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#15
Should have done some more testing.... My problem was using screen for my terminal program. I found the link to pyserial in another thread and got that working on my N800 (I really gotta learn python someday). With pyserial I can send and receive perfectly. Now I am going to try and compile minicom in scratchbox since nobody seems to have posted it.

By the way, I saw your website. If you like state machines, you really need to check out www.quantum-leaps.com. Very cool stuff.

Update:
Building minicom could not have been much easier in scratchbox and it works like a charm!!! No warranties / guarantees but if anyone wants the minicom deb, just let me know.

David
__________________
David Smoot

Last edited by djs_tx; 2007-12-31 at 18:55. Reason: More info
 
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#16
Thanks!

Awesome!!.. Many people needed minicom ported.
Please can you pm me the deb link.

The quantum-leaps site is pretty interesting.
__________________
machinegrid.com
 
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#17
Ok, the usual blather.. no warranties / no guarantees. If your handheld suddenly burst into flames its not my problem.

You can download the minicom deb file here:
http://home.comcast.net/~davidsmoot/....2-5_armel.deb
__________________
David Smoot
 
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#18
Please let me know if the minicom port works for you. Is there a bluetooth serial device in /dev for OS2008 that I could use for wireless serial?

David
__________________
David Smoot
 
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#19
/dev/rfcomm*

where * is 0,1,2...
__________________
machinegrid.com
 
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#20
Im getting an "incompatible application type " error, while installing.
__________________
machinegrid.com
 
Reply


 
Forum Jump


All times are GMT. The time now is 09:28.