> -----Ursprüngliche Nachricht----- > Von: Chris Johns [mailto:[email protected]] > Gesendet: Mittwoch, 8. April 2020 02:57 > An: Sommer, Jan; [email protected] > Betreff: Re: rtems-test with serial device and run.cfg > [...] > > Which seems to be caused by this: > > > > Traceback (most recent call last): > > File "stty.py", line 77, in __init__ > > self.fd = open(dev, 'rw') > > ValueError: must have exactly one of create/read/write/append mode > > > > I am not that familiar with the rtems-test internals. Do I need a different > kind of configuration? > > How do others use the "bsp_tty_dev" option (e.g. in the tftp tester)? > > The issue with direct tty access and the need to port PySerial to > rtems-test via the rtemstoolkit. The requirements of the rtems-tools > repo make depending on external packages for specific functionality > problematic. > > Adding PySerial is a welcome addition to the toolkit but I have not had > the time to complete this task as `ser2net` has been a suitable and > stable alternative. I use ser2net for PC testing from it's serial port. >
Since I am going through the documentation again, I have a follow-up question. In this page https://docs.rtems.org/branches/master/user/testing/configuration.html#configuration-scripts there is the following example user configuration: [bsp-special] bsp = example-bsp bsp_tty_dev = /dev/ttyUSB2 bsp_tty_settings = B115200,~BRKINT,IGNBRK,IGNCR,~ICANON,~ISIG,~IEXTEN,~ECHO,CLOCAL,~CRTSCTS,VMIN=1,VTIME=2 What I understood from your explanation, then this is currently not supported, hence ser2net is needed as a middle-man? Should that be updated as well then or do you want to keep it for a soon-to-add feature? Have a nice break, Jan > I hope this helps. > > Chris _______________________________________________ users mailing list [email protected] http://lists.rtems.org/mailman/listinfo/users
