Re: [PATCH 1/2] Add FDT support for Beaglebone Black.

Ok, got it. Best Regards Sichen Zhao From: devel on behalf of Sebastian Huber Sent: Wednesday, July 5, 2017 13:12 To: Sichen Zhao; devel@rtems.org Cc: punitv...@gmail.com;

Re: [PATCH 1/8] Add support for multiple memory resources.

Ok, i will remove patch 5/8 and 6/8. Is that ok? Best Regards Sichen Zhao From: devel on behalf of Sebastian Huber Sent: Wednesday, July 5, 2017 13:17 To: Sichen Zhao; devel@rtems.org Cc:

Re: [PATCH 1/8] Add support for multiple memory resources.

Hello Sichen, could you please create a minimal patch set that works with the FDT enabled BSP. -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de

Re: [PATCH 1/2] Add FDT support for Beaglebone Black.

Hello Sichen, congratulations to add FDT support to the first ARM BSP. On 05/07/17 04:52, Sichen Zhao wrote: --- c/src/lib/libbsp/arm/beagle/Makefile.am| 1 + c/src/lib/libbsp/arm/beagle/configure.ac | 9 + c/src/lib/libbsp/arm/beagle/include/bsp.h | 6 +-

[PATCH 7/8] Add FDT support for am335x USB driver.

Now RTEMS can detect and mount USB device. --- rtemsbsd/include/bsp/nexus-devices.h | 13 + 1 file changed, 13 insertions(+) diff --git a/rtemsbsd/include/bsp/nexus-devices.h b/rtemsbsd/include/bsp/nexus-devices.h index 1fbf756..2d5694e 100644 ---

[PATCH 8/8] Add umass support for Beaglebone black.

Now RTEMS can mount and open USB disk. --- rtemsbsd/include/bsp/nexus-devices.h | 1 + 1 file changed, 1 insertion(+) diff --git a/rtemsbsd/include/bsp/nexus-devices.h b/rtemsbsd/include/bsp/nexus-devices.h index 2d5694e..09a4cc3 100644 --- a/rtemsbsd/include/bsp/nexus-devices.h +++

[PATCH 6/8] Remove nexus support for am335x USB driver.

--- freebsd/sys/arm/ti/am335x/am335x_musb.c| 14 freebsd/sys/arm/ti/am335x/am335x_prcm.c| 10 --- freebsd/sys/arm/ti/am335x/am335x_usbss.c | 19 - freebsd/sys/arm/ti/ti_scm.c| 7 -- rtemsbsd/include/bsp/nexus-devices.h | 12 ---

[PATCH 5/8] Add nexus support for am335x USB driver.

--- freebsd/sys/arm/ti/am335x/am335x_musb.c| 14 freebsd/sys/arm/ti/am335x/am335x_prcm.c| 10 +++ freebsd/sys/arm/ti/am335x/am335x_usbss.c | 19 + freebsd/sys/arm/ti/ti_scm.c| 7 ++ rtemsbsd/include/bsp/nexus-devices.h | 12 +++

[PATCH 4/8] Port am335x usb driver to RTEMS.

--- freebsd/sys/arm/ti/am335x/am335x_prcm.c | 8 freebsd/sys/arm/ti/ti_cpuid.h | 19 +++ freebsd/sys/arm/ti/ti_prcm.c| 2 ++ freebsd/sys/arm/ti/ti_scm.c | 2 ++ libbsd.py | 30

[PATCH 2/8] Modify the support for multiple memory resources.

rtems-libbsd only support single resource for a device. But some usb control need two resources, such as musb. So modify support for multiple device resources allocation. --- rtemsbsd/rtems/rtems-kernel-nexus.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/8] Add support for multiple memory resources.

From: Hans Petter Selasky --- rtemsbsd/rtems/rtems-kernel-nexus.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/rtemsbsd/rtems/rtems-kernel-nexus.c b/rtemsbsd/rtems/rtems-kernel-nexus.c index 008e4b2..1a5a9ef 100644 ---

[PATCH 1/2] Add FDT support for Beaglebone Black.

--- c/src/lib/libbsp/arm/beagle/Makefile.am| 1 + c/src/lib/libbsp/arm/beagle/configure.ac | 9 + c/src/lib/libbsp/arm/beagle/include/bsp.h | 6 +- c/src/lib/libbsp/arm/beagle/startup/bspstart.c | 5 + c/src/lib/libbsp/arm/shared/start/start.S | 5 + 5

[PATCH 2/2] Modify sdcard.sh to support FDT for Beaglebone black.

--- c/src/lib/libbsp/arm/beagle/simscripts/bboneblk.dtb | Bin 0 -> 34458 bytes c/src/lib/libbsp/arm/beagle/simscripts/sdcard.sh| 6 -- 2 files changed, 4 insertions(+), 2 deletions(-) create mode 100644 c/src/lib/libbsp/arm/beagle/simscripts/bboneblk.dtb diff --git

RTEMS 4.11.2-rc5 Release

Hello, RTEMS 4.11.2-rc5 is available for testing. If you are using RTEMS 4.11.1 we encourage you to test and report any issues before the release date of 7th July 2017. I have built all architectures in the '4.11/rtems-all' build set on Windows taking just over 1 day to complete. The release is

Re: RISC-V interrupt vectoring

Hi Denis, It's not clear from your output which instruction is causing the fault. You can debug this by investigating mcause value after the faulting instruction, and see what's the value in s0, and whether it's valid or not. It's also a good idea to use objdump and/or Spike/Qemu for debugging

Re: RISC-V interrupt vectoring

2017-07-03 21:17 GMT+02:00 Joel Sherrill : > > > On Jul 3, 2017 12:45 PM, "Denis Obrezkov" wrote: > > 2017-07-03 19:09 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 3, 2017 11:49 AM, "Denis Obrezkov" >> wrote: >> >>

Re: RISC-V interrupt vectoring

2017-07-03 21:17 GMT+02:00 Joel Sherrill : > > > On Jul 3, 2017 12:45 PM, "Denis Obrezkov" wrote: > > 2017-07-03 19:09 GMT+02:00 Joel Sherrill : > >> >> >> On Jul 3, 2017 11:49 AM, "Denis Obrezkov" >> wrote: >> >>