Re: Requirement Document generator tool

On 28/1/20 10:48 am, Joel Sherrill wrote: > On Mon, Jan 27, 2020 at 4:18 PM Chris Johns > wrote: > > On 24/1/20 9:57 pm, Jose Valdez wrote: > > In fact these tools target the pre-qualified project. > > Do you see this as different to the RTEMS project? > >

Re: Requirement Document generator tool

On Mon, Jan 27, 2020 at 4:18 PM Chris Johns wrote: > On 24/1/20 9:57 pm, Jose Valdez wrote: > > In fact these tools target the pre-qualified project. > > Do you see this as different to the RTEMS project? > > > Since it was Sebastian who suggested to create this set of python tools, > > I think

Re: Requirement Document generator tool

On 24/1/20 9:57 pm, Jose Valdez wrote: > In fact these tools target the pre-qualified project. Do you see this as different to the RTEMS project? > Since it was Sebastian who suggested to create this set of python tools, I think Sebastian is wanting a smooth path for these tools into the

Re: [PATCH 1/2] rtemstoolkit/path: Add support to copy single file

Both have been pushed. Thank you. Chris On 24/1/20 8:57 pm, Vijay Kumar Banerjee wrote: > --- > rtemstoolkit/path.py | 8 ++-- > 1 file changed, 6 insertions(+), 2 deletions(-) > > diff --git a/rtemstoolkit/path.py b/rtemstoolkit/path.py > index 9401e99..b15164b 100644 > ---

Porting RTEMS to NXP i.MX RT1020

I'm evaluating porting RTEMS to the NXP i.MX RT1020. What will take me the longest is if the ethernet peripheral isn't supported. It's referred to as the "10/100-Mbps Ethernet MAC (ENET)" and the "MAC-NET" core. The "MAC-NET" core appears to be ethernet IP going back a while. Is this

"atsamv" BSP legacy network driver status

The "rtems-libbsd" "if_atsam.c" driver is derived from the legacy one. What's the status of the two drivers? I ask because I'm trying to do some small memory testing with the legacy stack on the . It is building but not working, I don't think network packets are going out even though the

JTAG for beaglebone black

I have been waiting for a 'flyswatter' JTAG to debug PRU apps, but the JTAG seems to be taking forever to arrive. Is there a work-around for JTAG based debugging? Has anybody used a different 'flavor' of JTAG for debugging BBB apps? Regards, Utkarsh