date:20210516

Re: [PATCH] riscv/console: console-config.c update

2021-05-16 Thread ND

This patch will help use Microchip PolarFire SoC icicle kit with RTEMS
mainline...any plan on when this will be available?

On Tue, May 11, 2021 at 11:35 AM somesh deshmukh 
wrote:

> Gentle Reminder.
>
> Hi All,
> Can you please review this patch and let me know if there are any
> suggestions/comments.
>
> Regards,
> Somesh
>
> -- Forwarded message -
> From: Somesh Deshmukh 
> Date: Wed, May 5, 2021 at 11:26 PM
> Subject: [PATCH] riscv/console: console-config.c update
> To: 
> Cc: Somesh Deshmukh 
>
>
> - Parsing the sub-node should be available generic not specific to Freedom
>   Arty310 board. If we remove the Freedom Arty macro now, it will lose
>   backward compatibility.The proposed change will retain the backward
>   compatibility and also adds the necessary fix for parsing sub-node.
> ---
>  bsps/riscv/riscv/console/console-config.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bsps/riscv/riscv/console/console-config.c
> b/bsps/riscv/riscv/console/console-config.c
> index d962a5a418..797506a31b 100644
> --- a/bsps/riscv/riscv/console/console-config.c
> +++ b/bsps/riscv/riscv/console/console-config.c
> @@ -91,7 +91,7 @@ static int riscv_get_console_node(const void *fdt)
>  stdout_path = "";
>}
>
> -#if RISCV_ENABLE_FRDME310ARTY_SUPPORT != 0
> +#if ((RISCV_ENABLE_FRDME310ARTY_SUPPORT != 0) ||
> (RISCV_CONSOLE_MAX_NS16550_DEVICES > 0))
>int root;
>int soc;
>root = fdt_path_offset(fdt, "/");
> --
> 2.25.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: while running rtems-test with coverage

2021-05-16 Thread Joel Sherrill

On Sun, May 16, 2021, 11:20 AM Vijay Kumar Banerjee  wrote:

> (Resending for the list)
>
> On Sun, May 16, 2021 at 10:18 AM Vijay Kumar Banerjee
>  wrote:
> >
> > Hi Mohammadreza,
> >
> > Sorry for the delay in replying :)
> >
> >
> > On Tue, May 11, 2021 at 11:39 AM mohammadreza tahzibi
> >  wrote:
> > >
> > > Dear Sir
> > > Hi,
> > >
> > > I am new in rtems and I am trying to run rtems-test ith enabling
> coverage.
> > >
> > Great.
> >
> > > But after many attempts I encountered the same problem and I am not
> able to handle this issue.
> > >
> > > I would be glad if you could resolve this issue.
> >
> > please try --rtems-bsp=xilinx_zynq_a9_qemu-cov
> >
> > As a convention, there are two versions of the config for the targets
> > that support coverage. The one with "-cov" suffix has the right
> > configuration to use with `--coverage` option.
> >
> >
> > Hope this helps.
> >
> > Best regards,
> > Vijay
> >
> >
> > > The error messages are attached below (atttachment).
> > >
> > > =
> > > root@xen:/home/work/sandbox2# rtems/5/bin/rtems-test
> --rtems-tools=/home/work/sandbox2/rtems/5/  --log=coverage-analysis.log
> --rtems-bsp=xilinx_zynq_a9_qemu --target=arm-rtems5   --coverage
> rtems-libbsd/build/arm-rtems5-xilinx_zynq_a9_qemu-default/selectpollkqueue01.exe
> > > RTEMS Testing - Tester, 5 (d697769d4682 modified)
> > > Traceback (most recent call last):
> > >   File "rtems/5/share/rtems/tester/rt/cmd-test.py", line 42, in
> 
> > > test.run(sys.argv[1:], command_path = base)
> > >   File "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/test.py",
> line 446, in run
> > > trace = cov_trace)
> > >   File
> "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/coverage.py", line 385,
> in __init__
> > > self.target = self.macros['target']
> > >   File
> "/home/work/sandbox2/rtems/5/share/rtems/rtemstoolkit/macros.py", line 195,
> in __getitem__
> > > raise IndexError('key: %s' % (key))
> > > IndexError: key: target
> > >
> > >
> > > =
>

Coverage was broken until a lot of recent work by Alex. You have to have
qemu-couverture and must be on the master.

There hasn't been any talk of back porting all this.  It would likely be a
heavy copy and paste from 6 to 5 and a lot of testing.


> >
> > >
> > > Thank you for your assistance.
> > > Regards
> > >
> > >
> > >
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: while running rtems-test with coverage

2021-05-16 Thread Vijay Kumar Banerjee

