30 Jan, 2018

1 commit

  • Since 'commit af2f44267 ("fdc spl: use different BOARD_INIT MACRO for spl and tpl")'
    board stm32f746-disco can't boot.

    The macro CONFIG_IS_ENABLED() can't evaluate the value of
    CONFIG_SPL_BOARD_INIT as it was defined in include/configs/stm32f746-disco.h
    without attributed value.

    Moving CONFIG_SPL_BOARD_INIT from stm32f746-disco.h to mach-stm32/Kconfig
    fixes this issue.

    Fixes: af2f44267 ("fdc spl: use different BOARD_INIT MACRO for spl and tpl")
    Signed-off-by: Patrice Chotard

    Patrice Chotard
     

28 Jan, 2018

1 commit


20 Jan, 2018

2 commits


10 Jan, 2018

3 commits

  • This board offers :

    _ STM32F469NIH6 microcontroller featuring 2 Mbytes of Flash memory
    and 324 Kbytes of RAM in BGA216 package
    _ On-board ST-LINK/V2-1 SWD debugger, supporting USB reenumeration capability:
    _ Mbed-enabled (mbed.org)
    _ USB functions: USB virtual COM port, mass storage, debug port
    _ 4 inches 800x480 pixel TFT color LCD with MIPI DSI interface and capacitive
    touch screen
    _ SAI Audio DAC, with a stereo headphone output jack
    _ 3 MEMS microphones
    _ MicroSD card connector
    _ I2C extension connector
    _ 4Mx32bit SDRAM
    _ 128-Mbit Quad-SPI NOR Flash
    _ Reset and wake-up buttons
    _ 4 color user LEDs
    _ USB OTG FS with Micro-AB connector
    _ Three power supply options:
    _ Expansion connectors and Arduino™ UNO V3 connectors

    Signed-off-by: Patrice Chotard

    Patrice Chotard
     
  • Use available DM clk_stm32f.c driver instead of dedicated
    mach-stm32/stm32f4/clock.c.

    Migrate periph_clock defines from stm32_periph.h directly in
    CLK driver. These periph_clock defines will be removed when STMMAC,
    TIMER2 and SYSCFG drivers will support DM CLK.

    Enable also CLK flag.

    Signed-off-by: Patrice Chotard

    Patrice Chotard
     
  • In order to use common clock driver between STM32F4 and
    STM32F7, remove clock_get() call
    As APB_PSC is always set to 2, only case when
    clock_get(CLOCK_AHB) != clock_get(CLOCK_APB1) is kept

    Signed-off-by: Patrice Chotard

    Patrice Chotard
     

30 Nov, 2017

2 commits


06 Nov, 2017

1 commit


09 Oct, 2017

1 commit


22 Sep, 2017

1 commit


27 Aug, 2017

1 commit


14 Aug, 2017

2 commits

  • A few years ago STM32F1 SoCs support has been added :
    0144caf22ce6acd5c gpio: stm32: add stm32f1 support
    2d18ef2364fd3561a ARMv7M: add STM32F1 support

    But neither STM32F1 dedicated defconfig nor board was
    associated to these commits.

    Got confirmation from Tom Rini and Matt Porter to remove
    all this code [1]

    [1] http://u-boot.10912.n7.nabble.com/Remove-STM32F1-support-td301603.html

    Signed-off-by: Patrice Chotard
    Reviewed-by: Tom Rini

    Patrice Chotard
     
  • The if in the else branch is superfluous.
    We can use a simple if.

    The problem was indicated by cppcheck.

    Signed-off-by: Heinrich Schuchardt

    xypron.glpk@gmx.de
     

05 Aug, 2017

