RiOTboard: add new board
PATCH 1/2 RiOTboard: add new board
this board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
- UART2 (console)
- eMMC
- SDCard
- uSDCard
- Ethernet
- USB Host (through 4 ports hub)
- HDMI output
- I2C 1/2/3
Boot on eMMC and through USB loader are tested.
For more informations on this board : http://www.riotboard.org/
--- board/embest/riotboard/Makefile | 9 + board/embest/riotboard/riotboard.c | 493 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/riotboard.h | 299 ++++++++++++++++++++++ 4 files changed, 802 insertions(+) create mode 100644 board/embest/riotboard/Makefile create mode 100644 board/embest/riotboard/riotboard.c create mode 100644 include/configs/riotboard.h
board/embest/riotboard/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# +# Copyright (C) 2007, Guennadi Liakhovetski <[email protected]> +# +# (C) Copyright 2011 Freescale Semiconductor, Inc. +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y := riotboard.o
board/embest/riotboard/riotboard.c new file +493 -0
493 lines not on this page · raw message
boards.cfg +1 -0
@@ -323,6 +323,7 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> +Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/riotboard.h new file +299 -0
299 lines not on this page · raw message
Signature · 1 line
1.8.5.3
PATCH 2/2 MarSBoard: add new board
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR Flash
Boot on SPI NOR and through USB loader are tested.
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.html
--- board/embest/marsboard/Makefile | 9 + board/embest/marsboard/marsboard.c | 489 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/marsboard.h | 304 +++++++++++++++++++++++ 4 files changed, 803 insertions(+) create mode 100644 board/embest/marsboard/Makefile create mode 100644 board/embest/marsboard/marsboard.c create mode 100644 include/configs/marsboard.h
board/embest/marsboard/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# +# Copyright (C) 2007, Guennadi Liakhovetski <[email protected]> +# +# (C) Copyright 2011 Freescale Semiconductor, Inc. +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y := marsboard.o
board/embest/marsboard/marsboard.c new file +489 -0
489 lines not on this page · raw message
boards.cfg +1 -0
@@ -324,6 +324,7 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> +Active arm armv7 mx6 embest marsboard marsboard marsboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6q.cfg,MX6Q,DDR_MB=1024 Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/marsboard.h new file +304 -0
304 lines not on this page · raw message
Signature · 1 line
1.8.5.3
PATCH 2/2 MarSBoard: add new board
Dear Eric,
Quoted 2 lines · In message <[email protected]> you wrote:
this board is produced by Embest/Element 14 and is based on i.MX6 Dual
Comparing this patch agains the earlier one for the RiOTboard, it turns out that the differences between these two boards are really minimal.
Would it not make sense to combine all the common code? Actually I think you should be able to use all common code with just two different target names.
Best regards,
Wolfgang Denk
Signature · 4 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de To be awake is to be alive. - Henry David Thoreau, in "Walden"
PATCH 2/2 MarSBoard: add new board
Hi Wolfgang,
Le Wed, 26 Mar 2014 20:02:57 +0100,
Wolfgang Denk <[email protected]> a ?crit :
Quoted 4 lines
Quoted 2 lines · In message <[email protected]> you wrote:
this board is produced by Embest/Element 14 and is based on i.MX6 Dual
Quoted 8 lines
Comparing this patch agains the earlier one for the RiOTboard, it turns out that the differences between these two boards are really minimal.
Would it not make sense to combine all the common code? Actually I think you should be able to use all common code with just two different target names.
that seems possible : the main differences at u-boot level are the eSDHC (3 on the RiOT vs 2 on the MarS) and the SPI flash which is populated in the MarSBoard (and used for boot when the RiOT boots on the eMMC). I'll check how to factorize the code.
Eric
PATCH v2 1/2 RiOTboard: add new board
In reply to Wolfgang Denkthis board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
- UART2 (console)
- eMMC
- SDCard
- uSDCard
- Ethernet
- USB Host (through 4 ports hub)
- HDMI output
- I2C 1/2/3
Boot on eMMC and through USB loader are tested.
For more informations on this board : http://www.riotboard.org/
--- board/embest/riotboard/Makefile | 9 + board/embest/riotboard/riotboard.c | 493 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/riotboard.h | 299 ++++++++++++++++++++++ 4 files changed, 802 insertions(+) create mode 100644 board/embest/riotboard/Makefile create mode 100644 board/embest/riotboard/riotboard.c create mode 100644 include/configs/riotboard.h
board/embest/riotboard/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# +# Copyright (C) 2007, Guennadi Liakhovetski <[email protected]> +# +# (C) Copyright 2011 Freescale Semiconductor, Inc. +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y := riotboard.o
board/embest/riotboard/riotboard.c new file +493 -0
493 lines not on this page · raw message
boards.cfg +1 -0
@@ -323,6 +323,7 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> +Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/riotboard.h new file +299 -0
299 lines not on this page · raw message
Signature · 1 line
1.8.5.3
PATCH v2 2/2 MarSBoard: add new board
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR Flash
Boot on SPI NOR and through USB loader are tested.
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.html
As this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards
---
board/embest/{riotboard => mx6boards}/Makefile | 2 +-
.../riotboard.c => mx6boards/mx6boards.c} | 49 +++++++++++++++++-
boards.cfg | 3 +-
include/configs/{riotboard.h => embestmx6boards.h} | 58 ++++++++++++++++++++++
4 files changed, 108 insertions(+), 4 deletions(-)
rename board/embest/{riotboard => mx6boards}/Makefile (87%)
rename board/embest/{riotboard/riotboard.c => mx6boards/mx6boards.c} (91%)
rename include/configs/{riotboard.h => embestmx6boards.h} (84%)board/embest/mx6boards/Makefile renamed from board/embest/riotboard/Makefile +1 -1
@@ -6,4 +6,4 @@ # SPDX-License-Identifier: GPL-2.0+ # -obj-y := riotboard.o +obj-y := mx6boards.o
board/embest/mx6boards/mx6boards.c renamed from board/embest/riotboard/riotboard.c +47 -2
116 lines not on this page · raw message
boards.cfg +2 -1
@@ -323,7 +323,8 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> -Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> +Active arm armv7 mx6 embest mx6boards riotboard embestmx6boards:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024,RIOTBOARD Eric B?nard <[email protected]> +Active arm armv7 mx6 embest mx6boards marsboard embestmx6boards:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6q.cfg,MX6Q,DDR_MB=1024,MARSBOARD Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/embestmx6boards.h renamed from include/configs/riotboard.h +58 -0
103 lines not on this page · raw message
Signature · 1 line
1.8.5.3
PATCH v2 2/2 MarSBoard: add new board
Quoted 13 lines · Eric B?nard
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR FlashBoot on SPI NOR and through USB loader are tested.
Quoted 7 lines
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.htmlAs this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards
Signed-off-by Eric B?nard <[email protected]>
I understand both boards share a lot of code but I think the set of ifdef makes harder for people to understand the board code. Personally I prefer v1.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
PATCH v2 2/2 MarSBoard: add new board
Quoted 3 lines · Otavio Salvador
I understand both boards share a lot of code but I think the set of ifdef makes harder for people to understand the board code. Personally I prefer v1.
Me too. I also think the ifdefs may easily cause confusion.
For example: if someone sends a patch for Riotboard, he/she may break Marsboard without knowing.
Usually the developer has only one board and is not able to test on both boards.
Regards,
Fabio Estevam
PATCH v2 2/2 MarSBoard: add new board
Dear Fabio Estevam,
Quoted 2 lines · In message <CAOMZO5D2N1Zvo5ogEAM1_EwT-0KKamzGvRfPEekh5zymQkLrhw@mail.gmail.com>…
Me too. I also think the ifdefs may easily cause confusion.
So you suggest we remove all conditional code and use duplication everywhere? You must be joking...
Quoted 4 lines
For example: if someone sends a patch for Riotboard, he/she may break Marsboard without knowing.
Usually the developer has only one board and is not able to test on both boards.
Yes, of course. If someone touches common code he make breake things for boards he did not test. That has always been the case, everywehre. But that has never been a reason to duplicate code,
or to accept code duplication. On contrary, we permanently struggle
to reduce such duplication.
Otherwise we would have to strictly split ARM and PowerPC code, and all other architectures. We would need code copies for each SoC. Actually each board would need his own version of the whole U-Boot code. Sorry, but this is just bizarre...
Best regards,
Wolfgang Denk
Signature · 7 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
I don't mind criticism. You know me. I've never been one to take
offence at criticism. No one could say I'm the sort to take offence
at criticism -- Not twice, anyway. Not without blowing bubbles.
- Terry Pratchett, _Witches Abroad_PATCH v2 2/2 MarSBoard: add new board
Quoted 8 lines · Wolfgang Denk
Dear Fabio Estevam,
Quoted 2 lines · In message <CAOMZO5D2N1Zvo5ogEAM1_EwT-0KKamzGvRfPEekh5zymQkLrhw@mail.gmail.com>…
Me too. I also think the ifdefs may easily cause confusion.
So you suggest we remove all conditional code and use duplication everywhere? You must be joking...
Not everywhere. We are just talking about board files here, which are coming obsolete these days with device tree...
Quoted 8 lines
Quoted 5 lines
For example: if someone sends a patch for Riotboard, he/she may break Marsboard without knowing.
Usually the developer has only one board and is not able to test on both boards.
Yes, of course. If someone touches common code he make breake things for boards he did not test. That has always been the case,
So in theory yes, we could have a single board file for all the mx6 boards out there and make it full of ifdefs all over it to handle all the hardware variations.
Not so good for the users though if they want to make a simple change and then they are forced to read all the schematics of several unrelated boards.
Quoted 8 lines
everywehre. But that has never been a reason to duplicate code,
or to accept code duplication. On contrary, we permanently struggle
to reduce such duplication.Otherwise we would have to strictly split ARM and PowerPC code, and all other architectures. We would need code copies for each SoC. Actually each board would need his own version of the whole U-Boot code. Sorry, but this is just bizarre...
Looks like you are extrapolating too much here. Our discussion is only about board files, not common driver code or architectural code.
Regards,
Fabio Estevam
PATCH v2 2/2 MarSBoard: add new board
Em 27/03/2014 09:44, "Fabio Estevam" <[email protected]> escreveu:
Quoted 5 lines · Wolfgang Denk
Quoted 3 lines
Dear Fabio Estevam,
In message <
CAOMZO5D2N1Zvo5ogEAM1_EwT-0KKamzGvRfPEekh5zymQkLrhw@mail.gmail.com> you
Quoted 8 lines · wrote:
Quoted 5 lines
Quoted 2 lines
Me too. I also think the ifdefs may easily cause confusion.
So you suggest we remove all conditional code and use duplication everywhere? You must be joking...
Not everywhere. We are just talking about board files here, which are coming obsolete these days with device tree...
And this does work, as can be seen in Barebox which has it working for quite some time.
You can see equivalent patch in
http://lists.infradead.org/pipermail/barebox/2014-March/018408.html
It seems U-Boot is behind !
Regards,
PATCH v2 2/2 MarSBoard: add new board
Hi Otavio,
Le Thu, 27 Mar 2014 09:50:10 -0300,
Otavio Salvador <[email protected]> a ?crit :
Quoted 9 lines
And this does work, as can be seen in Barebox which has it working for quite some time.
You can see equivalent patch in
http://lists.infradead.org/pipermail/barebox/2014-March/018408.html
It seems U-Boot is behind !
I don't know what you are trying to demonstrate here but in the present case, I'll also submit a v2 of these patches on barebox'ML to factorize the code and the device tree.
Eric
PATCH v2 2/2 MarSBoard: add new board
In reply to Fabio EstevamHi Fabio,
Le Thu, 27 Mar 2014 09:44:02 -0300,
Fabio Estevam <[email protected]> a ?crit :
Quoted 4 lines
So in theory yes, we could have a single board file for all the mx6 boards out there and make it full of ifdefs all over it to handle all the hardware variations.
here we talk of 2 boards from the same manufacturer which are very similar. What Wolfgang asked is very relevant in that case.
Eric
PATCH v2 2/2 MarSBoard: add new board
Quoted 10 lines · Eric B?nard
Hi Fabio,
Le Thu, 27 Mar 2014 09:44:02 -0300,
Fabio Estevam <[email protected]> a ?crit :Quoted 4 lines
So in theory yes, we could have a single board file for all the mx6 boards out there and make it full of ifdefs all over it to handle all the hardware variations.
here we talk of 2 boards from the same manufacturer which are very similar. What Wolfgang asked is very relevant in that case.
Agreed now. I wasn't aware they were from the same manufacturer.
Regards,
Fabio Estevam
PATCH v2 2/2 MarSBoard: add new board
In reply to Fabio EstevamDear Fabio Estevam,
Quoted 4 lines · In message <CAOMZO5BF0e20eRs4keLH+jkGkQuTGn5Eci-W_9qTRnDBCdk9Dw@mail.gmail.com>…
So in theory yes, we could have a single board file for all the mx6 boards out there and make it full of ifdefs all over it to handle all the hardware variations.
Well, actually I do think there is some common code for iMX6 that could / should be factored out. And that does not even need any ifdefs.
Quoted 6 lines
Quoted 4 lines
Otherwise we would have to strictly split ARM and PowerPC code, and all other architectures. We would need code copies for each SoC. Actually each board would need his own version of the whole U-Boot code. Sorry, but this is just bizarre...
Looks like you are extrapolating too much here. Our discussion is only
Not more than you, just in the other direction ;-)
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Es ist nicht genug zu wissen, man mu? auch anwenden; es ist nicht ge- nug zu wollen, man mu? auch tun. -- Goethe, Maximen und Reflexionen
PATCH v2 2/2 MarSBoard: add new board
In reply to Otavio SalvadorDear Otavio,
Quoted 4 lines · In message <CAP9ODKrj9as+R7gb-STCnqpoSGFdKg_diJ=P+Vg6hTOka5dfMw@mail.gmail.com>…
I understand both boards share a lot of code but I think the set of ifdef makes harder for people to understand the board code. Personally I prefer v1.
Duplication of so much code is really bad. It's always been a maintenance nightmare. The new version is much better. [Of course there are also ways to avoid ifdefs, but there are not so many here, and they are actually pretty easy to follow.]
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Commitment, n.: Commitment can be illustrated by a breakfast of ham and eggs. The chicken was involved, the pig was committed.
PATCH v2 2/2 MarSBoard: add new board
In reply to Eric Bénardadding my 0.02$ to this discussion...
Quoted 72 lines · Eric B?nard
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR FlashBoot on SPI NOR and through USB loader are tested.
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.htmlAs this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards
Signed-off-by Eric B?nard <[email protected]>--- board/embest/{riotboard => mx6boards}/Makefile | 2 +- .../riotboard.c => mx6boards/mx6boards.c} | 49 +++++++++++++++++- boards.cfg | 3 +- include/configs/{riotboard.h => embestmx6boards.h} | 58 ++++++++++++++++++++++ 4 files changed, 108 insertions(+), 4 deletions(-)rename board/embest/{riotboard => mx6boards}/Makefile (87%) rename
board/embest/{riotboard/riotboard.c=>mx6boards/mx6boards.c} (91%) renameinclude/configs/{riotboard.h=>embestmx6boards.h} (84%)board/embest/mx6boards/Makefile renamed from board/embest/riotboard/Makefile +1
-1@@ -6,4 +6,4 @@ # SPDX-License-Identifier: GPL-2.0+ # -obj-y := riotboard.o +obj-y := mx6boards.oboard/embest/mx6boards/mx6boards.c renamed from board/embest/riotboard/riotboard.c +5
-0@@ -60,6 +60,9 @@ DECLARE_GLOBAL_DATA_PTR; PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm | PAD_CTL_HYS | \ PAD_CTL_ODE | PAD_CTL_SRE_FAST) +#define SPI_PAD_CTRL (PAD_CTL_HYS | PAD_CTL_SPEED_MED | \ + PAD_CTL_DSE_40ohm | PAD_CTL_SRE_FAST) +int dram_init (void ) { gd->ram_size =get_ram_size ((void *)PHYS_SDRAM ,PHYS_SDRAM_SIZE );@@ -153,8 +156,10 @@ iomux_v3_cfg_t const usdhc3_pads[] = {MX6_PAD_SD3_DAT1__SD3_DATA1 |MUX_PAD_CTRL (USDHC_PAD_CTRL ),MX6_PAD_SD3_DAT2__SD3_DATA2 |MUX_PAD_CTRL (USDHC_PAD_CTRL ),MX6_PAD_SD3_DAT3__SD3_DATA3 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +#ifdef CONFIG_RIOTBOARDMX6_PAD_SD3_DAT4__GPIO7_IO01 |MUX_PAD_CTRL (NO_PAD_CTRL ),/* WP */ MX6_PAD_SD3_DAT5__GPIO7_IO00 | MUX_PAD_CTRL(NO_PAD_CTRL), /* CD */ +#endif }; iomux_v3_cfg_t const usdhc4_pads[] = {
board/embest/mx6boards/mx6boards.c int board_mmc_getcd(struct mmc *mmc) · line 200
Quoted 9 lines
board/embest/mx6boards/mx6boards.c renamed from board/embest/riotboard/riotboard.c +5
-0@@ -187,7 +192,12 @@ int board_mmc_getcd(struct mmc *mmc) ret = !gpio_get_value (USDHC2_CD_GPIO );break ;case USDHC3_BASE_ADDR : +#ifdef CONFIG_RIOTBOARD ret = !gpio_get_value (USDHC3_CD_GPIO ); +#endif +#ifdef CONFIG_MARSBOARD + ret =1 ;/* eMMC/uSDHC3 is always present */ +#endif
Yes, I agree. #ifdef's are ugly. But code duplication is also a problem as Wolfgang has mentioned.
Isn't there a way to detect the board type at runtime somehow (via CPU type or GPIO input, ...)? And then dynamically configure the board either for "RiOT" or "MarS"? This would make the code a bit more complex of course. But there would be no #ifdef's and no code duplication. And you would only have to maintain one U-Boot binary / version for both boards.
So, what do you think? Is this possible?
Thanks,
Stefan
PATCH v2 2/2 MarSBoard: add new board
Hi Stefan,
Le Thu, 27 Mar 2014 08:05:10 +0100,
Stefan Roese <[email protected]> a ?crit :
Quoted 11 lines
Yes, I agree. #ifdef's are ugly. But code duplication is also a problem as Wolfgang has mentioned.
Isn't there a way to detect the board type at runtime somehow (via CPU type or GPIO input, ...)? And then dynamically configure the board either for "RiOT" or "MarS"? This would make the code a bit more complex of course. But there would be no #ifdef's and no code duplication. And you would only have to maintain one U-Boot binary / version for both boards.
So, what do you think? Is this possible?
Thanks for the idea, that's possible by detecting i.MX6Solo vs i.MX6Dual.
I'll try to implement that.
Eric
PATCH v3 1/2 RiOTboard: add new board
In reply to Stefan Roesethis board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
- UART2 (console)
- eMMC
- SDCard
- uSDCard
- Ethernet
- USB Host (through 4 ports hub)
- HDMI output
- I2C 1/2/3
Boot on eMMC and through USB loader are tested.
For more informations on this board : http://www.riotboard.org/
--- board/embest/riotboard/Makefile | 9 + board/embest/riotboard/riotboard.c | 493 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/riotboard.h | 299 ++++++++++++++++++++++ 4 files changed, 802 insertions(+) create mode 100644 board/embest/riotboard/Makefile create mode 100644 board/embest/riotboard/riotboard.c create mode 100644 include/configs/riotboard.h
board/embest/riotboard/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# +# Copyright (C) 2007, Guennadi Liakhovetski <[email protected]> +# +# (C) Copyright 2011 Freescale Semiconductor, Inc. +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y := riotboard.o
board/embest/riotboard/riotboard.c new file +493 -0
493 lines not on this page · raw message
boards.cfg +1 -0
@@ -323,6 +323,7 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> +Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/riotboard.h new file +299 -0
299 lines not on this page · raw message
Signature · 1 line
1.8.5.3
PATCH v3 2/2 MarSBoard: add new board
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR Flash
Boot on SPI NOR and through USB loader are tested.
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.html
As this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards.
---
v3: switch to automatic board detection in c code to remove the #ifdef
#ifdef kept in the config file as one binary for both boards is not possible actually since both boards use different RAM init.
board/embest/{riotboard => mx6boards}/Makefile | 2 +-
.../riotboard.c => mx6boards/mx6boards.c} | 83 ++++++++++++++++++++--
boards.cfg | 3 +-
include/configs/{riotboard.h => embestmx6boards.h} | 58 +++++++++++++++
4 files changed, 137 insertions(+), 9 deletions(-)
rename board/embest/{riotboard => mx6boards}/Makefile (87%)
rename board/embest/{riotboard/riotboard.c => mx6boards/mx6boards.c} (86%)
rename include/configs/{riotboard.h => embestmx6boards.h} (84%)board/embest/mx6boards/Makefile renamed from board/embest/riotboard/Makefile +1 -1
@@ -6,4 +6,4 @@ # SPDX-License-Identifier: GPL-2.0+ # -obj-y := riotboard.o +obj-y := mx6boards.o
board/embest/mx6boards/mx6boards.c renamed from board/embest/riotboard/riotboard.c +76 -7
164 lines not on this page · raw message
boards.cfg +2 -1
@@ -323,7 +323,8 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> -Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> +Active arm armv7 mx6 embest mx6boards riotboard embestmx6boards:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024,RIOTBOARD Eric B?nard <[email protected]> +Active arm armv7 mx6 embest mx6boards marsboard embestmx6boards:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6q.cfg,MX6Q,DDR_MB=1024,MARSBOARD Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/embestmx6boards.h renamed from include/configs/riotboard.h +58 -0
103 lines not on this page · raw message
Signature · 1 line
1.8.5.3
PATCH v3 2/2 MarSBoard: add new board
Quoted 13 lines · Eric B?nard
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR FlashBoot on SPI NOR and through USB loader are tested.
Quoted 7 lines
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.htmlAs this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards.
Signed-off-by Eric B?nard <[email protected]>
Looks much better this way for my taste. Thanks for working on this.
Thanks,
Stefan
PATCH v3 2/2 MarSBoard: add new board
In reply to Eric BénardDear Eric B?nard,
Quoted 2 lines · In message <[email protected]> you wrote:
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
...
Quoted 2 lines
As this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards.
This looks much better than the original code Thanks a lot!
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "If a computer can't directly address all the RAM you can use, it's just a toy." - anonymous comp.sys.amiga posting, non-sequitir
PATCH v3 1/2 RiOTboard: add new board
In reply to Eric BénardDear Eric B?nard,
Quoted 2 lines · In message <[email protected]> you wrote:
this board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
....
You might use the clrbits / setbits / clrsetbits I/O accesses here:
board/embest/riotboard/riotboard.c line 390
Quoted 4 lines
board/embest/riotboard/riotboard.c new file +4
-0+/* Turn on LDB0, LDB1, IPU,IPU DI0 clocks */ + reg =readl (&mxc_ccm->CCGR3); + reg |=MXC_CCM_CCGR3_LDB_DI0_MASK |MXC_CCM_CCGR3_LDB_DI1_MASK ; +writel (reg, &mxc_ccm->CCGR3);
setbits_le32(&mxc_ccm->CCGR3, MXC_CCM_CCGR3_LDB_DI0_MASK | MXC_CCM_CCGR3_LDB_DI1_MASK);
?
board/embest/riotboard/riotboard.c line 398
Quoted 7 lines
board/embest/riotboard/riotboard.c new file +7
-0+/* set LDB0, LDB1 clk select to 011/011 */ + reg =readl (&mxc_ccm->cs2cdr); + reg &= ~(MXC_CCM_CS2CDR_LDB_DI0_CLK_SEL_MASK + |MXC_CCM_CS2CDR_LDB_DI1_CLK_SEL_MASK ); + reg |= (3 <<MXC_CCM_CS2CDR_LDB_DI0_CLK_SEL_OFFSET ) + | (3 <<MXC_CCM_CS2CDR_LDB_DI1_CLK_SEL_OFFSET ); +writel (reg, &mxc_ccm->cs2cdr);
clrsetbits_le32(&mxc_ccm->cs2cdr, MXC_CCM_CS2CDR_LDB_DI0_CLK_SEL_MASK | MXC_CCM_CS2CDR_LDB_DI1_CLK_SEL_MASK, (3 << MXC_CCM_CS2CDR_LDB_DI0_CLK_SEL_OFFSET) | (3 << MXC_CCM_CS2CDR_LDB_DI1_CLK_SEL_OFFSET));
?
board/embest/riotboard/riotboard.c line 402
Quoted 3 lines
board/embest/riotboard/riotboard.c new file +3
-0+ reg =readl (&mxc_ccm->cscmr2); + reg |=MXC_CCM_CSCMR2_LDB_DI0_IPU_DIV |MXC_CCM_CSCMR2_LDB_DI1_IPU_DIV ; +writel (reg, &mxc_ccm->cscmr2);
etc.
Quoted 1 line
+#define
CONFIG_ARP_TIMEOUT200UL
Do you need this on your boards?
Best regards,
Wolfgang Denk
Signature · 5 lines
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de "Unibus timeout fatal trap program lost sorry" - An error message printed by DEC's RSTS operating system for the PDP-11
PATCH v4 1/2 RiOTboard: add new board
this board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
- UART2 (console)
- eMMC
- SDCard
- uSDCard
- Ethernet
- USB Host (through 4 ports hub)
- HDMI output
- I2C 1/2/3
- LVDS TFT with LCD8000-97C from Embest/Element 14
Boot on eMMC and through USB loader are tested.
For more informations on this board : http://www.riotboard.org/
---
v4: add LVDS TFT support and use clrbits / setbits / clrsetbits as
suggested by Wolfgang
board/embest/riotboard/Makefile | 9 + board/embest/riotboard/riotboard.c | 566 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/riotboard.h | 299 ++++++++++++++++++++ 4 files changed, 875 insertions(+) create mode 100644 board/embest/riotboard/Makefile create mode 100644 board/embest/riotboard/riotboard.c create mode 100644 include/configs/riotboard.h
board/embest/riotboard/Makefile new file +9 -0
@@ -0,0 +1,9 @@ +# +# Copyright (C) 2007, Guennadi Liakhovetski <[email protected]> +# +# (C) Copyright 2011 Freescale Semiconductor, Inc. +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y := riotboard.o
board/embest/riotboard/riotboard.c new file +566 -0
566 lines not on this page · raw message
boards.cfg +1 -0
@@ -323,6 +323,7 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> +Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/riotboard.h new file +299 -0
299 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 2/2 MarSBoard: add new board
this board is produced by Embest/Element 14 and is based on i.MX6 Dual The following features are tested :
- UART2 (console)
- eMMC
- uSDCard
- Ethernet
- USB Host (through 2 ports hub)
- HDMI output
- I2C 1/2
- SPI NOR Flash
- LVDS TFT with LCD8000-97C from Embest/Element 14
Boot on SPI NOR and through USB loader are tested.
For more informations on this board :
http://www.embest-tech.com/shop/star/marsboard.html
As this board shares a lot with RiOTboard, both boards are supported by the same code base which is renamed embest/mx6boards.
---
v4: add LVDS TFT support
v3: switch to automatic board detection in c code to remove the #ifdef
#ifdef kept in the config file as one binary for both boards is not possible actually since both boards use different RAM init.
board/embest/{riotboard => mx6boards}/Makefile | 2 +-
.../riotboard.c => mx6boards/mx6boards.c} | 118 ++++++++++++++++++---
boards.cfg | 3 +-
include/configs/{riotboard.h => embestmx6boards.h} | 58 ++++++++++
4 files changed, 166 insertions(+), 15 deletions(-)
rename board/embest/{riotboard => mx6boards}/Makefile (87%)
rename board/embest/{riotboard/riotboard.c => mx6boards/mx6boards.c} (81%)
rename include/configs/{riotboard.h => embestmx6boards.h} (84%)board/embest/mx6boards/Makefile renamed from board/embest/riotboard/Makefile +1 -1
@@ -6,4 +6,4 @@ # SPDX-License-Identifier: GPL-2.0+ # -obj-y := riotboard.o +obj-y := mx6boards.o
board/embest/mx6boards/mx6boards.c renamed from board/embest/riotboard/riotboard.c +105 -13
231 lines not on this page · raw message
boards.cfg +2 -1
@@ -323,7 +323,8 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> -Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> +Active arm armv7 mx6 embest mx6boards riotboard embestmx6boards:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024,RIOTBOARD Eric B?nard <[email protected]> +Active arm armv7 mx6 embest mx6boards marsboard embestmx6boards:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6q.cfg,MX6Q,DDR_MB=1024,MARSBOARD Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>
include/configs/embestmx6boards.h renamed from include/configs/riotboard.h +58 -0
103 lines not on this page · raw message
Signature · 1 line
1.9.0
PATCH v4 1/2 RiOTboard: add new board
In reply to Eric BénardHi Eric,
I jump directly to V4 ;-) Sorry for late review, I was not in office last days.
Added Ben in CC. He sent a first version for the Marsboard.
Quoted 12 lines · Eric B?nard
this board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
- UART2 (console)
- eMMC
- SDCard
- uSDCard
- Ethernet
- USB Host (through 4 ports hub)
- HDMI output
- I2C 1/2/3
- LVDS TFT with LCD8000-97C from Embest/Element 14
Quoted 6 lines
Boot on eMMC and through USB loader are tested.
For more informations on this board : http://www.riotboard.org/
Signed-off-by Eric B?nard <[email protected]>---
A general remark. I agree by reading the whole thread about checking at runtime which is the running board (you do it getting the cpu type).
However, you use also a compiler switch mechanism, adding RIOTBOARD or MARSBOARD in the boards.cfg. You have implemented two ways to for the same thing. This makes in principle your runtime detection useless, because you can use #if CONFIG_MARSBOARD instead of "if board_type == BOARD_IS_MARSBOARD)". Is it possible to use only the runtime detection ? I think the main problem is CONFIG_ENV_IS_*, that is different for the two boards. What do you think about it ?
IMHO you could also squash the two patches together. You add new files, and patch 2/2 changes some of them. I think in this case having a single patch makes review easier.
Quoted 140 lines
v4: add LVDS TFT support and use clrbits / setbits / clrsetbits as
suggested by Wolfgangboard/embest/riotboard/Makefile | 9 + board/embest/riotboard/riotboard.c | 566 +++++++++++++++++++++++++++++++++++++ boards.cfg | 1 + include/configs/riotboard.h | 299 ++++++++++++++++++++ 4 files changed, 875 insertions(+) create mode 100644 board/embest/riotboard/Makefile create mode 100644 board/embest/riotboard/riotboard.c create mode 100644 include/configs/riotboard.hboard/embest/riotboard/Makefile new file +9
-0@@ -0,0 +1,9 @@ +# +# Copyright (C) 2007, Guennadi Liakhovetski <[email protected]> +# +# (C) Copyright 2011 Freescale Semiconductor, Inc. +# +# SPDX-License-Identifier: GPL-2.0+ +# + +obj-y := riotboard.oboard/embest/riotboard/riotboard.c new file +107
-0@@ -0,0 +1,566 @@ +/* +* Copyright (C) 2014 Eukr?a Electromatique +* Author: Eric B?nard <[email protected]> +* Fabio Estevam <[email protected]> +* Jon Nettleton <[email protected]> +* +* based on sabresd.c which is : +* Copyright (C) 2012 Freescale Semiconductor, Inc. +* and on hummingboard.c which is : +* Copyright (C) 2013 SolidRun ltd. +* Copyright (C) 2013 Jon Nettleton <[email protected]>. +* +* SPDX-License-Identifier: GPL-2.0+ +*/ + +#include <asm/arch/clock.h> +#include <asm/arch/imx-regs.h> +#include <asm/arch/iomux.h> +#include <asm/arch/mx6-pins.h> +#include <asm/errno.h> +#include <asm/gpio.h> +#include <asm/imx-common/iomux-v3.h> +#include <asm/imx-common/boot_mode.h> +#include <asm/imx-common/mxc_i2c.h> +#include <i2c.h> +#include <mmc.h> +#include <fsl_esdhc.h> +#include <miiphy.h> +#include <netdev.h> +#include <asm/arch/mxc_hdmi.h> +#include <asm/arch/crm_regs.h> +#include <linux/fb.h> +#include <ipu_pixfmt.h> +#include <asm/io.h> +#include <asm/arch/sys_proto.h> +DECLARE_GLOBAL_DATA_PTR ; + +#define UART_PAD_CTRL (PAD_CTL_PUS_100K_UP | \ + PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm | \ + PAD_CTL_SRE_FAST | PAD_CTL_HYS) + +#define USDHC_PAD_CTRL (PAD_CTL_PUS_47K_UP | \ + PAD_CTL_SPEED_LOW | PAD_CTL_DSE_80ohm | \ + PAD_CTL_SRE_FAST | PAD_CTL_HYS) + +#define USDHC_PAD_CLK_CTRL (PAD_CTL_SPEED_LOW | \ + PAD_CTL_DSE_80ohm | PAD_CTL_SRE_FAST | \ + PAD_CTL_HYS) + +#define ENET_PAD_CTRL (PAD_CTL_PUS_100K_UP | \ + PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm | PAD_CTL_HYS) + +#define ENET_PAD_CTRL_PD (PAD_CTL_PUS_100K_DOWN | \ + PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm | PAD_CTL_HYS) + +#define ENET_PAD_CTRL_CLK ((PAD_CTL_PUS_100K_UP & ~PAD_CTL_PKE) | \ + PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm | PAD_CTL_SRE_FAST) + +#define I2C_PAD_CTRL (PAD_CTL_PUS_100K_UP | \ + PAD_CTL_SPEED_MED | PAD_CTL_DSE_40ohm | PAD_CTL_HYS | \ + PAD_CTL_ODE | PAD_CTL_SRE_FAST) + +int dram_init (void ) +{ + gd->ram_size =get_ram_size ((void *)PHYS_SDRAM ,PHYS_SDRAM_SIZE ); + +return 0 ; +} + +static iomux_v3_cfg_t const uart2_pads[] = { +MX6_PAD_EIM_D26__UART2_TX_DATA |MUX_PAD_CTRL (UART_PAD_CTRL ), +MX6_PAD_EIM_D27__UART2_RX_DATA |MUX_PAD_CTRL (UART_PAD_CTRL ), +}; + +static void setup_iomux_uart (void ) +{ +imx_iomux_v3_setup_multiple_pads (uart2_pads,ARRAY_SIZE (uart2_pads)); +} + +iomux_v3_cfg_t const enet_pads[] = { +MX6_PAD_ENET_MDIO__ENET_MDIO |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_ENET_MDC__ENET_MDC |MUX_PAD_CTRL (ENET_PAD_CTRL ), +/* GPIO16 -> AR8035 25MHz */ +MX6_PAD_GPIO_16__ENET_REF_CLK |MUX_PAD_CTRL (NO_PAD_CTRL ), +MX6_PAD_RGMII_TXC__RGMII_TXC |MUX_PAD_CTRL (NO_PAD_CTRL ), +MX6_PAD_RGMII_TD0__RGMII_TD0 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_TD1__RGMII_TD1 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_TD2__RGMII_TD2 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_TD3__RGMII_TD3 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_TX_CTL__RGMII_TX_CTL |MUX_PAD_CTRL (ENET_PAD_CTRL ), +/* AR8035 CLK_25M --> ENET_REF_CLK (V22) */ +MX6_PAD_ENET_REF_CLK__ENET_TX_CLK |MUX_PAD_CTRL (ENET_PAD_CTRL_CLK ), +MX6_PAD_RGMII_RXC__RGMII_RXC |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_RD0__RGMII_RD0 |MUX_PAD_CTRL (ENET_PAD_CTRL_PD ), +MX6_PAD_RGMII_RD1__RGMII_RD1 |MUX_PAD_CTRL (ENET_PAD_CTRL_PD ), +MX6_PAD_RGMII_RD2__RGMII_RD2 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_RD3__RGMII_RD3 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +MX6_PAD_RGMII_RX_CTL__RGMII_RX_CTL |MUX_PAD_CTRL (ENET_PAD_CTRL_PD ), +/* AR8035 PHY Reset */ +MX6_PAD_EIM_D31__GPIO3_IO31 |MUX_PAD_CTRL (ENET_PAD_CTRL_PD ), +/* AR8035 PHY Interrupt */ +MX6_PAD_ENET_TX_EN__GPIO1_IO28 |MUX_PAD_CTRL (ENET_PAD_CTRL ), +}; + +static void setup_iomux_enet (void ) +{ +imx_iomux_v3_setup_multiple_pads (enet_pads,ARRAY_SIZE (enet_pads));
board/embest/riotboard/riotboard.c line 117
Quoted 10 lines
board/embest/riotboard/riotboard.c new file +10
-0+ +/* Reset AR8035 PHY */ +gpio_direction_output (IMX_GPIO_NR (3 ,31 ) ,0 ); +mdelay (2 ); +gpio_set_value (IMX_GPIO_NR (3 ,31 ),1 ); +} + +int mx6_rgmii_rework (struct phy_device *phydev) +{ +/* from linux/arch/arm/mach-imx/mach-imx6q.c :
Codestyle in U-Boot for multiline comments is:
/*
* ...
*/
Quoted 318 lines
board/embest/riotboard/riotboard.c new file +318
-0+* Ar803x phy SmartEEE feature cause link status generates glitch, +* which cause ethernet link down/up issue, so disable SmartEEE +*/ +phy_write (phydev,MDIO_DEVAD_NONE ,0xd ,0x7 ); +phy_write (phydev,MDIO_DEVAD_NONE ,0xe ,0x805d ); +phy_write (phydev,MDIO_DEVAD_NONE ,0xd ,0x4003 ); + +return 0 ; +} + +int board_phy_config (struct phy_device *phydev) +{ +mx6_rgmii_rework (phydev); + +if (phydev->drv->config) + phydev->drv->config (phydev); + +return 0 ; +} + +iomux_v3_cfg_t const usdhc2_pads[] = { +MX6_PAD_SD2_CLK__SD2_CLK |MUX_PAD_CTRL (USDHC_PAD_CLK_CTRL ), +MX6_PAD_SD2_CMD__SD2_CMD |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD2_DAT0__SD2_DATA0 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD2_DAT1__SD2_DATA1 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD2_DAT2__SD2_DATA2 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD2_DAT3__SD2_DATA3 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_GPIO_2__GPIO1_IO02 |MUX_PAD_CTRL (NO_PAD_CTRL ),/* WP */ +MX6_PAD_GPIO_4__GPIO1_IO04 |MUX_PAD_CTRL (NO_PAD_CTRL ),/* CD */ +}; + +iomux_v3_cfg_t const usdhc3_pads[] = { +MX6_PAD_SD3_CLK__SD3_CLK |MUX_PAD_CTRL (USDHC_PAD_CLK_CTRL ), +MX6_PAD_SD3_CMD__SD3_CMD |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD3_DAT0__SD3_DATA0 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD3_DAT1__SD3_DATA1 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD3_DAT2__SD3_DATA2 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD3_DAT3__SD3_DATA3 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD3_DAT4__GPIO7_IO01 |MUX_PAD_CTRL (NO_PAD_CTRL ),/* WP */ +MX6_PAD_SD3_DAT5__GPIO7_IO00 |MUX_PAD_CTRL (NO_PAD_CTRL ),/* CD */ +}; + +iomux_v3_cfg_t const usdhc4_pads[] = { +MX6_PAD_SD4_CLK__SD4_CLK |MUX_PAD_CTRL (USDHC_PAD_CLK_CTRL ), +MX6_PAD_SD4_CMD__SD4_CMD |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD4_DAT0__SD4_DATA0 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD4_DAT1__SD4_DATA1 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD4_DAT2__SD4_DATA2 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +MX6_PAD_SD4_DAT3__SD4_DATA3 |MUX_PAD_CTRL (USDHC_PAD_CTRL ), +/* eMMC RST */ +MX6_PAD_NANDF_ALE__GPIO6_IO08 |MUX_PAD_CTRL (NO_PAD_CTRL ), +}; + +#ifdef CONFIG_FSL_ESDHC +struct fsl_esdhc_cfg usdhc_cfg[3 ] = { + {USDHC2_BASE_ADDR }, + {USDHC3_BASE_ADDR }, + {USDHC4_BASE_ADDR }, +}; + +#define USDHC2_CD_GPIO IMX_GPIO_NR(1, 4) +#define USDHC3_CD_GPIO IMX_GPIO_NR(7, 0) + +int board_mmc_getcd (struct mmc *mmc) +{ +struct fsl_esdhc_cfg *cfg = (struct fsl_esdhc_cfg *)mmc->priv; +int ret =0 ; + +switch (cfg->esdhc_base) { +case USDHC2_BASE_ADDR : + ret = !gpio_get_value (USDHC2_CD_GPIO ); +break ; +case USDHC3_BASE_ADDR : + ret = !gpio_get_value (USDHC3_CD_GPIO ); +break ; +case USDHC4_BASE_ADDR : + ret =1 ;/* eMMC/uSDHC4 is always present */ +break ; + } + +return ret; +} + +int board_mmc_init (bd_t *bis) +{ +s32 status =0 ; +int i; + +/* +* According to the board_mmc_init() the following map is done: +* (U-boot device node) (Physical Port) +* mmc0 SDCard slot (bottom) +* mmc1 uSDCard slot (top) +* mmc2 eMMC +*/ +for (i =0 ; i <CONFIG_SYS_FSL_USDHC_NUM ; i++) { +switch (i) { +case 0 : +imx_iomux_v3_setup_multiple_pads ( + usdhc2_pads,ARRAY_SIZE (usdhc2_pads)); +gpio_direction_input (USDHC2_CD_GPIO ); + usdhc_cfg[0 ].sdhc_clk =mxc_get_clock (MXC_ESDHC2_CLK ); + usdhc_cfg[0 ].max_bus_width =4 ; +break ; +case 1 : +imx_iomux_v3_setup_multiple_pads ( + usdhc3_pads,ARRAY_SIZE (usdhc3_pads)); +gpio_direction_input (USDHC3_CD_GPIO ); + usdhc_cfg[1 ].sdhc_clk =mxc_get_clock (MXC_ESDHC3_CLK ); + usdhc_cfg[1 ].max_bus_width =4 ; +break ; +case 2 : +imx_iomux_v3_setup_multiple_pads ( + usdhc4_pads,ARRAY_SIZE (usdhc4_pads)); + usdhc_cfg[2 ].sdhc_clk =mxc_get_clock (MXC_ESDHC4_CLK ); + usdhc_cfg[2 ].max_bus_width =4 ; +gpio_direction_output (IMX_GPIO_NR (6 ,8 ) ,0 ); +udelay (250 ); +gpio_set_value (IMX_GPIO_NR (6 ,8 ),1 ); +break ; +default : +printf ("Warning: you configured more USDHC controllers" +"(%d) then supported by the board (%d)\n" , + i +1 ,CONFIG_SYS_FSL_USDHC_NUM ); +return status; + } + + status |=fsl_esdhc_initialize (bis, &usdhc_cfg[i]); + } + +return status; +} +#endif + +struct i2c_pads_info i2c_pad_info1 = { + .scl = { + .i2c_mode =MX6_PAD_CSI0_DAT9__I2C1_SCL + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gpio_mode =MX6_PAD_CSI0_DAT9__GPIO5_IO27 + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gp =IMX_GPIO_NR (5 ,27 ) + }, + .sda = { + .i2c_mode =MX6_PAD_CSI0_DAT8__I2C1_SDA + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gpio_mode =MX6_PAD_CSI0_DAT8__GPIO5_IO26 + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gp =IMX_GPIO_NR (5 ,26 ) + } +}; + +struct i2c_pads_info i2c_pad_info2 = { + .scl = { + .i2c_mode =MX6_PAD_KEY_COL3__I2C2_SCL + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gpio_mode =MX6_PAD_KEY_COL3__GPIO4_IO12 + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gp =IMX_GPIO_NR (4 ,12 ) + }, + .sda = { + .i2c_mode =MX6_PAD_KEY_ROW3__I2C2_SDA + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gpio_mode =MX6_PAD_KEY_ROW3__GPIO4_IO13 + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gp =IMX_GPIO_NR (4 ,13 ) + } +}; + +struct i2c_pads_info i2c_pad_info3 = { + .scl = { + .i2c_mode =MX6_PAD_GPIO_5__I2C3_SCL + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gpio_mode =MX6_PAD_GPIO_5__GPIO1_IO05 + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gp =IMX_GPIO_NR (1 ,5 ) + }, + .sda = { + .i2c_mode =MX6_PAD_GPIO_6__I2C3_SDA + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gpio_mode =MX6_PAD_GPIO_6__GPIO1_IO06 + |MUX_PAD_CTRL (I2C_PAD_CTRL ), + .gp =IMX_GPIO_NR (1 ,6 ) + } +}; + +iomux_v3_cfg_t const tft_pads[] = { +/* LCD_PWR_EN */ +MX6_PAD_ENET_TXD1__GPIO1_IO29 |MUX_PAD_CTRL (NO_PAD_CTRL ), +/* TOUCH_INT */ +MX6_PAD_NANDF_CS1__GPIO6_IO14 |MUX_PAD_CTRL (NO_PAD_CTRL ), +/* LED_PWR_EN */ +MX6_PAD_NANDF_CS2__GPIO6_IO15 |MUX_PAD_CTRL (NO_PAD_CTRL ), +/* BL LEVEL */ +MX6_PAD_SD1_CMD__GPIO1_IO18 |MUX_PAD_CTRL (NO_PAD_CTRL ), +}; + +#if defined(CONFIG_VIDEO_IPUV3 ) +struct display_info_t { +int bus; +int addr; +int pixfmt; +int (*detect)(struct display_info_t const *dev); +void (*enable)(struct display_info_t const *dev); +struct fb_videomode mode; +}; + +static void enable_lvds (struct display_info_t const *dev) +{ +struct iomuxc *iomux = (struct iomuxc *) +IOMUXC_BASE_ADDR ; +setbits_le32 (&iomux->gpr[2 ], +IOMUXC_GPR2_DATA_WIDTH_CH0_24BIT ); +/* set backlight level to ON */ +gpio_direction_output (IMX_GPIO_NR (1 ,18 ) ,1 ); +} + +static void disable_lvds (struct display_info_t const *dev) +{ +struct iomuxc *iomux = (struct iomuxc *)IOMUXC_BASE_ADDR ; + +/* set backlight level to OFF */ +gpio_direction_output (IMX_GPIO_NR (1 ,18 ) ,0 ); + +clrbits_le32 (&iomux->gpr[2 ], +IOMUXC_GPR2_LVDS_CH0_MODE_MASK ); +} + +static int detect_hdmi (struct display_info_t const *dev) +{ +struct hdmi_regs *hdmi = (struct hdmi_regs *)HDMI_ARB_BASE_ADDR ; +return readb (&hdmi->phy_stat0) &HDMI_DVI_STAT ; +} + +static void do_enable_hdmi (struct display_info_t const *dev) +{ +disable_lvds (dev); +imx_enable_hdmi_phy (); +} + +static int detect_i2c (struct display_info_t const *dev) +{ +return (0 ==i2c_set_bus_num (dev->bus)) && + (0 ==i2c_probe (dev->addr)); +} + +static struct display_info_t const displays[] = {{ + .bus =-1 , + .addr =0 , + .pixfmt =IPU_PIX_FMT_RGB24 , + .detect = detect_hdmi, + .enable = do_enable_hdmi, + .mode = { + .name ="HDMI" , + .refresh =60 , + .xres =1024 , + .yres =768 , + .pixclock =15385 , + .left_margin =220 , + .right_margin =40 , + .upper_margin =21 , + .lower_margin =7 , + .hsync_len =60 , + .vsync_len =10 , + .sync =FB_SYNC_EXT , + .vmode =FB_VMODE_NONINTERLACED +} }, { + .bus =2 , + .addr =0x1 , + .pixfmt =IPU_PIX_FMT_LVDS666 , + .detect = detect_i2c, + .enable = enable_lvds, + .mode = { + .name ="LCD8000-97C" , + .refresh =60 , + .xres =1024 , + .yres =768 , + .pixclock =15385 , + .left_margin =100 , + .right_margin =200 , + .upper_margin =10 , + .lower_margin =20 , + .hsync_len =20 , + .vsync_len =8 , + .sync =FB_SYNC_EXT , + .vmode =FB_VMODE_NONINTERLACED +} } }; + +int board_video_skip (void ) +{ +int i; +int ret; +char const *panel =getenv ("panel" ); +if (!panel) { +for (i =0 ; i <ARRAY_SIZE (displays); i++) { +struct display_info_t const *dev = displays+i; +if (dev->detect && dev->detect (dev)) { + panel = dev->mode.name; +printf ("auto-detected panel %s\n" , panel); +break ; + } + } +if (!panel) { + panel = displays[0 ].mode.name; +printf ("No panel detected: default to %s\n" , panel); + i =0 ; + } + }else { +for (i =0 ; i <ARRAY_SIZE (displays); i++) { +if (!strcmp (panel, displays[i].mode.name)) +break ; + } + } +if (i <ARRAY_SIZE (displays)) { + ret =ipuv3_fb_init (&displays[i].mode,0 , + displays[i].pixfmt); +if (!ret) { + displays[i].enable (displays+i); + printf("Display: %s (%ux%u)\n",
board/embest/riotboard/riotboard.c line 445
Quoted 10 lines
board/embest/riotboard/riotboard.c new file +10
-0+ displays[i].mode.name, + displays[i].mode.xres, + displays[i].mode.yres); + }else +printf ("LCD %s cannot be configured: %d\n" , + displays[i].mode.name, ret); + }else { +printf ("unsupported panel %s\n" , panel); +return -EINVAL ; + }
We have already discussed in the past about this function. Each board (at least, imx6 board) want to have such of them, and code is duplicated. What about to factorize it ? I am not against to move it into imx-common, if we generally agree, but I would like to avoid to duplicate this function for each board.
Quoted 429 lines
board/embest/riotboard/riotboard.c new file +121
-0+ +return 0 ; +} + +static void setup_display (void ) +{ +struct mxc_ccm_reg *mxc_ccm = (struct mxc_ccm_reg *)CCM_BASE_ADDR ; +struct iomuxc *iomux = (struct iomuxc *)IOMUXC_BASE_ADDR ; +int reg; + +enable_ipu_clock (); +imx_setup_hdmi (); + +/* Turn on LDB0, IPU,IPU DI0 clocks */ +setbits_le32 (&mxc_ccm->CCGR3, +MXC_CCM_CCGR3_LDB_DI0_MASK ); + +/* set LDB0 clk select to 011/011 */ +clrsetbits_le32 (&mxc_ccm->cs2cdr, +MXC_CCM_CS2CDR_LDB_DI0_CLK_SEL_MASK , + (3 <<MXC_CCM_CS2CDR_LDB_DI0_CLK_SEL_OFFSET )); + +setbits_le32 (&mxc_ccm->cscmr2, +MXC_CCM_CSCMR2_LDB_DI0_IPU_DIV ); + +setbits_le32 (&mxc_ccm->chsccdr, + (CHSCCDR_CLK_SEL_LDB_DI0 + <<MXC_CCM_CHSCCDR_IPU1_DI0_CLK_SEL_OFFSET )); + + reg =IOMUXC_GPR2_BGREF_RRMODE_EXTERNAL_RES + |IOMUXC_GPR2_DI0_VS_POLARITY_ACTIVE_LOW + |IOMUXC_GPR2_BIT_MAPPING_CH1_SPWG + |IOMUXC_GPR2_DATA_WIDTH_CH1_18BIT + |IOMUXC_GPR2_BIT_MAPPING_CH0_SPWG + |IOMUXC_GPR2_DATA_WIDTH_CH0_18BIT + |IOMUXC_GPR2_LVDS_CH1_MODE_DISABLED + |IOMUXC_GPR2_LVDS_CH0_MODE_ENABLED_DI0 ; +writel (reg, &iomux->gpr[2 ]); + +clrsetbits_le32 (&iomux->gpr[3 ], +IOMUXC_GPR3_LVDS0_MUX_CTL_MASK | +IOMUXC_GPR3_HDMI_MUX_CTL_MASK , +IOMUXC_GPR3_MUX_SRC_IPU1_DI0 + <<IOMUXC_GPR3_LVDS0_MUX_CTL_OFFSET ); +} +#endif /* CONFIG_VIDEO_IPUV3 */ + +/* +* Do not overwrite the console +* Use always serial for U-Boot console +*/ +int overwrite_console (void ) +{ +return 1 ; +} + +int board_eth_init (bd_t *bis) +{ +setup_iomux_enet (); + +return cpu_eth_init (bis); +} + +int board_early_init_f (void ) +{ +setup_iomux_uart (); + +imx_iomux_v3_setup_multiple_pads ( + tft_pads,ARRAY_SIZE (tft_pads)); +#if defined(CONFIG_VIDEO_IPUV3 ) +/* power ON LCD */ +gpio_direction_output (IMX_GPIO_NR (1 ,29 ) ,1 ); +/* touch interrupt is an input */ +gpio_direction_input (IMX_GPIO_NR (6 ,14 )); +/* power ON backlight */ +gpio_direction_output (IMX_GPIO_NR (6 ,15 ) ,1 ); +/* set backlight level to off */ +gpio_direction_output (IMX_GPIO_NR (1 ,18 ) ,0 ); +setup_display (); +#endif + +return 0 ; +} + +int board_init (void ) +{ +/* address of boot parameters */ + gd->bd->bi_boot_params =PHYS_SDRAM +0x100 ; +/* i2c1 : PMIC, Audio codec */ +setup_i2c (0 ,CONFIG_SYS_I2C_SPEED ,0x7f , &i2c_pad_info1); +/* i2c2 : HDMI EDID */ +setup_i2c (1 ,CONFIG_SYS_I2C_SPEED ,0x7f , &i2c_pad_info2); +/* i2c3 : LVDS, Expansion connector */ +setup_i2c (2 ,CONFIG_SYS_I2C_SPEED ,0x7f , &i2c_pad_info3); + +return 0 ; +} + +#ifdef CONFIG_CMD_BMODE +static const struct boot_mode board_boot_modes[] = { + {"sd2" ,MAKE_CFGVAL (0x40 ,0x28 ,0x00 ,0x00 )}, + {"sd3" ,MAKE_CFGVAL (0x40 ,0x30 ,0x00 ,0x00 )}, + {"emmc" ,MAKE_CFGVAL (0x40 ,0x38 ,0x00 ,0x00 )}, + {NULL ,0 }, +}; +#endif + +int board_late_init (void ) +{ +#ifdef CONFIG_CMD_BMODE +add_board_boot_modes (board_boot_modes); +#endif + +return 0 ; +} + +int checkboard (void ) +{ +puts ("Board: RIoTboard\n" ); +return 0 ; +}boards.cfg +1
-0@@ -323,6 +323,7 @@ Active arm armv7 mx6 freescale mx6sabresd Active arm armv7 mx6 freescale mx6sabresd mx6qsabresd mx6sabresd:IMX_CONFIG=board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg,MX6Q Fabio Estevam <[email protected]> Active arm armv7 mx6 freescale mx6slevk mx6slevk mx6slevk:IMX_CONFIG=board/freescale/mx6slevk/imximage.cfg,MX6SL Fabio Estevam <[email protected]> Active arm armv7 mx6 solidrun hummingboard hummingboard_solo hummingboard:IMX_CONFIG=board/solidrun/hummingboard/solo.cfg,MX6S,DDR_MB=512 Jon Nettleton <[email protected]> +Active arm armv7 mx6 embest riotboard riotboard riotboard:IMX_CONFIG=board/boundary/nitrogen6x/nitrogen6s1g.cfg,MX6S,DDR_MB=1024 Eric B?nard <[email protected]> Active arm armv7 omap3 - overo omap3_overo - Steve Sakoman <[email protected]> Active arm armv7 omap3 - pandora omap3_pandora - Grazvydas Ignotas <[email protected]> Active arm armv7 omap3 8dtech eco5pk eco5pk - Raphael Assenat <[email protected]>include/configs/riotboard.h new file +289
-0@@ -0,0 +1,299 @@ +/* +* Copyright (C) 2014 Eukr?a Electromatique +* Author: Eric B?nard <[email protected]> +* +* Configuration settings for the Embest RIoTboard +* +* based on mx6*sabre*.h which are : +* Copyright (C) 2012 Freescale Semiconductor, Inc. +* +* SPDX-License-Identifier: GPL-2.0+ +*/ + +#ifndef __RIOTBOARD_CONFIG_H +#define __RIOTBOARD_CONFIG_H + +#include <asm/arch/imx-regs.h> +#include <asm/imx-common/gpio.h> + +#include "mx6_common.h" +#include <linux/sizes.h> + +#define CONFIG_MXC_UART_BASE UART2_BASE +#define CONFIG_CONSOLE_DEV "ttymxc0" +#define CONFIG_MMCROOT "/dev/mmcblk1p2" +#define CONFIG_DEFAULT_FDT_FILE "imx6s-riotboard.dtb" +#define PHYS_SDRAM_SIZE (1u * 1024 * 1024 * 1024) + +#define CONFIG_SUPPORT_EMMC_BOOT /* eMMC specific */ + +#define CONFIG_MX6 + +#define CONFIG_DISPLAY_CPUINFO +#define CONFIG_DISPLAY_BOARDINFO + +#define CONFIG_CMDLINE_TAG +#define CONFIG_SETUP_MEMORY_TAGS +#define CONFIG_INITRD_TAG +#define CONFIG_REVISION_TAG + +/* Size of malloc() pool */ +#define CONFIG_SYS_MALLOC_LEN (10 * SZ_1M) + +#define CONFIG_BOARD_EARLY_INIT_F +#define CONFIG_BOARD_LATE_INIT +#define CONFIG_MXC_GPIO + +#define CONFIG_MXC_UART + +#define CONFIG_CMD_FUSE +#ifdef CONFIG_CMD_FUSE +#define CONFIG_MXC_OCOTP +#endif + +/* I2C Configs */ +#define CONFIG_CMD_I2C +#define CONFIG_SYS_I2C +#define CONFIG_SYS_I2C_MXC +#define CONFIG_SYS_I2C_SPEED 100000 + +/* USB Configs */ +#define CONFIG_CMD_USB +#define CONFIG_USB_EHCI +#define CONFIG_USB_EHCI_MX6 +#define CONFIG_USB_STORAGE +#define CONFIG_USB_HOST_ETHER +#define CONFIG_USB_ETHER_ASIX +#define CONFIG_USB_MAX_CONTROLLER_COUNT 2 +#define CONFIG_EHCI_HCD_INIT_AFTER_RESET /* For OTG port */ +#define CONFIG_MXC_USB_PORTSC (PORT_PTS_UTMI | PORT_PTS_PTW) +#define CONFIG_MXC_USB_FLAGS 0 + +/* MMC Configs */ +#define CONFIG_FSL_ESDHC +#define CONFIG_FSL_USDHC +#define CONFIG_SYS_FSL_ESDHC_ADDR 0 + +#define CONFIG_MMC +#define CONFIG_CMD_MMC +#define CONFIG_GENERIC_MMC +#define CONFIG_BOUNCE_BUFFER +#define CONFIG_CMD_EXT2 +#define CONFIG_CMD_FAT +#define CONFIG_DOS_PARTITION + +#define CONFIG_CMD_PING +#define CONFIG_CMD_DHCP +#define CONFIG_CMD_MII +#define CONFIG_CMD_NET +#define CONFIG_FEC_MXC +#define CONFIG_MII +#define IMX_FEC_BASE ENET_BASE_ADDR +#define CONFIG_FEC_XCV_TYPE RGMII +#define CONFIG_ETHPRIME "FEC" +#define CONFIG_FEC_MXC_PHYADDR 4 + +#define CONFIG_PHYLIB +#define CONFIG_PHY_ATHEROS + +/* allow to overwrite serial and ethaddr */ +#define CONFIG_ENV_OVERWRITE +#define CONFIG_CONS_INDEX 1 +#define CONFIG_BAUDRATE 115200 + +/* Command definition */ +#include <config_cmd_default.h> + +#define CONFIG_CMD_BMODE +#define CONFIG_CMD_BOOTZ +#define CONFIG_CMD_SETEXPR +#undef CONFIG_CMD_IMLS + +#define CONFIG_BOOTDELAY 1 + +#define CONFIG_LOADADDR 0x12000000 +#define CONFIG_SYS_TEXT_BASE 0x17800000 + +#ifdef CONFIG_SUPPORT_EMMC_BOOT +#define EMMC_ENV \ + "emmcdev=2\0" \ + "update_emmc_firmware=" \ + "if test ${ip_dyn} = yes; then " \ + "setenv get_cmd dhcp; " \ + "else " \ + "setenv get_cmd tftp; " \ + "fi; " \ + "if ${get_cmd} ${update_sd_firmware_filename}; then " \ + "if mmc dev ${emmcdev}; then " \ + "setexpr fw_sz ${filesize} / 0x200; " \ + "setexpr fw_sz ${fw_sz} + 1; " \ + "mmc write ${loadaddr} 0x2 ${fw_sz}; " \ + "fi; " \ + "fi\0" +#else +#define EMMC_ENV "" +#endif + +#define CONFIG_EXTRA_ENV_SETTINGS \ + "script=boot.scr\0" \ + "image=zImage\0" \ + "fdt_file=" CONFIG_DEFAULT_FDT_FILE "\0" \ + "fdt_addr=0x18000000\0" \ + "boot_fdt=try\0" \ + "ip_dyn=yes\0" \ + "console=" CONFIG_CONSOLE_DEV "\0" \ + "fdt_high=0xffffffff\0" \ + "initrd_high=0xffffffff\0" \ + "mmcdev=" __stringify(CONFIG_SYS_MMC_ENV_DEV) "\0" \ + "mmcpart=1\0" \ + "mmcroot=" CONFIG_MMCROOT " rootwait rw\0" \ + "update_sd_firmware=" \ + "if test ${ip_dyn} = yes; then " \ + "setenv get_cmd dhcp; " \ + "else " \ + "setenv get_cmd tftp; " \ + "fi; " \ + "if mmc dev ${mmcdev}; then " \ + "if ${get_cmd} ${update_sd_firmware_filename}; then " \ + "setexpr fw_sz ${filesize} / 0x200; " \ + "setexpr fw_sz ${fw_sz} + 1; " \ + "mmc write ${loadaddr} 0x2 ${fw_sz}; " \ + "fi; " \ + "fi\0" \ + EMMC_ENV \ + "mmcargs=setenv bootargs console=${console},${baudrate} " \ + "root=${mmcroot}\0" \ + "loadbootscript=" \ + "fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${script};\0" \ + "bootscript=echo Running bootscript from mmc ...; " \ + "source\0" \ + "loadimage=fatload mmc ${mmcdev}:${mmcpart} ${loadaddr} ${image}\0" \ + "loadfdt=fatload mmc ${mmcdev}:${mmcpart} ${fdt_addr} ${fdt_file}\0" \ + "mmcboot=echo Booting from mmc ...; " \ + "run mmcargs; " \ + "if test ${boot_fdt} = yes || test ${boot_fdt} = try; then " \ + "if run loadfdt; then " \ + "bootz ${loadaddr} - ${fdt_addr}; " \ + "else " \ + "if test ${boot_fdt} = try; then " \ + "bootz; " \ + "else " \ + "echo WARN: Cannot load the DT; " \ + "fi; " \ + "fi; " \ + "else " \ + "bootz; " \ + "fi;\0" \ + "netargs=setenv bootargs console=${console},${baudrate} " \ + "root=/dev/nfs " \ + "ip=dhcp nfsroot=${serverip}:${nfsroot},v3,tcp\0" \ + "netboot=echo Booting from net ...; " \ + "run netargs; " \ + "if test ${ip_dyn} = yes; then " \ + "setenv get_cmd dhcp; " \ + "else " \ + "setenv get_cmd tftp; " \ + "fi; " \ + "${get_cmd} ${image}; " \ + "if test ${boot_fdt} = yes || test ${boot_fdt} = try; then " \ + "if ${get_cmd} ${fdt_addr} ${fdt_file}; then " \ + "bootz ${loadaddr} - ${fdt_addr}; " \ + "else " \ + "if test ${boot_fdt} = try; then " \ + "bootz; " \ + "else " \ + "echo WARN: Cannot load the DT; " \ + "fi; " \ + "fi; " \ + "else " \ + "bootz; " \ + "fi;\0" + +#define CONFIG_BOOTCOMMAND \ + "mmc dev ${mmcdev};" \ + "if mmc rescan; then " \ + "if run loadbootscript; then " \ + "run bootscript; " \ + "else " \ + "if run loadimage; then " \ + "run mmcboot; " \ + "else run netboot; " \ + "fi; " \ + "fi; " \ + "else run netboot; fi" + +#define CONFIG_ARP_TIMEOUT 200UL + +/* Miscellaneous configurable options */ +#define CONFIG_SYS_LONGHELP +#define CONFIG_SYS_HUSH_PARSER +#define CONFIG_SYS_PROMPT_HUSH_PS2 "> " +#define CONFIG_AUTO_COMPLETE +#define CONFIG_SYS_CBSIZE 256 + +/* Print Buffer Size */ +#define CONFIG_SYS_PBSIZE (CONFIG_SYS_CBSIZE + sizeof(CONFIG_SYS_PROMPT) + 16) +#define CONFIG_SYS_MAXARGS 16 +#define CONFIG_SYS_BARGSIZE CONFIG_SYS_CBSIZE + +#define CONFIG_SYS_MEMTEST_START 0x10000000 +#define CONFIG_SYS_MEMTEST_END 0x10010000 +#define CONFIG_SYS_MEMTEST_SCRATCH 0x10800000 + +#define CONFIG_SYS_LOAD_ADDR CONFIG_LOADADDR + +#define CONFIG_CMDLINE_EDITING +#define CONFIG_STACKSIZE (128 * 1024) + +/* Physical Memory Map */ +#define CONFIG_NR_DRAM_BANKS 1 +#define PHYS_SDRAM MMDC0_ARB_BASE_ADDR + +#define CONFIG_SYS_SDRAM_BASE PHYS_SDRAM +#define CONFIG_SYS_INIT_RAM_ADDR IRAM_BASE_ADDR +#define CONFIG_SYS_INIT_RAM_SIZE IRAM_SIZE + +#define CONFIG_SYS_INIT_SP_OFFSET \ + (CONFIG_SYS_INIT_RAM_SIZE - GENERATED_GBL_DATA_SIZE) +#define CONFIG_SYS_INIT_SP_ADDR \ + (CONFIG_SYS_INIT_RAM_ADDR + CONFIG_SYS_INIT_SP_OFFSET) + +/* FLASH and environment organization */ +#define CONFIG_SYS_NO_FLASH + +#define CONFIG_ENV_SIZE (8 * 1024) + +#define CONFIG_ENV_IS_IN_MMC + +#if defined(CONFIG_ENV_IS_IN_MMC ) +#define CONFIG_ENV_OFFSET (6 * 64 * 1024) +#endif + +#define CONFIG_OF_LIBFDT + +#ifndef CONFIG_SYS_DCACHE_OFF +#define CONFIG_CMD_CACHE +#endif + +#define CONFIG_SYS_FSL_USDHC_NUM 3 +#if defined(CONFIG_ENV_IS_IN_MMC ) +#define CONFIG_SYS_MMC_ENV_DEV 2/* SDHC4 */ +#endif + +/* Framebuffer */ +#define CONFIG_VIDEO +#define CONFIG_VIDEO_IPUV3 +#define CONFIG_CFB_CONSOLE +#define CONFIG_VGA_AS_SINGLE_DEVICE +#define CONFIG_SYS_CONSOLE_IS_IN_ENV +#define CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE
include/configs/riotboard.h line 299
Quoted 10 lines
include/configs/riotboard.h new file +10
-0+#define CONFIG_VIDEO_BMP_RLE8 +#define CONFIG_SPLASH_SCREEN +#define CONFIG_SPLASH_SCREEN_ALIGN +#define CONFIG_BMP_16BPP +#define CONFIG_VIDEO_LOGO +#define CONFIG_VIDEO_BMP_LOGO +#define CONFIG_IPUV3_CLK 260000000 +#define CONFIG_IMX_HDMI + +#endif /* __RIOTBOARD_CONFIG_H */
Best regards,
Stefano Babic
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 1/2 RiOTboard: add new board
Hi Stefano,
Le Sun, 30 Mar 2014 18:20:49 +0200,
Stefano Babic <[email protected]> a ?crit :
Quoted 25 lines
I jump directly to V4 ;-) Sorry for late review, I was not in office last days.
Added Ben in CC. He sent a first version for the Marsboard.
Quoted 12 lines · Eric B?nard
this board is produced by Embest/Element 14 and is based on i.MX6 Solo The following features are tested :
- UART2 (console)
- eMMC
- SDCard
- uSDCard
- Ethernet
- USB Host (through 4 ports hub)
- HDMI output
- I2C 1/2/3
- LVDS TFT with LCD8000-97C from Embest/Element 14Quoted 6 lines
Boot on eMMC and through USB loader are tested.
For more informations on this board : http://www.riotboard.org/
Signed-off-by Eric B?nard <[email protected]>---
Quoted 8 lines
A general remark. I agree by reading the whole thread about checking at runtime which is the running board (you do it getting the cpu type).
However, you use also a compiler switch mechanism, adding RIOTBOARD or MARSBOARD in the boards.cfg. You have implemented two ways to for the same thing. This makes in principle your runtime detection useless, because you can use #if
CONFIG_MARSBOARDinstead of "ifboard_type==BOARD_IS_MARSBOARD)".
True, as said in the log, anyway at the moment the same code can't run on both boards because of the different CPU (Solo vs Dual - and not Dual Lite).
Quoted 4 lines
Is it possible to use only the runtime detection ?
I think the main problem is CONFIG_ENV_IS_*, that is different for the two boards. What do you think about it ?
I'll see how we can handle the 2 CONFIG_ENV_IS with runtime detection.
Quoted 4 lines
IMHO you could also squash the two patches together. You add new files, and patch 2/2 changes some of them. I think in this case having a single patch makes review easier.
OK no problem.
Quoted 8 lines
board/embest/riotboard/riotboard.c line 117
Quoted 1 line
board/embest/riotboard/riotboard.c new file +1
-0+/* from linux/arch/arm/mach-imx/mach-imx6q.c : Codestyle in U-Boot for multiline comments is:
/*
* ...
*/
OK will fix. FWIW checkpatch doesn't provide any warning concerning this problem.
Quoted 9 lines
Quoted 3 lines
(quoted diff) +2
-0+int board_video_skip(void) +{..././//
We have already discussed in the past about this function. Each board (at least, imx6 board) want to have such of them, and code is duplicated. What about to factorize it ? I am not against to move it into imx-common, if we generally agree, but I would like to avoid to duplicate this function for each board.
OK, if I understand correctly you want me to factorize it ? ;-) I'll see what I can do there.
Thanks,
Eric
PATCH v4 1/2 RiOTboard: add new board
Hi Eric,
Quoted 8 lines · Eric B?nard
Quoted 6 lines
We have already discussed in the past about this function. Each board (at least, imx6 board) want to have such of them, and code is duplicated. What about to factorize it ? I am not against to move it into imx-common, if we generally agree, but I would like to avoid to duplicate this function for each board.
OK, if I understand correctly you want me to factorize it ? ;-) I'll see what I can do there.
It will be great, thanks !
Best regards,
Stefano
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 1/2 RiOTboard: add new board
In reply to Stefano BabicHi Stefano,
Le Sun, 30 Mar 2014 18:20:49 +0200,
Stefano Babic <[email protected]> a ?crit :
Quoted 11 lines
A general remark. I agree by reading the whole thread about checking at runtime which is the running board (you do it getting the cpu type).
However, you use also a compiler switch mechanism, adding RIOTBOARD or MARSBOARD in the boards.cfg. You have implemented two ways to for the same thing. This makes in principle your runtime detection useless, because you can use #if
CONFIG_MARSBOARDinstead of "ifboard_type==BOARD_IS_MARSBOARD)". Is it possible to use only the runtime detection ? I think the main problem is CONFIG_ENV_IS_*, that is different for the two boards. What do you think about it ?
I've tried and I don't see how to include functions to handle both MMC and SF environment in the same binary with the current env code.
A workaround would be to use MMC to store env also on the MarSBoard but as it is using the SPI flash as the boot source I would prefer to keep the env in the SPI flash.
Best regards,
Eric
PATCH v4 1/2 RiOTboard: add new board
Hi Eric,
Quoted 15 lines · Eric B?nard
Hi Stefano,
Le Sun, 30 Mar 2014 18:20:49 +0200,
Stefano Babic <[email protected]> a ?crit :Quoted 11 lines
A general remark. I agree by reading the whole thread about checking at runtime which is the running board (you do it getting the cpu type).
However, you use also a compiler switch mechanism, adding RIOTBOARD or MARSBOARD in the boards.cfg. You have implemented two ways to for the same thing. This makes in principle your runtime detection useless, because you can use #if
CONFIG_MARSBOARDinstead of "ifboard_type==BOARD_IS_MARSBOARD)". Is it possible to use only the runtime detection ? I think the main problem is CONFIG_ENV_IS_*, that is different for the two boards. What do you think about it ?
Quoted 3 lines
I've tried and I don't see how to include functions to handle both MMC and SF environment in the same binary with the current env code.
I was not sure, but I had the feeling this can be the major issue.
Quoted 4 lines
A workaround would be to use MMC to store env also on the MarSBoard but as it is using the SPI flash as the boot source I would prefer to keep the env in the SPI flash.
Ok - then I propose that you have still two entries in boards.cfg, and you set there ENV_IS_IN_MMC or ENV_IS_IN_SPI_FLASH. A lot of boards, having different hardware configurations, are doing in this way. You can drop CONFIG_RIOTBOARD and CONFIG_MARSBOARD as well (for example, mx28evk has an entry in boards.cfg mx28evk_nand for ENV on NAND).
Best regards,
Stefano
Signature · 5 lines
===================================================================== DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de =====================================================================
PATCH v4 1/2 RiOTboard: add new board
Hi Stefano,
Le Tue, 01 Apr 2014 10:41:50 +0200,
Stefano Babic <[email protected]> a ?crit :
Quoted 25 lines · Eric B?nard
Quoted 13 lines
Le Sun, 30 Mar 2014 18:20:49 +0200,
Stefano Babic <[email protected]> a ?crit :Quoted 11 lines
A general remark. I agree by reading the whole thread about checking at runtime which is the running board (you do it getting the cpu type).
However, you use also a compiler switch mechanism, adding RIOTBOARD or MARSBOARD in the boards.cfg. You have implemented two ways to for the same thing. This makes in principle your runtime detection useless, because you can use #if
CONFIG_MARSBOARDinstead of "ifboard_type==BOARD_IS_MARSBOARD)". Is it possible to use only the runtime detection ? I think the main problem is CONFIG_ENV_IS_*, that is different for the two boards. What do you think about it ?Quoted 3 lines
I've tried and I don't see how to include functions to handle both MMC and SF environment in the same binary with the current env code.
I was not sure, but I had the feeling this can be the major issue.
Quoted 4 lines
A workaround would be to use MMC to store env also on the MarSBoard but as it is using the SPI flash as the boot source I would prefer to keep the env in the SPI flash.
Quoted 6 lines
Ok - then I propose that you have still two entries in boards.cfg, and you set there
ENV_IS_IN_MMCorENV_IS_IN_SPI_FLASH. A lot of boards, having different hardware configurations, are doing in this way. You can dropCONFIG_RIOTBOARDandCONFIG_MARSBOARDas well (for example, mx28evk has an entry in boards.cfgmx28evk_nandfor ENV on NAND).
you're right that will remove the ifdef in the config file, thanks.
Eric