<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi Charles,</p>
<p>There has been some recent improvements in the patches related to
the device name etc. for the APBUART driver. The patches were
posted to the devel list. I'm planning on pushing them to master
tomorrow. Historically the APBUART1 would be /dev/console_b.<br>
</p>
<p>Best Regards,<br>
</p>
<pre class="moz-signature" cols="72">Daniel Hellstrom
Software Section Head
Cobham Gaisler
T : +46 (0) 31 775 8657
F : +46 (0) 31 421407
<a class="moz-txt-link-abbreviated" href="mailto:daniel.hellstrom@gaisler.com">daniel.hellstrom@gaisler.com</a>
Cobham Gaisler AB, Kungsgatan 12, SE-411 19, GÖTEBORG, Sweden.
+46 (0) 31 775 8650, <a class="moz-txt-link-abbreviated" href="http://www.cobham.com/gaisler">www.cobham.com/gaisler</a>
Please consider the environment before printing this email
This e-mail and any files transmitted with it ("E-mail") is intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the addressee(s), any disclosure,
reproduction, copying, distribution or other use of the E-mail is prohibited. If you have received this E-mail in error, please delete it and notify the sender immediately via our switchboard or return e-mail.
Neither the company nor any subsidiary or affiliate or associated company nor any individual sending this Email accepts any liability in respect of the content (including errors and omissions) nor shall this e-mail be deemed to enter the company or any subsidiary or affiliate or associated company into a contract or to create any legally binding obligations unless expressly agreed to in writing under separate cover and timeliness of the E-mail which arise as a result of transmission. If verification is required, please request a hard copy version from the sender. </pre>
<div class="moz-cite-prefix">On 2017-04-24 13:58, Charles INGELS
wrote:<br>
</div>
<blockquote
cite="mid:95626395-7c84-fbe0-c505-fad46b2f5002@syderal.ch"
type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<p>Hi Daniel,</p>
<p>thanks for your answer. The version I use is from the master
branch and the checkout has been done the 7th of march. It is
definitely not the latest release because I need to freeze one
version that I use to compile against the software applications
I am currently developing. This is mainly because each time I
make an "update", I have to go through a new integration test
cycle for each of the software apps, which can become very time
consuming, at least for the moment.</p>
<p>However, since that work is on the go, I might in a near future
update my RTEMS working copy and then go again into a hopefully
final test campaign, before releasing the latest final version
of the software apps.</p>
<p>Regards,</p>
<p>Charles</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 24.04.2017 à 12:41, Daniel
Hellstrom a écrit :<br>
</div>
<blockquote
cite="mid:68f6a546-9843-db5d-286c-333c63561a9c@gaisler.com"
type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<p>Hi Charles,</p>
<p>Sorry I missed to reply on your email. Thanks for reminding
me. Which codebase do you use, is it the current RTEMS master
or RCC-1.2?<br>
</p>
/Daniel<br>
<br>
<br>
<div class="moz-cite-prefix">On 2017-04-24 07:50, Charles INGELS
wrote:<br>
</div>
<blockquote
cite="mid:0af66c0e-1664-467b-8aed-107d52f9dc01@syderal.ch"
type="cite">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
<p>Hi Joel,</p>
<p>until now, I did not receive any answer from Daniel. I do
not know if my feedback has been taken into account, maybe
for other users if they have the same issue.</p>
<p>Nevertheless, the fix seems to work fine with no apparent
side effects.</p>
<p>Regards,</p>
<p>Charles</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">Le 11.04.2017 à 03:29, Joel
Sherrill a écrit :<br>
</div>
<blockquote
cite="mid:CAF9ehCVhWZ3LWWVrVudWwCedvLzg_aY71Og1f1M4xCkFtNBayg@mail.gmail.com"
type="cite">
<div dir="auto">I'm going to assume that Daniel didn't see
this since he didn't comment.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Apr 10, 2017 2:41 AM, "Charles
INGELS" <<a moz-do-not-send="true"
href="mailto:charles.ingels@syderal.ch">charles.ingels@syderal.ch</a>>
wrote:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000099">
<p>Hello,</p>
<p>By using the APB Uart BSP on a SPARC LEON3
target, I think that I have found something which
seems to be incorrect.</p>
<p>In my RTEMS app, I just want to receive data
through the UART1. Such data are then echoed on
the same interface.</p>
<p>When I want to open the '/dev/apbuart1'
descriptor, I get a 'No such file or directory'
error message. I get the same error message
whatever is the descriptor I try to open
('/dev/apbuart0', ...).</p>
<p>I am using the driver manager and I have defined
the CONFIGURE_DRIVER_AMBAPP_<wbr>GAISLER_APBUART
to have the driver manager create the device
descriptors. However, the descriptors are not
created.</p>
<p>I had a look at the content of the following file
:</p>
<p>U:\rtems\src2\rtems\c\src\lib\<wbr>libbsp\sparc\shared\uart\<wbr>apbuart_cons.c</p>
<p>On line #278, the if statement does not
explicitly test the value returned by the call to
function 'drvmgr_get_dev_prefix()'.</p>
<p>Since such function returns 0 in case of success,
the content of the if statement is never executed.
Consequently, the variable 'priv->devName' is
never initialized to the right string
'/dev/apbuart%d', it is always empty which seems
to explain why the device descriptor is not not
created.</p>
<p>I have slightly modified the test with the
following code :</p>
<pre>if (drvmgr_get_dev_prefix(dev, prefix) != -1)
{
...
}
</pre>
<p>I explicitly test the returned value against -1
(which is considered as an error). With that code,
the '/dev/apbuartX' device descriptors are
successfully created and communicate with the
UART.</p>
<p>So is it a known bug ? Will it be fixed in the
next releases ? Is the way I fixed it correct, or
no ?</p>
<p>Such fix works for me but are there some side
effects that shall be taken into account ?</p>
<p>Thanks for your answers,</p>
<p>Regards,</p>
<p>Charles</p>
<p><br>
</p>
<p><br>
</p>
<br>
<div class="m_-5841158778217462889moz-signature">--
<br>
<table border="0" width="750px">
<tbody>
<tr>
<td> <b>Charles INGELS</b><br>
Embedded software expert<br>
<font face="courier"><a
moz-do-not-send="true"
class="m_-5841158778217462889moz-txt-link-abbreviated"
href="mailto:charles.ingels@syderal.ch" target="_blank">charles.ingels@syderal.ch</a></font><br>
Phone <i><a moz-do-not-send="true"
href="tel:+41%2032%20338%2099%2010"
value="+41323389910" target="_blank">+41
(0)32 338 99 10</a></i> <br>
iNum <i>+883 5100 0902 7759</i> <br>
<br>
<b>SYDERAL SA</b> <br>
Neuenburgstrasse 7 <br>
CH-3238 Gals (Suisse) <br>
Desk <i><a moz-do-not-send="true"
href="tel:+41%2032%20338%2098%2000"
value="+41323389800" target="_blank">+41
(0)32 338 98 00</a></i> <br>
Fax <i><a moz-do-not-send="true"
href="tel:+41%2032%20338%2099%2034"
value="+41323389934" target="_blank">+41
(0)32 338 99 34</a></i> <br>
Web site <a moz-do-not-send="true"
class="m_-5841158778217462889moz-txt-link-freetext"
href="http://www.syderal.ch"
target="_blank">http://www.syderal.ch</a>
<br>
</td>
<td> <img
src="cid:part7.A82C8C60.86E2CCE3@gaisler.com"
height="65%" width="65%"> </td>
</tr>
</tbody>
</table>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
users mailing list<br>
<a moz-do-not-send="true"
href="mailto:users@rtems.org">users@rtems.org</a><br>
<a moz-do-not-send="true"
href="http://lists.rtems.org/mailman/listinfo/users"
rel="noreferrer" target="_blank">http://lists.rtems.org/<wbr>mailman/listinfo/users</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>