<div dir="ltr"><div dir="ltr"><div>Hi,<br></div><div><br></div><div>Sorry for not providing detailed explanations and for the late response.<br></div><div><br></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 2, 2021 at 5:31 PM Christian Mauderer <<a href="mailto:oss@c-mauderer.de" target="_blank">oss@c-mauderer.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Husni,<br>
<br>
On 01/05/2021 23:38, Ahamed Husni wrote:<br>
> Hi all,<br>
> <br>
> My project proposal<br>
> <a href="https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing</a> <br>
> <<a href="https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing</a>><br>
> <br>
> I tried to set up the JTAG Environment for the Beaglebone Black.<br>
> But I couldn't find the hardware anywhere in my country (Sri Lanka).<br>
> <br>
> I tried to,<br>
> <br>
> 1. Find TI XDS Debuggers<br>
> 2. Find a TI Launchpad so we can isolate and use the debugger in it.<br>
<br>
I assume you didn't find these? </blockquote><div><br></div><div>Yes, that was the case until yesterday. Luckily I was able to find a TI Launchpad CC1310 board.<br></div><div>Due to the Covid situation in the country, I'll only be able to get the hardware on Monday.<br></div><div>So until then I won't be able to try anything related to JTAG.<br></div><div>Also I will need an ARM10-cTI20 JTAG adapter to use the XDS110 debugger in the launchpad. I'll find it asap.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> 3. Use RPi as a debugger using OpenOCD<br>
<br>
I would have expect that one to work (like nearly any OpenOCD debugger). <br>
What was the problem? Did OpenOCD detect the processor? What pins did <br>
you connect? Please provide some more details so we might can help with <br>
tips.<br>
</blockquote><div><br></div><div>No. I didn't try it myself. <br></div><div>I found a discussion in TI. It looks like someone has tried it and wasn't successful.</div><div>I didn't understand most of the technical stuff in the discussion.<br></div><div>It seems like he was able to program with JTAG but not debug.<br></div><div><a href="https://e2e.ti.com/support/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly" target="_blank">https://e2e.ti.com/support/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly</a></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
By the way: If you get it running it might would be a nice addition to <br>
the user manual:<br>
<br>
<a href="https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-beagle-bone-black-using-a-jtag-debugger-and-gdb" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-beagle-bone-black-using-a-jtag-debugger-and-gdb</a><br>
<br>
That's currently mostly about the gdb part. You maybe could add two or <br>
three sentences and program calls how to start OpenOCD on a beagle and <br>
what pins can be used for it.<br>
<br>
> <br>
> I looked for the debuggers in major electronic shops, embedded systems <br>
> related companies,<br>
> university labs and etc. But couldn't find them.<br>
> Also these debuggers are expensive. When ordering online the shipping <br>
> charges are also high.<br>
<br>
I know from past GSoC that it can be difficult to get certain stuff in <br>
some countries. That's OK and I'm sure we find some solution.<br>
<br>
> So I can't guarantee that I can set up JTAG.<br>
> <br>
> Can we use RTEMS Libdebugger until we figure out the JTAG?<br>
<br>
I did too few stuff with libdebugger. So I don't know it really well. I <br>
_think_ that it needs a working network stack which would mean that you <br>
can only use it _after_ libbsd is initialized.<br>
<br>
Anyone: Please correct me if I'm wrong. If it would for example work <br>
with a serial interface, it should be OK.<br>
<br>
> Can we make a fallback plan for this project? If yes, what sorts of <br>
> changes should be made?<br>
<br>
I think the next best thing if you don't have a hardware debugger would <br>
be the RTEMS event recording. You have to instrument code and the <br>
processor has to be able to print an exception so you can get the data. <br>
You can't check anything on a instruction level but it's a great tool if <br>
you have to analyze the execution order of some problem cases. Most <br>
likely that will work for a lot of problems in your project too. So I <br>
would say that should be a fallback. Maybe you want to have a look at that:<br>
<br>
<a href="https://docs.rtems.org/branches/master/user/tracing/eventrecording.html" rel="noreferrer" target="_blank">https://docs.rtems.org/branches/master/user/tracing/eventrecording.html</a><br>
<br>
Basically it's adding a few CONFIGURE_RECORD_... defines to your <br>
application, receive events with rtems-record-lttng via network or from <br>
a serial dump and then using Eclipse Trace Compass to analyze the trace. <br>
Please speak up if you need help setting that up.<br>
<br></blockquote><div><br></div><div>For the last couple of days I've been learning about the rtems-libbsd.<br>I have built and installed the rtems-libbsd. I ran the Telnet testsuite on the hardware.</div><div>Serial output is <a href="https://pastebin.com/c7C2R7Fj" target="_blank">here</a>.</div><div><br></div><div>Next I'll try out the libdebugger and event recording till I get the JTAG hardwares.</div><div><br></div><div>Best regards,</div><div><br></div><div>Husni.<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Best regards<br>
<br>
Christian<br>
<br>
> <br>
> Best regards,<br>
> Husni.<br>
> <br>
> On Fri, Apr 2, 2021 at 6:16 PM Christian Mauderer <<a href="mailto:oss@c-mauderer.de" target="_blank">oss@c-mauderer.de</a> <br>
> <mailto:<a href="mailto:oss@c-mauderer.de" target="_blank">oss@c-mauderer.de</a>>> wrote:<br>
> <br>
> <br>
> <br>
> On 02/04/2021 08:36, Ahamed Husni wrote:<br>
> > > Yes, this seems like an area that can be chipped<br>
> away at, with a<br>
> > > strong plan of activities. My concern would be<br>
> whether it is about<br>
> > > writing code or not?<br>
> > ><br>
> > ><br>
> > > After completing the above milestones, if we have more<br>
> time I can start<br>
> > > to work on<br>
> > > the Mass storage support.<br>
> > ><br>
> ><br>
> ><br>
> > I would suggest to put _more_ into the proposal and make it<br>
> clear that<br>
> > the later points depend on whether there is enough time or not.<br>
> ><br>
> > @Gedare: The time and effort for that project is really hard to<br>
> > estimate<br>
> > in my point of view. Do you have an idea how we could handle<br>
> that?<br>
> ><br>
> ><br>
> > So do I have to include mass storage support into the project<br>
> schedule or<br>
> > should I prepare the schedule for Ethernet, Serial and add the<br>
> list of<br>
> > possible advances and say that I'll work on them if there is<br>
> enough time?<br>
> <br>
> I would suggest to include it. I'm quite sure that there is enough time.<br>
> <br>
> ><br>
> > Most likely we would have to put some further open points at<br>
> the end of<br>
> > that because like I said: Depending on how well it works you<br>
> might need<br>
> > anything between a day and three weeks to get CDC Ethernet<br>
> running.<br>
> > From<br>
> > my first guess, it's maybe a week.<br>
> ><br>
> > Note that I would expect that you will need a debugger and<br>
> the RTEMS<br>
> > event recording for this kind of project.<br>
> ><br>
> ><br>
> > CDC Serial should be only a small step as soon as CDC Ethernet is<br>
> > running.<br>
> ><br>
> ><br>
> > I don't have a JTAG debugger now. I'll get that set up asap.<br>
> ><br>
> ><br>
> > > USB OTG would be a nice area. But that will be less<br>
> writing a driver<br>
> > > for<br>
> > > Beagle but more finding out how that works with libbsd<br>
> and finding a<br>
> > > good way to configure it. I once put a few hours into<br>
> it didn't take<br>
> > > too<br>
> > > much time till a PC detected an USB device (see<br>
> > ><br>
> <a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>>><br>
> > ><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>>>>).<br>
> > > Basically it's about importing the "usb_template" stuff<br>
> and finding a<br>
> > > way to configure it in libbsd.<br>
> ><br>
> ><br>
> > I'm trying to build and test this branch. I had trouble with<br>
> building<br>
> > the libbsd.<br>
> <br>
> The branch is very old. Most likely it won't build with a current<br>
> toolchain and a current RTEMS. You might want to try to rebase the last<br>
> two patches onto an up to date libbsd.<br>
> <br>
> > So I started to build the tools and kernel from scratch with the RSB<br>
> > master, using<br>
> > beaglebone black bset. It gives me the following error.<br>
> > Error log: <a href="https://pastebin.com/NYZRej1B" rel="noreferrer" target="_blank">https://pastebin.com/NYZRej1B</a><br>
> <<a href="https://pastebin.com/NYZRej1B" rel="noreferrer" target="_blank">https://pastebin.com/NYZRej1B</a>> <<a href="https://pastebin.com/NYZRej1B" rel="noreferrer" target="_blank">https://pastebin.com/NYZRej1B</a><br>
> <<a href="https://pastebin.com/NYZRej1B" rel="noreferrer" target="_blank">https://pastebin.com/NYZRej1B</a>>><br>
> ><br>
> > Build command<br>
> ><br>
> > ../source-builder/sb-set-builder --log=beagle.txt<br>
> > --prefix=$BASE/rtems/6 bsps/beagleboneblack.bset<br>
> <br>
> For development I would suggest to build only the toolchain using RSB.<br>
> After that you should build the BSP and libbsd manually. You will have<br>
> to recompile the BSP and libbsd quite often and it's a lot more<br>
> convenient to do that without touching RSB every time.<br>
> <br>
> I would suggest to use some simple scripts or a Makefile for that.<br>
> Something like<br>
> <br>
> <a href="https://gitlab.com/c-mauderer/rtems-bbb/-/blob/master/Makefile" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-bbb/-/blob/master/Makefile</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-bbb/-/blob/master/Makefile" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-bbb/-/blob/master/Makefile</a>><br>
> <br>
> Note that the repo containing that Makefile is no official one and<br>
> it is<br>
> unstable. Most of the time I use it for testing stuff.<br>
> <br>
> ><br>
> > What would be the steps to configure the USB OTG driver from<br>
> libbsd to BBB.<br>
> > I would like to try it out. Please guide me on this.<br>
> <br>
> I think that's most of the problem of the GSoC ;-)<br>
> <br>
> Basically it's the following steps:<br>
> <br>
> - Importing the relevant parts (should be the usb_template stuff) from<br>
> FreeBSD into libbsd. That's basically what the first commit on the<br>
> branch does. Take a look at the CONTRIBUTING.md file in libbsd for<br>
> details about the import process:<br>
> <a href="https://git.rtems.org/rtems-libbsd/tree/CONTRIBUTING.md#n158" rel="noreferrer" target="_blank">https://git.rtems.org/rtems-libbsd/tree/CONTRIBUTING.md#n158</a><br>
> <<a href="https://git.rtems.org/rtems-libbsd/tree/CONTRIBUTING.md#n158" rel="noreferrer" target="_blank">https://git.rtems.org/rtems-libbsd/tree/CONTRIBUTING.md#n158</a>><br>
> <br>
> - Enable them for Beagle. That's the second commit on the branch.<br>
> <br>
> - Somehow configure the USB OTG stuff. Like I said: That's the tricky<br>
> part. It has something to do with the usb_temp_init functions. But I<br>
> didn't manage to get it working in an hour or so and stopped trying<br>
> after that. So finding out how to configure and set up the stuff<br>
> will be<br>
> part of your Project.<br>
> <br>
> Best regards<br>
> <br>
> Christian<br>
> <br>
> ><br>
> > Best regards,<br>
> ><br>
> > On Fri, Mar 26, 2021 at 8:17 PM Christian MAUDERER<br>
> > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>> wrote:<br>
> ><br>
> > Hello Ahamed,<br>
> ><br>
> > Am 26.03.21 um 15:31 schrieb Ahamed Husni:<br>
> > > USB OTG would be a nice area. But that will be less<br>
> writing a<br>
> > driver<br>
> > > for<br>
> > > Beagle but more finding out how that works with libbsd and<br>
> > finding a<br>
> > > good way to configure it. I once put a few hours into it<br>
> > didn't take<br>
> > > too<br>
> > > much time till a PC detected an USB device (see<br>
> > ><br>
> <a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>>><br>
> > ><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>>>>).<br>
> > > Basically it's about importing the "usb_template"<br>
> stuff and<br>
> > finding a<br>
> > > way to configure it in libbsd.<br>
> > ><br>
> > > I think that topic would have to be a bit of an open<br>
> one: You<br>
> > might<br>
> > > work<br>
> > > only a day on it and have a working CDC Ethernet<br>
> afterwards<br>
> > or you can<br>
> > > need weeks for that. So you should add an open list of<br>
> possible<br>
> > > advanced<br>
> > > targets. An OTG device can be:<br>
> > ><br>
> > > - Ethernet<br>
> > > - Serial port<br>
> > > - Mass storage<br>
> > > - Keyboard / Mouse<br>
> > > - Modem<br>
> > > - Audio<br>
> > > - ...<br>
> > ><br>
> > > The simplest one will most likely be Ethernet followed<br>
> by serial<br>
> > > port. I<br>
> > > would add some of the others (like mass storage) as an<br>
> > extended targets.<br>
> > ><br>
> > > Best regards<br>
> > ><br>
> > > Christian<br>
> > ><br>
> > ><br>
> > > USB OTG would allow more extended capabilities for the<br>
> beagle board.<br>
> > > To work on the USB OTG devices, what would be the best way?<br>
> > > What I understood from what Christian says is,<br>
> > ><br>
> > > 1. Finding out how USB OTG works with libbsd and finding a<br>
> > > way to configure it for the beagle.<br>
> > > 2. Work on CDC Ethernet<br>
> > > 3. CDC Ethernet - Example application & Documentation<br>
> > > 4. Work on Serial over USB<br>
> > > 5. Serial over USB - Example application & Documentation<br>
> > ><br>
> > > Am I right?<br>
> ><br>
> > Most likely we would have to put some further open points at<br>
> the end of<br>
> > that because like I said: Depending on how well it works you<br>
> might need<br>
> > anything between a day and three weeks to get CDC Ethernet<br>
> running.<br>
> > From<br>
> > my first guess, it's maybe a week.<br>
> ><br>
> > Note that I would expect that you will need a debugger and<br>
> the RTEMS<br>
> > event recording for this kind of project.<br>
> ><br>
> ><br>
> > CDC Serial should be only a small step as soon as CDC Ethernet is<br>
> > running.<br>
> ><br>
> > Mass storage depends on the current implementation for that<br>
> in FreeBSD.<br>
> > It might could be an interesting part.<br>
> ><br>
> > ><br>
> > > Would implementing Ethernet and Serial solve the problem<br>
> of using<br>
> > TTL<br>
> > > converters<br>
> > > when working on RTEMS in Beagle for the developers?<br>
> > ><br>
> ><br>
> > Depends on the application. For those who want to write an<br>
> application,<br>
> > a CDC Serial device would be a nice alternative. For those<br>
> who want to<br>
> > develop drivers or RTEMS itself: Very unlikely that CDC Serial is<br>
> > enough<br>
> > for that.<br>
> ><br>
> > > Yes, this seems like an area that can be chipped away<br>
> at, with a<br>
> > > strong plan of activities. My concern would be whether<br>
> it is<br>
> > about<br>
> > > writing code or not?<br>
> > ><br>
> > ><br>
> > > After completing the above milestones, if we have more<br>
> time I can<br>
> > start<br>
> > > to work on<br>
> > > the Mass storage support.<br>
> > ><br>
> ><br>
> > I would suggest to put _more_ into the proposal and make it<br>
> clear that<br>
> > the later points depend on whether there is enough time or not.<br>
> ><br>
> > @Gedare: The time and effort for that project is really hard to<br>
> > estimate<br>
> > in my point of view. Do you have an idea how we could handle<br>
> that?<br>
> ><br>
> ><br>
> > ><br>
> > > Hi,<br>
> > ><br>
> > > Regarding the PRU.<br>
> > > I was able to load code to the PRU.<br>
> > > However I wasn't able to map IRQ interrupts to the<br>
> PRU, thus<br>
> > unable<br>
> > > to communicate with it in a meaningful way.<br>
> > > Also I don't think that this project should be continued<br>
> > without a<br>
> > > full DEBUGGING Setup.<br>
> > ><br>
> > > Best,<br>
> > > Nils<br>
> > ><br>
> > ><br>
> > > +1, without a proper debugging setup I found it hard<br>
> to precisely<br>
> > > pin point the problem when I initially took up this task.<br>
> > ><br>
> > ><br>
> > > What is the full DEBUGGING setup needed to work on the PRU?<br>
> ><br>
> > I expect a JTAG-Debugger. I had good experience with the<br>
> Segger J-Link<br>
> > EDU for GSoC projects with BBB. Alternatively there are<br>
> OpenOCD based<br>
> > ones out there too that are said do work well. Note that you<br>
> have to<br>
> > solder a debug connector to the Beagle for that.<br>
> ><br>
> > Best regards<br>
> ><br>
> > Christian<br>
> ><br>
> > ><br>
> > > Regards,<br>
> > > Husni.<br>
> > ><br>
> > > On Tue, Mar 23, 2021 at 10:25 PM Utkarsh Rai<br>
> > <<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a> <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a>><br>
> <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a> <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a>>><br>
> > > <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a><br>
> <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a>><br>
> > <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a><br>
> <mailto:<a href="mailto:utkarsh.rai60@gmail.com" target="_blank">utkarsh.rai60@gmail.com</a>>>>> wrote:<br>
> > ><br>
> > ><br>
> > ><br>
> > ><br>
> > > On Tue, Mar 23, 2021 at 9:36 PM Nils Hölscher<br>
> > <<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a> <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a>><br>
> <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a> <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a>>><br>
> > > <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a> <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a>><br>
> <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a> <mailto:<a href="mailto:nilhoel1@gmail.com" target="_blank">nilhoel1@gmail.com</a>>>>> wrote:<br>
> > ><br>
> > > Hi,<br>
> > ><br>
> > > Regarding the PRU.<br>
> > > I was able to load code to the PRU.<br>
> > > However I wasn't able to map IRQ interrupts to the<br>
> PRU, thus<br>
> > > unable to communicate with it in a meaningful way<br>
> > ><br>
> > ><br>
> > ><br>
> > > Just a small addition, AFAIK the issue with this was<br>
> the fact<br>
> > that<br>
> > > mmap() would always fail.<br>
> > ><br>
> > > .<br>
> > > Also I don't think that this project should be<br>
> continued<br>
> > without<br>
> > > a full DEBUGGING Setup.<br>
> > ><br>
> > ><br>
> > > +1, without a proper debugging setup I found it hard<br>
> to precisely<br>
> > > pin point the problem when I initially took up this task.<br>
> > ><br>
> > ><br>
> > > Best,<br>
> > > Nils<br>
> > ><br>
> > > On Tue, 23 Mar 2021 at 17:00, Christian MAUDERER<br>
> > > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>> wrote:<br>
> > ><br>
> > > Hello Gedare,<br>
> > ><br>
> > > Am 23.03.21 um 16:48 schrieb Gedare Bloom:<br>
> > > > CC: Nils, Utkarsh<br>
> > > ><br>
> > > > On Tue, Mar 23, 2021 at 9:17 AM Christian<br>
> MAUDERER<br>
> > > > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>> wrote:<br>
> > > >><br>
> > > >> Hello Ahamed,<br>
> > > >><br>
> > > >> Am 23.03.21 um 11:24 schrieb Ahamed Husni:<br>
> > > >>> Hi everyone,<br>
> > > >>><br>
> > > >>> I'm really interested to work on the<br>
> *Beagle BSP<br>
> > > Projects* [#2891<br>
> > > >>> <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a><br>
> <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a>><br>
> > <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a><br>
> <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a>>><br>
> > > <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a><br>
> <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a>><br>
> > <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a><br>
> <<a href="https://devel.rtems.org/ticket/2891" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/2891</a>>>>>]. *<br>
> > > >>> *<br>
> > > >>> *Adding PRU Support* [#3730<br>
> > > <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a><br>
> <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a>><br>
> > <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a><br>
> <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a>>><br>
> > > <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a><br>
> <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a>><br>
> > <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a><br>
> <<a href="https://devel.rtems.org/ticket/3730" rel="noreferrer" target="_blank">https://devel.rtems.org/ticket/3730</a>>>>>]<br>
> > > >>> project seems really interesting to me.<br>
> > > >>> This project is partially done during<br>
> GSoC 2019<br>
> > > >>> <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a><br>
> <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a>><br>
> > <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a><br>
> <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a>>><br>
> > > <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a><br>
> <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a>><br>
> > <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a><br>
> <<a href="https://devel.rtems.org/wiki/GSoC/2019" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/GSoC/2019</a>>>>>by Nils Hölscher .<br>
> > > >>> Is this a good project for the GSoC?<br>
> > > >>><br>
> > > >>> Up to now I have,<br>
> > > >>><br>
> > > >>> 1. Completed the GSoC prerequisite task<br>
> > > >>> 2. Got the required hardware and tested it.<br>
> > > (Beagleboard Black, USB to<br>
> > > >>> TTL Converter)<br>
> > > >>> 3. Installed RTEMS on the Beagleboard<br>
> and tested.<br>
> > > (Screenshot attached<br>
> > > >>> below)<br>
> > > >>><br>
> > > >>><br>
> > > >>> I need guidance to define the scope of<br>
> the project.<br>
> > > >>> I'm currently thinking of ,<br>
> > > >>><br>
> > > >>> 1. First finish the remaining work from<br>
> GSoC<br>
> > 2019 on<br>
> > > the PRU.<br>
> > > >>> (What is the status of current<br>
> > implementation of<br>
> > > the PRU?)<br>
> > > >><br>
> > > >> I'm really not sure what the state of the<br>
> PRU is. I<br>
> > > didn't follow that<br>
> > > >> project closely. Maybe one of the mentors<br>
> of that<br>
> > > project can say<br>
> > > >> anything regarding that.<br>
> > > >><br>
> > > > Some more background:<br>
> > > ><br>
> > ><br>
> <a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a>><br>
> > <br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a>>><br>
> > ><br>
> > <br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a>><br>
> > <br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2019-December/056478.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2019-December/056478.html</a>>>><br>
> > > ><br>
> > ><br>
> <a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a>><br>
> > <br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a>>><br>
> > ><br>
> > <br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a>><br>
> > <br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a><br>
> <<a href="https://lists.rtems.org/pipermail/devel/2020-January/056958.html" rel="noreferrer" target="_blank">https://lists.rtems.org/pipermail/devel/2020-January/056958.html</a>>>><br>
> > > ><br>
> > > > Maybe Utkarsh or Nils have more to say.<br>
> > > ><br>
> > > >>> 2. Implement additional peripheral support.<br>
> > > >>> What would be most useful?<br>
> > > >>> (USB OTG, CAN, ...).<br>
> > > >><br>
> > > >> I think CAN is a bit hard without some CAN<br>
> analyzer<br>
> > > hardware as a peer.<br>
> > > >><br>
> > > >> USB OTG would be a nice area. But that<br>
> will be less<br>
> > > writing a driver for<br>
> > > >> Beagle but more finding out how that works<br>
> with<br>
> > libbsd<br>
> > > and finding a<br>
> > > >> good way to configure it. I once put a few<br>
> hours<br>
> > into it<br>
> > > didn't take too<br>
> > > >> much time till a PC detected an USB device<br>
> (see<br>
> > > >><br>
> > ><br>
> <a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>>><br>
> > ><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>><br>
> > <br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a><br>
> <<a href="https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce" rel="noreferrer" target="_blank">https://gitlab.com/c-mauderer/rtems-libbsd/-/tree/20170707-cdce</a>>>>).<br>
> > > >> Basically it's about importing the<br>
> "usb_template"<br>
> > stuff<br>
> > > and finding a<br>
> > > >> way to configure it in libbsd.<br>
> > > >><br>
> > > >> I think that topic would have to be a bit<br>
> of an open<br>
> > > one: You might work<br>
> > > >> only a day on it and have a working CDC<br>
> Ethernet<br>
> > > afterwards or you can<br>
> > > >> need weeks for that. So you should add an open<br>
> > list of<br>
> > > possible advanced<br>
> > > >> targets. An OTG device can be:<br>
> > > >><br>
> > > >> - Ethernet<br>
> > > >> - Serial port<br>
> > > >> - Mass storage<br>
> > > >> - Keyboard / Mouse<br>
> > > >> - Modem<br>
> > > >> - Audio<br>
> > > >> - ...<br>
> > > >><br>
> > > >> The simplest one will most likely be Ethernet<br>
> > followed<br>
> > > by serial port. I<br>
> > > >> would add some of the others (like mass<br>
> storage)<br>
> > as an<br>
> > > extended targets.<br>
> > > >><br>
> > > > Yes, this seems like an area that can be<br>
> chipped<br>
> > away at,<br>
> > > with a<br>
> > > > strong plan of activities. My concern would be<br>
> > whether it<br>
> > > is about<br>
> > > > writing code or not?<br>
> > > ><br>
> > ><br>
> > > It won't produce a lot of code. But it will<br>
> produce<br>
> > relevant<br>
> > > one:<br>
> > ><br>
> > > 1. Interface for configuration (if necessary)<br>
> > ><br>
> > > 2. Example application<br>
> > ><br>
> > > 3. Documentation<br>
> > ><br>
> > > For Ethernet and serial port that's most<br>
> likely it.<br>
> > For Mass<br>
> > > storage<br>
> > > there might be some more code. Without a too<br>
> detailed<br>
> > look:<br>
> > > I would<br>
> > > expect that the mass storage either implements<br>
> some<br>
> > access<br>
> > > to a raw<br>
> > > block device - in which case it would be<br>
> necessary to add<br>
> > > the access to<br>
> > > block devices. Or it implements something like the<br>
> > PTP stuff<br>
> > > used on<br>
> > > smartphones in which case there will be most<br>
> likely some<br>
> > > code that<br>
> > > accesses the file system using POSIX functions<br>
> instead of<br>
> > > FreeBSD kernel<br>
> > > functions.<br>
> > ><br>
> > > Best regards<br>
> > ><br>
> > > Christian<br>
> > ><br>
> > > >> Best regards<br>
> > > >><br>
> > > >> Christian<br>
> > > >><br>
> > > >>><br>
> > > >>> The builtin USB is NOT functional other<br>
> > than for<br>
> > > power under RTEMS.<br>
> > > >>> (USB OTG would have to be implemented in<br>
> > RTEMS to<br>
> > > get rid of USB to<br>
> > > >>> TTL Converter.)<br>
> > > >>> - Ben Gras<br>
> > > >>><br>
> > ><br>
> > <br>
> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a>> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a>>><br>
> > ><br>
> > <br>
> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a>> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a> <<a href="http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html" rel="noreferrer" target="_blank">http://www.shrike-systems.com/beagleboard-xm-beaglebone-black-and-everything-else-rtems-on-the-beagles.html</a>>>>><br>
> > > >>> (Blog post)<br>
> > > >>><br>
> > > >>><br>
> > > >>> Thanks,<br>
> > > >>> Husni Faiz.<br>
> > > >>><br>
> > > >>><br>
> > > >>> BBB_Serial_Out.png<br>
> > > >>><br>
> > > >>><br>
> > > >>><br>
> _______________________________________________<br>
> > > >>> devel mailing list<br>
> > > >>> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>>><br>
> > <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>>>><br>
> > > >>><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>>><br>
> > > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>>>><br>
> > > >>><br>
> > > >><br>
> > > >> --<br>
> > > >> --------------------------------------------<br>
> > > >> embedded brains GmbH<br>
> > > >> Herr Christian MAUDERER<br>
> > > >> Dornierstr. 4<br>
> > > >> 82178 Puchheim<br>
> > > >> Germany<br>
> > > >> email:<br>
> <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > >> phone: +49-89-18 94 741 - 18<br>
> > > >> fax: +49-89-18 94 741 - 08<br>
> > > >><br>
> > > >> Registergericht: Amtsgericht München<br>
> > > >> Registernummer: HRB 157899<br>
> > > >> Vertretungsberechtigte Geschäftsführer: Peter<br>
> > Rasmussen,<br>
> > > Thomas Dörfler<br>
> > > >> Unsere Datenschutzerklärung finden Sie hier:<br>
> > > >><br>
> <a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>><br>
> > <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>>><br>
> > > <br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>><br>
> > <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>>>><br>
> > > >><br>
> _______________________________________________<br>
> > > >> devel mailing list<br>
> > > >> <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>>><br>
> > <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>>>><br>
> > > >><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>>><br>
> > > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> > <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>>>><br>
> > ><br>
> > > --<br>
> > > --------------------------------------------<br>
> > > embedded brains GmbH<br>
> > > Herr Christian MAUDERER<br>
> > > Dornierstr. 4<br>
> > > 82178 Puchheim<br>
> > > Germany<br>
> > > email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > phone: +49-89-18 94 741 - 18<br>
> > > fax: +49-89-18 94 741 - 08<br>
> > ><br>
> > > Registergericht: Amtsgericht München<br>
> > > Registernummer: HRB 157899<br>
> > > Vertretungsberechtigte Geschäftsführer: Peter<br>
> Rasmussen,<br>
> > > Thomas Dörfler<br>
> > > Unsere Datenschutzerklärung finden Sie hier:<br>
> > > <a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>><br>
> > <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>>><br>
> > > <br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>><br>
> > <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>>>><br>
> > ><br>
> ><br>
> > --<br>
> > --------------------------------------------<br>
> > embedded brains GmbH<br>
> > Herr Christian MAUDERER<br>
> > Dornierstr. 4<br>
> > 82178 Puchheim<br>
> > Germany<br>
> > email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > phone: +49-89-18 94 741 - 18<br>
> > fax: +49-89-18 94 741 - 08<br>
> ><br>
> > Registergericht: Amtsgericht München<br>
> > Registernummer: HRB 157899<br>
> > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen,<br>
> Thomas Dörfler<br>
> > Unsere Datenschutzerklärung finden Sie hier:<br>
> > <a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>><br>
> > <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
> <<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a>>><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Husni<br>
> ><br>
> > _______________________________________________<br>
> > devel mailing list<br>
> > <a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a> <mailto:<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a>><br>
> > <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
> <<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a>><br>
> ><br>
> <br>
</blockquote></div></div></div>