(Resending for the list)

On Sun, May 16, 2021 at 10:18 AM Vijay Kumar Banerjee
 wrote:
>
> Hi Mohammadreza,
>
> Sorry for the delay in replying :)
>
>
> On Tue, May 11, 2021 at 11:39 AM mohammadreza tahzibi
>  wrote:
> >
> > Dear Sir
> > Hi,
> >
> > I am new in rtems and I am trying to run rtems-test ith enabling coverage.
> >
> Great.
>
> > But after many attempts I encountered the same problem and I am not able to 
> > handle this issue.
> >
> > I would be glad if you could resolve this issue.
>
> please try --rtems-bsp=xilinx_zynq_a9_qemu-cov
>
> As a convention, there are two versions of the config for the targets
> that support coverage. The one with "-cov" suffix has the right
> configuration to use with `--coverage` option.
>
>
> Hope this helps.
>
> Best regards,
> Vijay
>
>
> > The error messages are attached below (atttachment).
> >
> > =
> > root@xen:/home/work/sandbox2# rtems/5/bin/rtems-test 
> > --rtems-tools=/home/work/sandbox2/rtems/5/  --log=coverage-analysis.log  
> > --rtems-bsp=xilinx_zynq_a9_qemu --target=arm-rtems5   --coverage  
> > rtems-libbsd/build/arm-rtems5-xilinx_zynq_a9_qemu-default/selectpollkqueue01.exe
> > RTEMS Testing - Tester, 5 (d697769d4682 modified)
> > Traceback (most recent call last):
> >   File "rtems/5/share/rtems/tester/rt/cmd-test.py", line 42, in 
> > test.run(sys.argv[1:], command_path = base)
> >   File "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/test.py", line 
> > 446, in run
> > trace = cov_trace)
> >   File "/home/work/sandbox2/rtems/5/share/rtems/tester/rt/coverage.py", 
> > line 385, in __init__
> > self.target = self.macros['target']
> >   File "/home/work/sandbox2/rtems/5/share/rtems/rtemstoolkit/macros.py", 
> > line 195, in __getitem__
> > raise IndexError('key: %s' % (key))
> > IndexError: key: target
> >
> >
> > =
> >
> >
> > Thank you for your assistance.
> > Regards
> >
> >
> >
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v2] user/bld/index.rst: removed references to legacy network config options

2021-05-16 Thread Vijay Kumar Banerjee

Hi Harrison,

I pushed this patch.

https://git.rtems.org/rtems-docs/commit/?id=1f538688a7f743158e0e9e9bb673abd576307a0c

Thanks,
Vijay

On Tue, May 11, 2021 at 7:28 PM Vijay Kumar Banerjee  wrote:
>
> Hi Harrison,
>
> This patch looks good. If no one objects by Friday, I'll push this. Thanks.
>
> Best regards,
> Vijay
>
> On Tue, May 11, 2021 at 7:16 PM Harrison Edward Gerber
>  wrote:
> >
> > ---
> >  user/bld/index.rst | 7 ---
> >  1 file changed, 7 deletions(-)
> >
> > diff --git a/user/bld/index.rst b/user/bld/index.rst
> > index ebedf5a..411b3a2 100644
> > --- a/user/bld/index.rst
> > +++ b/user/bld/index.rst
> > @@ -309,10 +309,6 @@ in the configuration file.
> >  Set ``RTEMS_MULTIPROCESSING`` to ``True`` or ``False`` in the BSP
> >  section of the configuration file.
> >
> > -``--enable-networking`` | ``--disable-networking``
> > -Set ``RTEMS_NETWORKING`` to ``True`` or ``False`` in the BSP 
> > section of
> > -the configuration file.
> > -
> >  ``--enable-paravirt`` | ``--disable-paravirt``
> >  Set ``RTEMS_PARAVIRT`` to ``True`` or ``False`` in the BSP section 
> > of
> >  the configuration file.
> > @@ -354,9 +350,6 @@ Please have a look at the following example 
> > configuration file.
> >  # --enable-multiprocessing
> >  RTEMS_MULTIPROCESSING = False
> >
> > -# --enable-networking
> > -RTEMS_NETWORKING = True
> > -
> >  # --disable-paravirt
> >  RTEMS_PARAVIRT = False
> >
> > --
> > 2.25.1
> >
> > ___
> > devel mailing list
> > devel@rtems.org
> > http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [GSoC 2021] Beagle BSP USB OTG Support

2021-05-16 Thread Ahamed Husni

Hi,

I tried the CDC Ethernet in FreeBSD. My Laptop detects an ethernet
 interface with an IPv6.
I tried to ping the IPv6, but it didn't work
. The serial and ethernet works. I'll
check the mass
storage.

