Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Hi Ahmad, > > I have the code locally - but this time I will not have it posted before > > it is tested. > > > > Then I cloned the latest at91bootstrap - but they no longer support old > > at91sam92xx CPUs. > > So it was time to enable bootstrap support for at91sam9263. > > > > In the past I had something working, but alas no luck this time. > > > > Can anyone (Ahmad?) help me a little how to get the bootstrap > > functionality working on the at91sam9263? > > > > I do not expect patches, but I hope for something that can point me in > > the right way to do it. > > > > I have skov-arm9cpu boards (plenty - as they are mostly retired by SKOV) > > and one at91sam9263ek where I can test. > > The skov-arm9cpu looks like it already runs first stage without at91bootstrap? > So the issue is only with at91sam9263ek? For the moment my focus is on the skov-arm9cpu - and here bootstrap is not (yet) functional. But I think with all the good feedback from you and Oleksij I should manage. Thanks for the replies! > > We see very little interest in at91sam92* boards and we could decide > > to retire all the boards that are not updated to multi-image. > > As long as it works, I guess most people don't see a reason make interest > publicly known. > > > This could simplify things - and if there is interest the missing boards > > can be brought back to life provided they are updated to multi image. > > Any comments on this? > > I have only worked on SAMA5D3 and SAMA5D2. Of course, I'd like to see > board code in AT91 replaced with DT-enabled/multi-image-compatible code, > but I don't think it will happen. I don't think the maintenance burden > is high, so I'd just leave it as is. If it bitrots and people complain, > we can nudge them into the right direction. OK, you are right that if it just works no reason to touch it. I will do the patches alongside the current codebase then. Sam ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Hi Sam,
On 09.01.22 20:53, Sam Ravnborg wrote:
> Hi,
>>
>> Can anyone (Ahmad?) help me a little how to get the bootstrap
>> functionality working on the at91sam9263?
>
> To answer the obvious questions - what have I done so far.
>
> - I have an at91bootstrap generated BOOT.BIN that works.
> This ruins out a lot of possible issues with the SD card
> as the board boots from the SD card with the at91bootstrap based
> BOOT.BIN.
So the arm9cpu boots XIP from NAND, but the 9263ek boots from SD?
Did I get that right?
> - The toolchain used is generated from buildroot, and I do not have any
> proof that it works as I have not had any successes.
> So far I have assumed that it works.
>
> - The configuration used is pasted below.
>
> - The board I use is the skov-arm9cpu which I know works as it boots
> barebox with the at91bootstrap BOOT.BIN
>
> - I have only a limited set of patches - pasted below.
>
> - Latest barebox from the master branch
>
> - I have tried to power cycle and reset of the board - no change
>
> - There is a ">RomBOOT" prompt - but nothing else
>
> Sam
>
>
> diff --git a/arch/arm/boards/skov-arm9cpu/lowlevel.c
> b/arch/arm/boards/skov-arm9cpu/lowlevel.c
> index d335953a7..8d5c0b025 100644
> --- a/arch/arm/boards/skov-arm9cpu/lowlevel.c
> +++ b/arch/arm/boards/skov-arm9cpu/lowlevel.c
> @@ -3,14 +3,20 @@
>
> #include
>
> +#include
> +
> #include
>
> #include
> #include
> +#include
> +#include
>
> #define MASTER_PLL_MUL 171
> #define MASTER_PLL_DIV 14
>
> +#define MASTER_CLOCK(2/2)
> +
> static void __bare_init skovarm9cpu_board_config(struct
> at91sam926x_board_cfg *cfg)
> {
> /* Disable Watchdog */
> @@ -96,6 +102,18 @@ static void __bare_init skovarm9cpu_board_config(struct
> at91sam926x_board_cfg *c
> AT91_RSTC_RSTTYP_WATCHDOG;
> }
>
> +static void dbgu_init(void)
> +{
> + void __iomem *pio = IOMEM(AT91SAM9263_BASE_PIOC);
> + // Setup DBGU uart
> + at91_mux_pio3_pin(pio, pin_to_mask(AT91_PIN_PC30), AT91_MUX_PERIPH_A,
> GPIO_PULL_UP); // DRXD
> + at91_mux_pio3_pin(pio, pin_to_mask(AT91_PIN_PC31), AT91_MUX_PERIPH_A,
> 0); // DTXD
> +
> + at91_dbgu_setup_ll(IOMEM(AT91_BASE_DBGU1), MASTER_CLOCK, 115200);
> + pbl_set_putc(at91_dbgu_putc, IOMEM(AT91_BASE_DBGU1));
That's not safe to call here. pbl_set_putc accesses global variables, but there
has
been no relocation yet.
> + putc_ll('#');
> +}
> +
> static void __bare_init skov_arm9cpu_init(void *fdt)
> {
> struct at91sam926x_board_cfg cfg;
> @@ -108,6 +126,8 @@ static void __bare_init skov_arm9cpu_init(void *fdt)
> skovarm9cpu_board_config();
> at91sam9263_board_init();
>
> + dbgu_init();
> +
If you have a functional skov arm9cpu configuration. Could you figure out the
bare
minimum of clock setup you need for DEBUG_LL to work and move that further up?
Once you get get to the barebox_arm_entry, you'll want to call into the PBL
xload from MMC stuff instead, like Oleksij did for the SAMA5D3.
Cheers,
Ahmad
> barebox_arm_entry(AT91_CHIPSELECT_1, at91_get_sdram_size(cfg.sdramc),
> fdt);
> }
>
> #
> # Automatically generated file; DO NOT EDIT.
> # Barebox/arm 2021.12.0 Configuration
> #
> CONFIG_ARM=y
> CONFIG_HAVE_MACH_ARM_HEAD=y
> CONFIG_ARM_USE_COMPRESSED_DTB=y
> CONFIG_TEXT_BASE=0x0
>
> #
> # System Type
> #
> CONFIG_ARCH_AT91=y
> # CONFIG_ARCH_BCM283X is not set
> # CONFIG_ARCH_CLPS711X is not set
> # CONFIG_ARCH_DAVINCI is not set
> # CONFIG_ARCH_DIGIC is not set
> # CONFIG_ARCH_EP93XX is not set
> # CONFIG_ARCH_IMX is not set
> # CONFIG_ARCH_LAYERSCAPE is not set
> # CONFIG_ARCH_MVEBU is not set
> # CONFIG_ARCH_MXS is not set
> # CONFIG_ARCH_NOMADIK is not set
> # CONFIG_ARCH_OMAP is not set
> # CONFIG_ARCH_PXA is not set
> # CONFIG_ARCH_ROCKCHIP is not set
> # CONFIG_ARCH_SOCFPGA is not set
> # CONFIG_ARCH_S3C24xx is not set
> # CONFIG_ARCH_S5PCxx is not set
> # CONFIG_ARCH_S3C64xx is not set
> # CONFIG_ARCH_STM32MP is not set
> # CONFIG_ARCH_VERSATILE is not set
> # CONFIG_ARCH_VEXPRESS is not set
> # CONFIG_ARCH_TEGRA is not set
> # CONFIG_ARCH_UEMD is not set
> # CONFIG_ARCH_ZYNQ is not set
> # CONFIG_ARCH_ZYNQMP is not set
> # CONFIG_ARCH_ARM64_VIRT is not set
>
> #
> # Processor Type
> #
> CONFIG_CPU_32=y
> CONFIG_CPU_ARM926T=y
> CONFIG_CPU_32v5=y
>
> #
> # processor features
> #
> # CONFIG_BOOT_ENDIANNESS_SWITCH is not set
> CONFIG_HAVE_AT91_UTMI=y
> CONFIG_HAVE_AT91_USB_CLK=y
> CONFIG_COMMON_CLK_AT91=y
> CONFIG_HAVE_AT91_SMD=y
> CONFIG_HAVE_AT91_BOOTSTRAP=y
> CONFIG_AT91SAM926X_BOARD_INIT=y
> CONFIG_AT91SAM9_SMC=y
> CONFIG_HAVE_AT91SAM9_RST=y
> CONFIG_SOC_AT91SAM9=y
> CONFIG_ARCH_TEXT_BASE=0x23f0
> CONFIG_HAVE_AT91_LOAD_BAREBOX_SRAM=y
>
> #
> # Atmel AT91 System-on-Chip
> #
> CONFIG_SOC_AT91SAM9263=y
> CONFIG_AT91_MULTI_BOARDS=y
> CONFIG_MACH_SKOV_ARM9CPU=y
> # CONFIG_MACH_AT91SAM9263EK is not set
> #
Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Hello Sam, On 09.01.22 19:38, Sam Ravnborg wrote: > Hi all. > > This little detour started because Ahmad pointed out I had made > a stupid mistake in pwm-atmel. > So I decided I wanted to give it a spin to verify if it actually works > now. > > The first challenge I encountered was that said driver had bit-rotted > as it used the old pwm framework - so I updated it from the Linux > kernel. Ouch. How did I miss this :/ > I have the code locally - but this time I will not have it posted before > it is tested. > > Then I cloned the latest at91bootstrap - but they no longer support old > at91sam92xx CPUs. > So it was time to enable bootstrap support for at91sam9263. > > In the past I had something working, but alas no luck this time. > > Can anyone (Ahmad?) help me a little how to get the bootstrap > functionality working on the at91sam9263? > > I do not expect patches, but I hope for something that can point me in > the right way to do it. > > I have skov-arm9cpu boards (plenty - as they are mostly retired by SKOV) > and one at91sam9263ek where I can test. The skov-arm9cpu looks like it already runs first stage without at91bootstrap? So the issue is only with at91sam9263ek? > We see very little interest in at91sam92* boards and we could decide > to retire all the boards that are not updated to multi-image. As long as it works, I guess most people don't see a reason make interest publicly known. > This could simplify things - and if there is interest the missing boards > can be brought back to life provided they are updated to multi image. > Any comments on this? I have only worked on SAMA5D3 and SAMA5D2. Of course, I'd like to see board code in AT91 replaced with DT-enabled/multi-image-compatible code, but I don't think it will happen. I don't think the maintenance burden is high, so I'd just leave it as is. If it bitrots and people complain, we can nudge them into the right direction. > I am happy to type the patches - and verify that the boards I have works. Great. Looking forward to more boards in at91_multi_defconfig. Cheers, Ahmad > > Sam > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Hi Oleksij, > > By porting sama5d3 I noticed that bootROM is resetting configuration for > at least some of ip cores. So, the main question is, do everything needed > for uart is still pre-configured? For example pllc and clk settings? I found this in the data sheet that agrees with you: " Before performing the jump to the application in internal SRAM, all the PIOs and peripherals used in the boot program are set to their reset state. " I will throw some hours after this in the weekend to see if I can get it up and running. > > As soon as UART is working, every thing else will be not really hard to > do :) Agree, except that I need find a nice way to add whatever I do to the current at91 stuff. But that is part of the fun. Sam ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Hi Sam,
On Sun, Jan 09, 2022 at 08:53:49PM +0100, Sam Ravnborg wrote:
> Hi,
> >
> > Can anyone (Ahmad?) help me a little how to get the bootstrap
> > functionality working on the at91sam9263?
>
> To answer the obvious questions - what have I done so far.
>
> - I have an at91bootstrap generated BOOT.BIN that works.
> This ruins out a lot of possible issues with the SD card
> as the board boots from the SD card with the at91bootstrap based
> BOOT.BIN.
>
> - The toolchain used is generated from buildroot, and I do not have any
> proof that it works as I have not had any successes.
> So far I have assumed that it works.
>
> - The configuration used is pasted below.
>
> - The board I use is the skov-arm9cpu which I know works as it boots
> barebox with the at91bootstrap BOOT.BIN
>
> - I have only a limited set of patches - pasted below.
>
> - Latest barebox from the master branch
>
> - I have tried to power cycle and reset of the board - no change
>
> - There is a ">RomBOOT" prompt - but nothing else
>
> Sam
By porting sama5d3 I noticed that bootROM is resetting configuration for
at least some of ip cores. So, the main question is, do everything needed
for uart is still pre-configured? For example pllc and clk settings?
I would recommend to measure with scope the uart lines and see if you
get something and if it is at expected frequency. JTAG would probably
help as well to see what code is currently executed and if register
configurations are in expected state.
As soon as UART is working, every thing else will be not really hard to
do :)
> diff --git a/arch/arm/boards/skov-arm9cpu/lowlevel.c
> b/arch/arm/boards/skov-arm9cpu/lowlevel.c
> index d335953a7..8d5c0b025 100644
> --- a/arch/arm/boards/skov-arm9cpu/lowlevel.c
> +++ b/arch/arm/boards/skov-arm9cpu/lowlevel.c
> @@ -3,14 +3,20 @@
>
> #include
>
> +#include
> +
> #include
>
> #include
> #include
> +#include
> +#include
>
> #define MASTER_PLL_MUL 171
> #define MASTER_PLL_DIV 14
>
> +#define MASTER_CLOCK(2/2)
> +
> static void __bare_init skovarm9cpu_board_config(struct
> at91sam926x_board_cfg *cfg)
> {
> /* Disable Watchdog */
> @@ -96,6 +102,18 @@ static void __bare_init skovarm9cpu_board_config(struct
> at91sam926x_board_cfg *c
> AT91_RSTC_RSTTYP_WATCHDOG;
> }
>
> +static void dbgu_init(void)
> +{
> + void __iomem *pio = IOMEM(AT91SAM9263_BASE_PIOC);
> + // Setup DBGU uart
> + at91_mux_pio3_pin(pio, pin_to_mask(AT91_PIN_PC30), AT91_MUX_PERIPH_A,
> GPIO_PULL_UP); // DRXD
> + at91_mux_pio3_pin(pio, pin_to_mask(AT91_PIN_PC31), AT91_MUX_PERIPH_A,
> 0); // DTXD
> +
> + at91_dbgu_setup_ll(IOMEM(AT91_BASE_DBGU1), MASTER_CLOCK, 115200);
> + pbl_set_putc(at91_dbgu_putc, IOMEM(AT91_BASE_DBGU1));
> + putc_ll('#');
> +}
> +
> static void __bare_init skov_arm9cpu_init(void *fdt)
> {
> struct at91sam926x_board_cfg cfg;
> @@ -108,6 +126,8 @@ static void __bare_init skov_arm9cpu_init(void *fdt)
> skovarm9cpu_board_config();
> at91sam9263_board_init();
>
> + dbgu_init();
> +
> barebox_arm_entry(AT91_CHIPSELECT_1, at91_get_sdram_size(cfg.sdramc),
> fdt);
> }
>
> #
> # Automatically generated file; DO NOT EDIT.
> # Barebox/arm 2021.12.0 Configuration
> #
> CONFIG_ARM=y
> CONFIG_HAVE_MACH_ARM_HEAD=y
> CONFIG_ARM_USE_COMPRESSED_DTB=y
> CONFIG_TEXT_BASE=0x0
>
> #
> # System Type
> #
> CONFIG_ARCH_AT91=y
> # CONFIG_ARCH_BCM283X is not set
> # CONFIG_ARCH_CLPS711X is not set
> # CONFIG_ARCH_DAVINCI is not set
> # CONFIG_ARCH_DIGIC is not set
> # CONFIG_ARCH_EP93XX is not set
> # CONFIG_ARCH_IMX is not set
> # CONFIG_ARCH_LAYERSCAPE is not set
> # CONFIG_ARCH_MVEBU is not set
> # CONFIG_ARCH_MXS is not set
> # CONFIG_ARCH_NOMADIK is not set
> # CONFIG_ARCH_OMAP is not set
> # CONFIG_ARCH_PXA is not set
> # CONFIG_ARCH_ROCKCHIP is not set
> # CONFIG_ARCH_SOCFPGA is not set
> # CONFIG_ARCH_S3C24xx is not set
> # CONFIG_ARCH_S5PCxx is not set
> # CONFIG_ARCH_S3C64xx is not set
> # CONFIG_ARCH_STM32MP is not set
> # CONFIG_ARCH_VERSATILE is not set
> # CONFIG_ARCH_VEXPRESS is not set
> # CONFIG_ARCH_TEGRA is not set
> # CONFIG_ARCH_UEMD is not set
> # CONFIG_ARCH_ZYNQ is not set
> # CONFIG_ARCH_ZYNQMP is not set
> # CONFIG_ARCH_ARM64_VIRT is not set
>
> #
> # Processor Type
> #
> CONFIG_CPU_32=y
> CONFIG_CPU_ARM926T=y
> CONFIG_CPU_32v5=y
>
> #
> # processor features
> #
> # CONFIG_BOOT_ENDIANNESS_SWITCH is not set
> CONFIG_HAVE_AT91_UTMI=y
> CONFIG_HAVE_AT91_USB_CLK=y
> CONFIG_COMMON_CLK_AT91=y
> CONFIG_HAVE_AT91_SMD=y
> CONFIG_HAVE_AT91_BOOTSTRAP=y
> CONFIG_AT91SAM926X_BOARD_INIT=y
> CONFIG_AT91SAM9_SMC=y
> CONFIG_HAVE_AT91SAM9_RST=y
> CONFIG_SOC_AT91SAM9=y
> CONFIG_ARCH_TEXT_BASE=0x23f0
> CONFIG_HAVE_AT91_LOAD_BAREBOX_SRAM=y
>
> #
> # Atmel AT91 System-on-Chip
> #
> CONFIG_SOC_AT91SAM9263=y
> CONFIG_AT91_MULTI_BOARDS=y
> CONFIG_MACH_SKOV_ARM9CPU=y
> #
Re: Q about bootstrap support for at91sam92* boards and proposal for retirement
Hi,
>
> Can anyone (Ahmad?) help me a little how to get the bootstrap
> functionality working on the at91sam9263?
To answer the obvious questions - what have I done so far.
- I have an at91bootstrap generated BOOT.BIN that works.
This ruins out a lot of possible issues with the SD card
as the board boots from the SD card with the at91bootstrap based
BOOT.BIN.
- The toolchain used is generated from buildroot, and I do not have any
proof that it works as I have not had any successes.
So far I have assumed that it works.
- The configuration used is pasted below.
- The board I use is the skov-arm9cpu which I know works as it boots
barebox with the at91bootstrap BOOT.BIN
- I have only a limited set of patches - pasted below.
- Latest barebox from the master branch
- I have tried to power cycle and reset of the board - no change
- There is a ">RomBOOT" prompt - but nothing else
Sam
diff --git a/arch/arm/boards/skov-arm9cpu/lowlevel.c
b/arch/arm/boards/skov-arm9cpu/lowlevel.c
index d335953a7..8d5c0b025 100644
--- a/arch/arm/boards/skov-arm9cpu/lowlevel.c
+++ b/arch/arm/boards/skov-arm9cpu/lowlevel.c
@@ -3,14 +3,20 @@
#include
+#include
+
#include
#include
#include
+#include
+#include
#define MASTER_PLL_MUL 171
#define MASTER_PLL_DIV 14
+#define MASTER_CLOCK(2/2)
+
static void __bare_init skovarm9cpu_board_config(struct at91sam926x_board_cfg
*cfg)
{
/* Disable Watchdog */
@@ -96,6 +102,18 @@ static void __bare_init skovarm9cpu_board_config(struct
at91sam926x_board_cfg *c
AT91_RSTC_RSTTYP_WATCHDOG;
}
+static void dbgu_init(void)
+{
+ void __iomem *pio = IOMEM(AT91SAM9263_BASE_PIOC);
+ // Setup DBGU uart
+ at91_mux_pio3_pin(pio, pin_to_mask(AT91_PIN_PC30), AT91_MUX_PERIPH_A,
GPIO_PULL_UP); // DRXD
+ at91_mux_pio3_pin(pio, pin_to_mask(AT91_PIN_PC31), AT91_MUX_PERIPH_A,
0); // DTXD
+
+ at91_dbgu_setup_ll(IOMEM(AT91_BASE_DBGU1), MASTER_CLOCK, 115200);
+ pbl_set_putc(at91_dbgu_putc, IOMEM(AT91_BASE_DBGU1));
+ putc_ll('#');
+}
+
static void __bare_init skov_arm9cpu_init(void *fdt)
{
struct at91sam926x_board_cfg cfg;
@@ -108,6 +126,8 @@ static void __bare_init skov_arm9cpu_init(void *fdt)
skovarm9cpu_board_config();
at91sam9263_board_init();
+ dbgu_init();
+
barebox_arm_entry(AT91_CHIPSELECT_1, at91_get_sdram_size(cfg.sdramc),
fdt);
}
#
# Automatically generated file; DO NOT EDIT.
# Barebox/arm 2021.12.0 Configuration
#
CONFIG_ARM=y
CONFIG_HAVE_MACH_ARM_HEAD=y
CONFIG_ARM_USE_COMPRESSED_DTB=y
CONFIG_TEXT_BASE=0x0
#
# System Type
#
CONFIG_ARCH_AT91=y
# CONFIG_ARCH_BCM283X is not set
# CONFIG_ARCH_CLPS711X is not set
# CONFIG_ARCH_DAVINCI is not set
# CONFIG_ARCH_DIGIC is not set
# CONFIG_ARCH_EP93XX is not set
# CONFIG_ARCH_IMX is not set
# CONFIG_ARCH_LAYERSCAPE is not set
# CONFIG_ARCH_MVEBU is not set
# CONFIG_ARCH_MXS is not set
# CONFIG_ARCH_NOMADIK is not set
# CONFIG_ARCH_OMAP is not set
# CONFIG_ARCH_PXA is not set
# CONFIG_ARCH_ROCKCHIP is not set
# CONFIG_ARCH_SOCFPGA is not set
# CONFIG_ARCH_S3C24xx is not set
# CONFIG_ARCH_S5PCxx is not set
# CONFIG_ARCH_S3C64xx is not set
# CONFIG_ARCH_STM32MP is not set
# CONFIG_ARCH_VERSATILE is not set
# CONFIG_ARCH_VEXPRESS is not set
# CONFIG_ARCH_TEGRA is not set
# CONFIG_ARCH_UEMD is not set
# CONFIG_ARCH_ZYNQ is not set
# CONFIG_ARCH_ZYNQMP is not set
# CONFIG_ARCH_ARM64_VIRT is not set
#
# Processor Type
#
CONFIG_CPU_32=y
CONFIG_CPU_ARM926T=y
CONFIG_CPU_32v5=y
#
# processor features
#
# CONFIG_BOOT_ENDIANNESS_SWITCH is not set
CONFIG_HAVE_AT91_UTMI=y
CONFIG_HAVE_AT91_USB_CLK=y
CONFIG_COMMON_CLK_AT91=y
CONFIG_HAVE_AT91_SMD=y
CONFIG_HAVE_AT91_BOOTSTRAP=y
CONFIG_AT91SAM926X_BOARD_INIT=y
CONFIG_AT91SAM9_SMC=y
CONFIG_HAVE_AT91SAM9_RST=y
CONFIG_SOC_AT91SAM9=y
CONFIG_ARCH_TEXT_BASE=0x23f0
CONFIG_HAVE_AT91_LOAD_BAREBOX_SRAM=y
#
# Atmel AT91 System-on-Chip
#
CONFIG_SOC_AT91SAM9263=y
CONFIG_AT91_MULTI_BOARDS=y
CONFIG_MACH_SKOV_ARM9CPU=y
# CONFIG_MACH_AT91SAM9263EK is not set
# CONFIG_MACH_AT91SAM9X5EK is not set
# CONFIG_MACH_MICROCHIP_KSZ9477_EVB is not set
# CONFIG_MACH_SAMA5D3_XPLAINED is not set
# CONFIG_MACH_SAMA5D27_SOM1 is not set
# CONFIG_MACH_SAMA5D27_GIANTBOARD is not set
#
# AT91 Board Options
#
CONFIG_AT91_BOOTSTRAP=y
# CONFIG_AT91_LOAD_BAREBOX_SRAM is not set
CONFIG_BAREBOX_MAX_IMAGE_SIZE=0x4
# CONFIG_BOARD_ARM_GENERIC_DT is not set
# CONFIG_AEABI is not set
# end of System Type
#
# ARM specific settings
#
# CONFIG_ARM_OPTIMZED_STRING_FUNCTIONS is not set
CONFIG_ARM_EXCEPTIONS=y
# CONFIG_ARM_SEMIHOSTING is not set
# end of ARM specific settings
CONFIG_GREGORIAN_CALENDER=y
CONFIG_HAS_KALLSYMS=y
CONFIG_HAS_MODULES=y
CONFIG_HAS_CACHE=y
CONFIG_HAS_DMA=y
CONFIG_HAS_ARCH_SJLJ=y
CONFIG_GENERIC_GPIO=y
CONFIG_BLOCK=y
CONFIG_BLOCK_WRITE=y
CONFIG_USE_COMPRESSED_DTB=y
CONFIG_FILETYPE=y
#
# General Settings
#
Q about bootstrap support for at91sam92* boards and proposal for retirement
Hi all. This little detour started because Ahmad pointed out I had made a stupid mistake in pwm-atmel. So I decided I wanted to give it a spin to verify if it actually works now. The first challenge I encountered was that said driver had bit-rotted as it used the old pwm framework - so I updated it from the Linux kernel. I have the code locally - but this time I will not have it posted before it is tested. Then I cloned the latest at91bootstrap - but they no longer support old at91sam92xx CPUs. So it was time to enable bootstrap support for at91sam9263. In the past I had something working, but alas no luck this time. Can anyone (Ahmad?) help me a little how to get the bootstrap functionality working on the at91sam9263? I do not expect patches, but I hope for something that can point me in the right way to do it. I have skov-arm9cpu boards (plenty - as they are mostly retired by SKOV) and one at91sam9263ek where I can test. We see very little interest in at91sam92* boards and we could decide to retire all the boards that are not updated to multi-image. This could simplify things - and if there is interest the missing boards can be brought back to life provided they are updated to multi image. Any comments on this? I am happy to type the patches - and verify that the boards I have works. Sam ___ barebox mailing list barebox@lists.infradead.org http://lists.infradead.org/mailman/listinfo/barebox
