Thread: [Flashforth-devel] Issues controlling flashforth from windows application via usb serial port
Brought to you by:
oh2aun
From: Bob E. <bob...@ti...> - 2018-04-21 15:38:57
|
I have a pic18f4553 board set up for USB serial link. It is going to control an antenna tuner from a linx 10 tablet running 32 bit windows 8, which also hosts a software defined radio (ham radio). In windows 8, I have to use zadiq to install the USB serial port for flashforth because it is not a registered product - that's OK. I use teraterm to program and manually test flashforth. This works reliably with inter-char and inter-line delays fitted. The delays seem to be needed when loading flashforth from a file, else it can fail. Thus I know that extended communication between teraterm and my flashforth board works. I've downloaded some large files to further test this. However, I want to control the flashforth board from a control application written in LabView on the tablet. When I use the serial port library that comes with LabView, it fails to open the flashforth port, although it successfully opens COM1, a normal serial port (but no external connector so not usable) I wrote my own serial port driver in LabView that directly calls the windows serial port api. Still not successful - I get a blue screen of death after up to 200 messages to and fro with the BSOD message *"STOP 0x0000000A: IRQL_NOT_LESS_EQUAL – usbser.sys".* Is the flashforth usb port fully compliant to the standard? Calling the api to read the settings of the port completes successfully (returns the DCB structure) but writing a modified DCB to the port fails (to set 9600,n,8,1,n,Xon/Xoff etc ). Doing the same thing to COM1 works. This is probably what prevents the labview library from opening the port since it assumes you would always want to set baud rate etc. What I want to know is, has anyone successfully controlled flashforth via usb serial link from Windows 7/8/10? What were the details and did you have this same problem along the way? (It's quite possible I have a bug still in my code or that USBSER.SYS is corrupt) Cheers, Bob G4BBY * * |
From: hc <ml...@i2...> - 2018-04-23 03:54:06
|
in https://sourceforge.net/p/flashforth/mailman/message/36299729/ When I was trying to use pic18 USB last year, I couldn't find/use the port from Realterm. I don't remember exactly what the problem was now, and reflashed for uart. At the time I thought that there is something not right in the USB info so it is not creating a vcp properly Anyway you can try Realterm and see if it works for you. When you plug a USB device in, Realterm shows it on notification. https://realterm.i2cchip.com/ Realterm_BUG_TESTERS_ONLY_BETA2_3.0.1.45_setup.exe This version has the Send tab comboboxes changed, so you can just type lines then <enter> and they are sent, so more fluid as a FF console. If there is any interest, I may add more FF support. Discuss here: https://sourceforge.net/p/flashforth/discussion/726813/thread/f2531242/ |
From: hc <ml...@i2...> - 2018-04-23 04:31:27
|
in https://sourceforge.net/p/flashforth/mailman/message/36299729/ When I was trying to use pic18 USB last year, I couldn't find/use the port from Realterm. I don't remember exactly what the problem was now, and reflashed for uart. At the time I thought that there is something not right in the USB info so it is not creating a vcp properly Anyway you can try Realterm and see if it works for you. When you plug a USB device in, Realterm shows it on notification. https://realterm.i2cchip.com/ Realterm_BUG_TESTERS_ONLY_BETA2_3.0.1.45_setup.exe This version has the Send tab comboboxes changed, so you can just type lines then <enter> and they are sent, so more fluid as a FF console. If there is any interest, I may add more FF support. Discuss here: https://sourceforge.net/p/flashforth/discussion/726813/thread/f2531242/ |
From: Mikael N. <mik...@fl...> - 2018-04-21 20:26:03
|
You are right. FF does not store new serial settings. I removed that part when I made the USB code as small as possible. Maybe I can put it back, I did not realize it would cause problems, since the terminal emulators do not seem to care about that part. BR Mikael On 2018-04-21 18:25, Bob Edwards via Flashforth-devel wrote: > > Is the flashforth usb port fully compliant to the standard? Calling > the api to read the settings of the port completes successfully > (returns the DCB structure) but writing a modified DCB to the port > fails (to set 9600,n,8,1,n,Xon/Xoff etc ). Doing the same thing to > COM1 works. This is probably what prevents the labview library from > opening the port since it assumes you would always want to set baud > rate etc. > Cheers, Bob G4BBY |