Bacport of ARM cache, RTL and TMS570 to RTEMS 4.11 Was: Simple question about RTL
Hello all, I have pushed massive update to RTEMS-4.11 ARM BSPs support. The cache manager and RTL update has been prepared in response to RTL failures reported by Tim Tian on Zynq BSP more than month ago. I have proposed 4.11 update series at September 9. https://github.com/ppisa/rtems/tree/4.11-arm-update Code has been tested by Alan Cudmore and more RPi versions and correction of Zynq problem has been reported as well. Because there has not been reported any problem on master nor on my 4.11-arm-update branch I have pushed changes to official 4.11 tree. Please, check on more BSPs and applications if all works correctly. I have pushed TMS570 backport from master to 4.11 as well, there has been critical problem corrected on master #2794 ARM TMS570 BSP: Serial port hangs when baudrate change initiates before all characters are sent and the rest of updates is required to boot RTEMS on TMS570LS3137 without separate loader or mixing code with other sources. I expect to do some more testing of 4.11 on TMS570 HW next week. >From my side, I think that RTEMS 4.11 branch is in the state where release can report Raspberry Pi 1, 2 and TMS570 as supported now. Best wishes, Pavel On Tuesday 06 of September 2016 09:28:42 Pavel Pisa wrote: > Hello Chris, > > On Tuesday 06 of September 2016 07:12:53 Chris Johns wrote: > > Hi Tim and Pavel, > > > > Thank you for the patches and testing. I will have a chat to Joel > > tomorrow about the patches and what we will do. If Joel agrees I may > > test and push the patches. > > > > FYI I am currently looking at #2767 which is reported against 4.11 and a > > zynq so there is real interest on these patches ending up on 4.11. > > > > Chris > > I have made 4.11 to boot on Raspberry Pi. > > The final patch > > arm/raspberrypi: minimized mainline patch move MMU in front of > application image and correct RPi2 boot on 4.11 branch. > https://github.com/ppisa/rtems/commit/984047e8295bb82b12700edb3aac911bd8427 >8af > > of branch > > https://github.com/ppisa/rtems/tree/4.11-arm-update > > series. > > Tickets > > https://devel.rtems.org/ticket/2783 > > https://devel.rtems.org/ticket/2782 > > At least one of these tickets can be assigned to all patches > in this backports branch. > > I have to move to other tasks today to have students exams prepared > and to have resources to pay our company bills. > > I understand that modifications are huge for 4.11 > > If there is interrest I can resend series to mainlinglist > when I return from our potential customers meeting. > > Best wishes, > > Pavel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
[PATCH] cpukit/m68k: Remove leftover bits of gen68302 BSP
closes #2543. --- cpukit/score/cpu/m68k/Makefile.am | 3 +- cpukit/score/cpu/m68k/preinstall.am | 4 - cpukit/score/cpu/m68k/rtems/m68k/m68302.h | 659 -- doc/relnotes/status.texi | 1 - 4 files changed, 1 insertion(+), 666 deletions(-) delete mode 100644 cpukit/score/cpu/m68k/rtems/m68k/m68302.h diff --git a/cpukit/score/cpu/m68k/Makefile.am b/cpukit/score/cpu/m68k/Makefile.am index 360dca7..7d5e856 100644 --- a/cpukit/score/cpu/m68k/Makefile.am +++ b/cpukit/score/cpu/m68k/Makefile.am @@ -7,8 +7,7 @@ include_rtemsdir = $(includedir)/rtems include_rtems_HEADERS = rtems/asm.h include_rtems_m68kdir = $(includedir)/rtems/m68k -include_rtems_m68k_HEADERS = rtems/m68k/m68302.h -include_rtems_m68k_HEADERS += rtems/m68k/m68360.h +include_rtems_m68k_HEADERS = rtems/m68k/m68360.h include_rtems_m68k_HEADERS += rtems/m68k/qsm.h include_rtems_m68k_HEADERS += rtems/m68k/sim.h diff --git a/cpukit/score/cpu/m68k/preinstall.am b/cpukit/score/cpu/m68k/preinstall.am index 29954b5..e2fa0c3 100644 --- a/cpukit/score/cpu/m68k/preinstall.am +++ b/cpukit/score/cpu/m68k/preinstall.am @@ -27,10 +27,6 @@ $(PROJECT_INCLUDE)/rtems/m68k/$(dirstamp): @: > $(PROJECT_INCLUDE)/rtems/m68k/$(dirstamp) PREINSTALL_DIRS += $(PROJECT_INCLUDE)/rtems/m68k/$(dirstamp) -$(PROJECT_INCLUDE)/rtems/m68k/m68302.h: rtems/m68k/m68302.h $(PROJECT_INCLUDE)/rtems/m68k/$(dirstamp) - $(INSTALL_DATA) $< $(PROJECT_INCLUDE)/rtems/m68k/m68302.h -PREINSTALL_FILES += $(PROJECT_INCLUDE)/rtems/m68k/m68302.h - $(PROJECT_INCLUDE)/rtems/m68k/m68360.h: rtems/m68k/m68360.h $(PROJECT_INCLUDE)/rtems/m68k/$(dirstamp) $(INSTALL_DATA) $< $(PROJECT_INCLUDE)/rtems/m68k/m68360.h PREINSTALL_FILES += $(PROJECT_INCLUDE)/rtems/m68k/m68360.h diff --git a/cpukit/score/cpu/m68k/rtems/m68k/m68302.h b/cpukit/score/cpu/m68k/rtems/m68k/m68302.h deleted file mode 100644 index acf55f5..000 --- a/cpukit/score/cpu/m68k/rtems/m68k/m68302.h +++ /dev/null @@ -1,659 +0,0 @@ -/** - * @file - * - * @brief Definitions for Motorola MC68302 Processor - * - * Section references in this file refer to revision 2 of Motorola's - * "MC68302 Integrated Multiprotocol Processor User's Manual". - * (Motorola document MC68302UM/AD REV 2.) - * - * Based on Don Meyer's cpu68302.h that was posted in comp.sys.m68k - * on 17 February, 1993. - */ - -/* - * COPYRIGHT 1995 David W. Glessner. - * - * Redistribution and use in source and binary forms are permitted - * provided that the following conditions are met: - * 1. Redistribution of source code and documentation must retain - *the above copyright notice, this list of conditions and the - *following disclaimer. - * 2. The name of the author may not be used to endorse or promote - *products derived from this software without specific prior - *written permission. - * - * This software is provided "AS IS" without warranty of any kind, - * either expressed or implied, including, but not limited to, the - * implied warranties of merchantability, title and fitness for a - * particular purpose. - * - *-- - */ - -#ifndef _RTEMS_M68K_M68302_H -#define _RTEMS_M68K_M68302_H - -/* - * BAR - Base Address Register - * Section 2.7 - */ -#define M302_BAR (*((volatile uint16_t *) 0xf2)) - -/* - * SCR - System Control Register - * Section 3.8.1 - */ -#define M302_SCR (*((volatile uint32_t *) 0xf4)) -/* - * SCR bits - */ -#define RBIT_SCR_IPA 0x0800 -#define RBIT_SCR_HWT 0x0400 -#define RBIT_SCR_WPV 0x0200 -#define RBIT_SCR_ADC 0x0100 - -#define RBIT_SCR_ERRE 0x0040 -#define RBIT_SCR_VGE 0x0020 -#define RBIT_SCR_WPVE 0x0010 -#define RBIT_SCR_RMCST 0x0008 -#define RBIT_SCR_EMWS 0x0004 -#define RBIT_SCR_ADCE 0x0002 -#define RBIT_SCR_BCLM 0x0001 - -#define RBIT_SCR_FRZW 0x8000 -#define RBIT_SCR_FRZ2 0x4000 -#define RBIT_SCR_FRZ1 0x2000 -#define RBIT_SCR_SAM 0x1000 -#define RBIT_SCR_HWDEN 0x0800 -#define RBIT_SCR_HWDCN20x0400 -#define RBIT_SCR_HWDCN10x0200 /* 512 clocks */ -#define RBIT_SCR_HWDCN00x0100 /* 128 clocks */ - -#define RBIT_SCR_LPREC 0x0080 -#define RBIT_SCR_LPP16 0x0040 -#define RBIT_SCR_LPEN 0x0020 -#define RBIT_SCR_LPCLKDIV 0x001f - - -/* - * 68000 interrupt and trap vector numbers - */ -#define M68K_IVEC_BUS_ERROR 2 -#define M68K_IVEC_ADDRESS_ERROR 3 -#define M68K_IVEC_ILLEGAL_OPCODE4 -#define M68K_IVEC_ZERO_DIVIDE 5 -#define M68K_IVEC_CHK 6 -#define M68K_IVEC_TRAPV 7 -#define M68K_IVEC_PRIVILEGE 8 -#define M68K_IVEC_TRACE 9 -#define M
Re: Bacport of ARM cache, RTL and TMS570 to RTEMS 4.11 Was: Simple question about RTL
Hi Pavel, I have built the Raspberry Pi 1 and 2 BSPs with the latest 4.11 branch. I plan on testing them soon. I also tried to build the 4.11 sparc/sis BSP, but it failed to compile: ../../../../../../../rtems-src/rtems-4.11/c/src/../../cpukit/libdl/rtl-obj.c:585:47: error: 'CPU_CACHE_LINE_BYTES' undeclared (first use in this function) old_end = (uintptr_t)sync_ctx->end_va & ~(CPU_CACHE_LINE_BYTES - 1); It looks like rtl-obj.c uses CPU_CACHE_LINE_BYTES, but a grep only shows that is defined for ARM. Do we need to back port these defines for the other CPU architectures as well? Thanks, Alan > On Oct 2, 2016, at 6:06 AM, Pavel Pisa wrote: > > Hello all, > > I have pushed massive update to RTEMS-4.11 ARM BSPs > support. The cache manager and RTL update has been > prepared in response to RTL failures reported by Tim Tian > on Zynq BSP more than month ago. I have proposed > 4.11 update series at September 9. > > https://github.com/ppisa/rtems/tree/4.11-arm-update > > Code has been tested by Alan Cudmore and more RPi > versions and correction of Zynq problem has been reported > as well. Because there has not been reported any > problem on master nor on my 4.11-arm-update branch > I have pushed changes to official 4.11 tree. > > Please, check on more BSPs and applications > if all works correctly. > > I have pushed TMS570 backport from master to 4.11 as well, > there has been critical problem corrected on master > > > #2794 ARM TMS570 BSP: Serial port hangs when baudrate change > initiates before all characters are sent > > and the rest of updates is required to boot RTEMS > on TMS570LS3137 without separate loader or mixing > code with other sources. > > I expect to do some more testing of 4.11 on TMS570 HW > next week. > > From my side, I think that RTEMS 4.11 branch is in the > state where release can report Raspberry Pi 1, 2 > and TMS570 as supported now. > > Best wishes, > > Pavel > > On Tuesday 06 of September 2016 09:28:42 Pavel Pisa wrote: >> Hello Chris, >> >> On Tuesday 06 of September 2016 07:12:53 Chris Johns wrote: >>> Hi Tim and Pavel, >>> >>> Thank you for the patches and testing. I will have a chat to Joel >>> tomorrow about the patches and what we will do. If Joel agrees I may >>> test and push the patches. >>> >>> FYI I am currently looking at #2767 which is reported against 4.11 and a >>> zynq so there is real interest on these patches ending up on 4.11. >>> >>> Chris >> >> I have made 4.11 to boot on Raspberry Pi. >> >> The final patch >> >> arm/raspberrypi: minimized mainline patch move MMU in front of >> application image and correct RPi2 boot on 4.11 branch. >> https://github.com/ppisa/rtems/commit/984047e8295bb82b12700edb3aac911bd8427 >> 8af >> >> of branch >> >> https://github.com/ppisa/rtems/tree/4.11-arm-update >> >> series. >> >> Tickets >> >> https://devel.rtems.org/ticket/2783 >> >> https://devel.rtems.org/ticket/2782 >> >> At least one of these tickets can be assigned to all patches >> in this backports branch. >> >> I have to move to other tasks today to have students exams prepared >> and to have resources to pay our company bills. >> >> I understand that modifications are huge for 4.11 >> >> If there is interrest I can resend series to mainlinglist >> when I return from our potential customers meeting. >> >> Best wishes, >> >> Pavel > ___ > 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
