That shows that the TS-7390 was probably what missed an incoming
character since the simulator on the desktop sent two responses but the
TS-7390 only received one complete response.
You wrote: "When I run the DlpTempGSim on the PC, it times out after
about 15 seconds anyways regardless, surely this should stay running."
For these simple test programs I want the programs to crash if they miss
a character. It all works OK as long as you start the simulator right
before you start the DlpTempG program.
Can you run dmesg on the TS-TPC-7390 right after you plug in the USB to
serial adapter? That would show what chipset the adapter has.
Donal O'Connor wrote:
> Hi Again,
>
> Sorry about the wrong paste there. Here is the output from the TS7390:
>
> *ts7000:/home/eclipse/serialtest# ./DlpTempG
>
> Ports available: ttyS3 ttyS2 ttyS1 ttyS0 ttyUSB0 ttyAM2 ttyAM1 ttyAM0
>
> *** Press Ctrl-C to stop ***
>
> 1-1-70 00:30:08 S1 temperature C: -0.50 F: 31.10
> An unhandled exception occurred at $0001AB14 :
> ESynaSerError : Communication error 9997: Timeout during operation
> $0001AB14
> $00018198
> $00018290
> $0000849C*
> *
> *When I run the DlpTempGSim on the PC, it times out after about 15 seconds
> anyways regardless, surely this should stay running.
>
> I edited the pass files of both the program and sim and removed the exit
> statement since as far as I could see it would always exit anyways and set
> the device to /dev/ttyUSB0 on both which are both the Usb->Serial adaptors.
>
> I ran a dmesg on the TS7390 and the output doesn't look very nice:
>
> *ep93xx-ohci ep93xx-ohci: urb c16d9800 path 3 ep3in 6c160000 cc 6 --> status
> -71
> ep93xx-ohci ep93xx-ohci: urb c16d9800 path 3 ep3in 6c160000 cc 6 --> status
> -71
> ep93xx-ohci ep93xx-ohci: urb c16d9800 path 3 ep3in 6c160000 cc 6 --> status
> -71
> ep93xx-ohci ep93xx-ohci: urb c16d9800 path 3 ep3in 6c160000 cc 6 --> status
> -71
> ep93xx-ohci ep93xx-ohci: urb c16d9800 path 3 ep3in 6c160000 cc 6 --> status
> -71*
>
>>From what I could find on google, this is the USB host controller interface.
>
>
> This is the USB->Serial converter on the ts7390:
> http://www.usr.com/support/product-template.asp?prod=5700
>
> I will try the other suggestion there with ser2net later on the day.
>
> Thanks very much.
>
>
> Regards,
> Donal
>
>
> On Tue, Mar 24, 2009 at 10:05 PM, Paul Breneman
> <>wrote:
>
>> I have those serial programs purposely configured so they should crash
>> if they miss any characters. I just tried them again and at the program
>> default of 9600 baud it is all working well. I even started up Dillo on
>> my TS-TPC-7390 and browsed to a couple of web pages and it still didn't
>> miss any characters.
>>
>> I'm using the IOGear GUC232A USB to serial adapter. My adapter has the
>> pl2302 chipset (per dmesg) but be warned that adapter manufacturers have
>> been known to keep the same model number while switching to a completely
>> different chipset.
>>
>> I tried FTDI and moschip adapters but the default drivers for those on
>> the TS-7390 seem to have bugs that cause crashes when you use RTS or
>> DTR. The prolific pl2303 works with RTS & DTR. I'm not sure if the
>> later pl2303X chipset works or not.
>>
>> Let me know if I can test anything on my TS-7390 to help you
>> troubleshoot this.
>>
>>
>> Paul Breneman wrote:
>>> Hi Donal,
>>>
>>> It seems your cut-and-paste did not work for the dump from the TS-7390
>>> as it is a copy of your desktop dump.
>>>
>>> If you could get the correct one we might be able to see which end
>>> missed a character.
>>>
>>> I've run those programs without a problem so it does seem like your
>>> TS-7390 is what is at fault for some reason.
>>>
>>> Paul
>>>
>>>
>>> Donal O'Connor wrote:
>>>> Hi Guys,
>>>>
>>>> I am really sorry about the delay back, so busy with other college
>>>> stuff and
>>>> I got a bit sick there for a while.
>>>>
>>>> I am still experiencing this problem with the serial I/O.
>>>>
>>>> I have:
>>>>
>>>> - Moved to NAND flash
>>>> - Set the thread priority of the serial comm to time critical (QT)
>>>>
>>>> I am still getting the problem where I miss a character, the important
>>>> one
>>>> '>'
>>>>
>>>> I don't know if this is a problem of my own programming but since it
>>>> works
>>>> perfectly on my desktop machine, something has to be up.
>>>>
>>>> I have download the Serial testing program at:
>>>> http://www.turbocontrol.com/simpleserial.htm
>>>>
>>>> I run the *DlpTempGSim* program on my x86 development machine on
>>>> (/dev/ttyUSB0) where my usb->serial converter plugged in.
>>>>
>>>> I then have a null modem cable to my ARM device which is connected to
>>>> another usb->serial converter at same address, /dev/ttyUSB0.
>>>>
>>>> I run the *DlpTempG* program on this and I get interesting results.
>>>>
>>>> Output from Simulator on my development machine:
>>>>
>>>> :~/Desktop/Downloads/serialtestx86$ ./DlpTempGSim
>>>>
>>>> Ports available: ttyS3 ttyS2 ttyS1 ttyS0 ttyUSB0
>>>>
>>>> *** Press Ctrl-C to stop ***
>>>>
>>>> 24-3-09 17:23:19 sent response
>>>> 24-3-09 17:23:20 sent response
>>>> An unhandled exception occurred at $08062F2D :
>>>> ESynaSerError : Communication error 9997: Timeout during operation
>>>> $08062F2D
>>>> $080612B4
>>>> $0806136D
>>>> $08048225*
>>>>
>>>> Output from the program on the ts7390:
>>>>
>>>> :~/Desktop/Downloads/serialtestx86$ ./DlpTempGSim
>>>>
>>>> Ports available: ttyS3 ttyS2 ttyS1 ttyS0 ttyUSB0
>>>>
>>>> *** Press Ctrl-C to stop ***
>>>>
>>>> 24-3-09 17:23:19 sent response
>>>> 24-3-09 17:23:20 sent response
>>>> An unhandled exception occurred at $08062F2D :
>>>> ESynaSerError : Communication error 9997: Timeout during operation
>>>> $08062F2D
>>>> $080612B4
>>>> $0806136D
>>>> $08048225
>>>> *
>>>>
>>>> Now the two of them seem to be communicating but after a few seconds it
>>>> crashes.
>>>>
>>>>
>>>> Anyone have any ideas or pointers? - Should I try another driver? If so
>>>> which one.
>>>>
>>>> Hope someone can help.
>>>>
>>>> Thanks very much.
>>>>
>>>> Regards,
>>>> Donal
>>>>
>>>> On Wed, Feb 25, 2009 at 1:16 PM, Matthew Harrell <
>>>> <lists-keyword-yahoo.fd265e%40bittwiddlers.com>>
>> wrote:
>>>>>> From working on a 2.6.27 port of the SD card stuff, I've found a
>>>>> couple
>>>>>> bugs in the sdcard driver (and I know that a few remain). The one
>>>>>> you're experiencing is due to the fact that the driver enters atomic
>>>>>> mode (unnecessarily) while transferring data to/from the sdcard.
>>>>>>
>>>>>> Even when I release the atomic mode, the sdcard performance is about
>>>>>> 87k/second on a ts7400 and requires 100% cpu load, even after I got
>> rid
>>>>>> of the while (!(DMA_READ(STATUS) & 0x40)) ; busy wait.
>>>>>>
>>>>>> What is more interesting is that their 2.4 driver does about 1.3
>>>>>> megabytes per second running under linux 2.4.
>>>>> Interesting. Does this problem occur only when you're writing to the
>>>>> card or does it also happen periodically when the system writes
>>>>> something
>>>>> to the card?
>>>>>
>>>>> Do you have a version of your driver I can experiment with?
>>>>>
>>>>> --
>>>>> Matthew Harrell Another Month's End:
>>>>> Bit Twiddlers, Inc. All Targets Met
>>>>> <mharrell%40bittwiddlers.com> <mharrell%
>> 40bittwiddlers.com> All Systems
>>>>> Working
>>>>> All Customers Satisfied
>>>>> All Staff Enthusiastic
>>>>> All Pigs Fed And Ready To Fly
------------------------------------
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|