--Husni


On Thu, May 13, 2021 at 9:40 AM Ahamed Husni 
wrote:

> Hi,
>
> I couldn't set up the JTAG using Launchpad as it requires some adapters.
> While discussing
> 
> in the Element14 forum, it seems it would require a lot of
> work to set up JTAG using the Launchpad.
> I can get the standard JTAG hardwares required  by ordering online before
> the coding period begins.
>
> Until that I did the hardware mod 
> required for Libdebugger on the BBB
> 
> .
> I don't know how to use the libdebugger. If anyone could point me in the
> right direction, that would be great.
>
> I tried booting the FreeBSD on BBB. The serial over usb is working.
> Ethernet and mass storage might require some configuration in FreeBSD.
>
> Best regards,
> Husni Faiz.
>
> On Mon, May 10, 2021 at 12:04 PM Christian MAUDERER <
> christian.maude...@embedded-brains.de> wrote:
>
>> Hello Ahamed,
>>
>> I'm using a J-Link to debug Beagle. I think that it doesn't have a EMU
>> pin either. Only difference: It has an additional TRST. I would suggest
>> to just try it.
>>
>> I think on OpenOCD there are a few options regarding RST. You can have
>> SRST only, TRST only, both connected together and both as separate pins.
>>
>> Best regards
>>
>> Christian
>>
>> Am 10.05.21 um 06:09 schrieb Ahamed Husni:
>> > Hi all,
>> >
>> > I need to debug the Beaglebone Black using JTAG. I got a TI LaunchPad
>> > CC1310. Launchpad has a XDS110 debugger with a (ARM - not sure) 10 pin
>> > JTAG out which can be used to debug external targets. The Beaglebone
>> has
>> > a cTI 20 pin JTAG interface. Pin layouts for the ARM10 and cTI20 is
>> > given here.
>> >
>> >
>> http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information
>> > <
>> http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_jtag_connectors.html#connector-information
>> >
>> >
>> > Can we map the pins, point to point without adapters to debug the BBB
>> > using Launchpads's XDS110?
>> >
>> > Following is what I came up with just refering the above given pin
>> layouts.
>> >
>> > *ARM10 to cTI20*
>> >
>> > 1==5 (VTRef/VCC)
>> > 2==1 (SWDIO/TMS)
>> > 3==8(GND)
>> > 4==9  (SWCLK/TCLK) SWDCLK(9) and TCK(11) are separate in cTI
>> > 5==10  (GND)
>> > 6==7(SWO/TDO)
>> > 7 KEYED
>> > 8==3 (NC/TDI)
>> > 9==12   (GNDDetect)
>> > 10==15  (nRESET)
>> >
>> > Will this work? (EMU pins are not used here)
>> >
>> > Also I found a discussion in TI' forum which says,
>> >
>> > "Controlling the EMU0 and EMU1 signals, which are mandatory to place
>> the
>> > AM335x in debug mode."
>> >
>> >
>> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly
>> > <
>> https://e2e.ti.com/support/processors-group/processors/f/processors-forum/777331/am3358-how-to-evaluate-if-a-jtag-chain-works-correctly
>> >
>> >
>> > Also the hardware Mod for libdebugger in RTEMS connects the SWO/TDO(7)
>> > to the EMU0(13).
>> >
>> >
>> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger
>> > <
>> https://docs.rtems.org/branches/master/user/bsps/bsps-arm.html#debugging-using-libdebugger
>> >
>> >
>> > My Project Proposal:
>> >
>> https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
>> > <
>> https://docs.google.com/document/d/1CN3ri7g6NJeFPb5h8y4smr1aziGWyXbiiXUsFMhdUu4/edit?usp=sharing
>> >
>> >
>> > Best regards,
>> > Husni Faiz.
>> >
>>
>> --
>> 
>> embedded brains GmbH
>> Herr Christian MAUDERER
>> Dornierstr. 4
>> 82178 Puchheim
>> Germany
>> email: christian.maude...@embedded-brains.de
>> phone: +49-89-18 94 741 - 18
>> fax:   +49-89-18 94 741 - 08
>>
>> Registergericht: Amtsgericht München
>> Registernummer: HRB 157899
>> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
>> Unsere Datenschutzerklärung finden Sie hier:
>> https://embedded-brains.de/datenschutzerklaerung/
>>
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] riscv/console: console-config.c update

Re: while running rtems-test with coverage

Re: while running rtems-test with coverage

Re: [PATCH v2] user/bld/index.rst: removed references to legacy network config options

Re: [GSoC 2021] Beagle BSP USB OTG Support

5 matches

Site Navigation

Mail list logo

Footer information