1 commit

  • fix the following compilation error reported by buidlman:

    arm: + stm32f429-discovery
    +arch/arm/mach-stm32/stm32f4/soc.c: In function 'arch_cpu_init':
    +arch/arm/mach-stm32/stm32f4/soc.c:30:2: error: 'for' loop initial declarations are only allowed in C99 or C11 mode
    + for (int i = 0; i < ARRAY_SIZE(stm32_region_config); i++)
    + ^
    +arch/arm/mach-stm32/stm32f4/soc.c:30:2: note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to compile your code
    +make[3]: *** [arch/arm/mach-stm32/stm32f4/soc.o] Error 1
    +make[2]: *** [arch/arm/mach-stm32/stm32f4] Error 2
    +make[1]: *** [arch/arm/mach-stm32] Error 2
    +make: *** [sub-make] Error 2

    Signed-off-by: Patrice Chotard
    Acked-by: Vikas Manocha

    Patrice Chotard
     

07 Jul, 2017

1 commit

  • The current code gives a warning:

    arch/arm/mach-stm32/stm32f7/soc.c: In function 'arch_cpu_init':
    arch/arm/mach-stm32/stm32f7/soc.c:38:2: error: 'for' loop initial
    declarations are only allowed in C99 or C11 mode
    for (int i = 0; i < ARRAY_SIZE(stm32_region_config); i++)
    ^
    arch/arm/mach-stm32/stm32f7/soc.c:38:2: note: use option -std=c99,
    -std=gnu99, -std=c11 or -std=gnu11 to compile your code

    Fix it by moving the declaration to the top of the function.

    Signed-off-by: Simon Glass
    Series-cc trini

    Simon Glass
     

09 Jun, 2017

3 commits

  • With xip booting configuration, we don't need to copy the next image
    (U-Boot or linux xipimage) from flash to sdram area.

    Flash memory organization is like this:
    spl-U-Boot: u-boot-spl.bin : 0x0800_0000
    U-Boot : u-boot-dtb.bin : 0x0800_8000
    linux : xipImage : 0x0800_8000

    It is also possible to have U-Boot binary & linux binaries configured at
    different addresses of flash memory like U-Boot at 0x0800_8000 & linux
    xipImage at 0x0800_4000. But in any case, spl-U-Boot needs to be compiled for
    U-Boot as next binary with SPL_OS_BOOT option disabled.
    By default, spl is configured to boot linux xipImage.

    Signed-off-by: Vikas Manocha

    Vikas Manocha
     
  • Signed-off-by: Vikas Manocha

    Vikas Manocha
     
  • This commit supports booting from stm32 internal nor flash. spl U-Boot
    initializes the sdram memory, copies next image (e.g. standard U-Boot)
    to sdram & then jumps to entry point.

    Here are the flash memory addresses for U-Boot-spl & standard U-Boot:
    - spl U-Boot : 0x0800_0000
    - standard U-Boot : 0x0800_8000

    To compile u-boot without spl: Remove SUPPORT_SPL configuration
    (arch/arm/mach-stm32/Kconfig)

    Signed-off-by: Vikas Manocha
    [trini: Rework Kconfig logic a bit]
    Signed-off-by: Tom Rini

    Vikas Manocha
     

12 May, 2017

2 commits

  • This configuration should be valid for all F7 family devices in general.
    Here is the regions info:

    - Region0 : 4GB : cacheable & executable.
    - Region1 : 512MB : text area : strogly ordered & executable.
    - Region2 : 512MB : peripherals : device memory & non-executable.
    - Region3 : 512MB : peripherals : device memory & non-executable.
    - Region4 : 512MB : cortexM area: strongly ordered & non-executable.

    Higher region number overrides the lower region configuration.

    Signed-off-by: Vikas Manocha

    Vikas Manocha
     
  • Signed-off-by: Vikas Manocha

    Vikas Manocha
     

08 Apr, 2017

1 commit


18 Mar, 2017

1 commit


29 Jan, 2017

4 commits


22 Jul, 2016

1 commit


15 Jul, 2016

3 commits


27 Mar, 2016

1 commit


25 Feb, 2016

2 commits


08 Feb, 2016

1 commit


20 Jan, 2016

1 commit