On Sun, Apr 26, 2020 at 07:38:44AM -0600, Gregory Nutt wrote:
>
> >>I recently started playing with the Core746I board from waveshare.
> >>It is quite different from the stm32f746g-disco.
> >>Seeveral IO are differently, the SDRAM is connected to bank 2, it
> >>has a different xtal.
> >>The stm32f746-ws looks like it could be for the waveshare board.
> >>At least the PLL setup makes sense for the 8MHz xtal.
> >>However there is no readme and I couldn't get details via commitlogs
> >>either - maybe there is, but I failed to find.
> >
> >I don't know the answer to your other question, but as far as the git logs,
> >recently (a year ago?) the boards directories were refactored. They used to
> >be in TOPDIR/configs, now they're in TOPDIR/boards and organized by arch,
> >mcu, board, and it seems that git doesn't know how to follow the
> >directories back in time across moves/renames. Maybe someone more
> >knowledgeable about git can enlighten us how to follow the logs to before
> >the move. I think you'll find more information there.
>
> Try 'git log --follow'
>
> --follow
> Continue listing the history of a file beyond renames (works
> only
> for a single file).
>
> It doesn't always work as expected, it depends on how good a job GIT did
> of identifying the predecessor file.
All files I've tested end in more or less something like this:
commit ac6581acecac998e673e67891754cb836a165994
Author: Gregory Nutt <gn...@nuttx.org>
Date: Mon Nov 7 08:28:39 2016 -0600
Changes from review of last PR
commit 6f2e37e3adb3da2bcb3a7fe0bacfc23b7dd9707d
Author: Lok Tep <lok...@yahoo.com>
Date: Sun Jun 19 23:06:21 2016 +0200
mmc + usb
commit 5e8d2347acebb133b4c94d2167799e5dbea4a149
Author: pkolesnikov <peter.kolesni...@external.telekom.de>
Date: Mon May 23 15:05:56 2016 +0200
copy nucleo-144 to stm32f746-ws
So it is derived from the nucleo-144, which is interesting, since it
has an 8MHz xtal as well.
So far I thought it was derived from stm32f746g-disco, because some
files say stm32f746g-disco in their comments, but no idea in which
state the nucleo-144 tree was in 2016.
Ah - here is more info:
config ARCH_BOARD_STM32F746_WS
bool "Waveshare STM32F746 board"
depends on ARCH_CHIP_STM32F746IG
---help---
Waveshare STM32F746 development board featuring the STM32F746IG
MCU.
So this is indeed for a Waveshare board.
Other waveshare boards also use *-ws directories.
To my knowledge the Core746I is the only board Waveshare has with
the STM32F746.
Well ok - then I assume it is best to extend the stm32f746-ws tree.
And create a readme...
The SDRAM is part of the module, so support belongs to this in any
case.
I can't test some of the optional IO boards yet, but will add what I
have.
--
B.Walter <be...@bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
