1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 <2019> 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Serial port bus connection issue on arm platform |
From: | "Johnson, Andrew N. via Tech-talk" <[email protected]> |
To: | "Seeberger, John T CIV USN NAS PAX MD (USA)" <[email protected]>, "Rivers, Mark L." <[email protected]>, "Kasemir, Kay" <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Thu, 7 Nov 2019 20:23:11 +0000 |
Hi, On 11/7/19 12:01 PM, Seeberger, John T CIV USN NAS PAX MD (USA) via Tech-talk wrote:
One thing I was wondering would there be away to build and have both linux-arm32, and linux-arm64 platforms. Rather then just linux-arm. EPICS Base allows you to create your own local target architectures based on the build configuration of another existing architecture. The easiest way to show this is to look in the base/configure/os directory at the *.linux-arm_eb* or *.linux-arm_el* files, which include the linux-arm target files and then override some settings. You could create files for say linux-aarch64; you just need to ensure that you have the environment variable EPICS_HOST_ARCH set to that on your aarch64 system since our EpicsHostArch.pl script doesn't currently know how to distinguish that. I would be happy to add such configuration files (and any modifications to the EpicsHostArch.pl script) to Base if you can offer them. HTH, - Andrew ________________________________________ From: Mark Rivers [[email protected]] Sent: Thursday, November 07, 2019 11:37 AM To: Seeberger, John T CIV USN NAS PAX MD (USA); Kasemir, Kay Cc: [email protected] Subject: [Non-DoD Source] RE: Serial port bus connection issue on arm platform Hi Thad, The answer is in your original post. You showed this output: dbior "stream" Driver: stream StreamDevice 2.7.7 built Oct 24 2019 13:43:29 registered bus interfaces: DebugInterface DummyInterface I get this output on my system: epics> dbior "stream" Driver: stream StreamDevice 2.8.STREAM_PATCHLEVEL built Nov 2 2019 14:06:26 registered bus interfaces: AsynDriverInterface DebugInterface DummyInterface Note that you are missing the AsynDriverInterface. So the problem appears to be the way your built stream. Please check the stream/configure/RELEASE file, etc. Mark -----Original Message----- From: Tech-talk <[email protected]> On Behalf Of Seeberger, John T CIV USN NAS PAX MD (USA) via Tech-talk Sent: Thursday, November 7, 2019 10:26 AM To: Kasemir, Kay <[email protected]> Cc: Seeberger, John T CIV USN NAS PAX MD (USA) via Tech-talk <[email protected]> Subject: RE: Serial port bus connection issue on arm platform Works fine on the aarch64 and x86 version, so I'd say no. Thad ________________________________ From: Tech-talk [[email protected]] on behalf of Kasemir, Kay via Tech-talk [[email protected]] Sent: Thursday, November 07, 2019 11:17 AM To: Seeberger, John T CIV USN NAS PAX MD (USA) via Tech-talk Subject: [Non-DoD Source] Re: Serial port bus connection issue on arm platform Just a silly idea: Is "SERIALPORT" simply too long for the stream device? I've mostly seen examples like "P1" for ports. 2019/11/07 16:04:56.709466 _main_ Cannot find a bus named 'SERIALPORT' for 'aoa' -- Complexity comes for free, Simplicity you have to work for. |