Re: [U-Boot] [PATCH V5 7/7] board: ti: AM57xx: Add detection logic for AM57xx-evm
On Wed, Feb 24, 2016 at 12:30:58PM -0600, Steve Kipisz wrote: > Current AM57xx evm supports both BeagleBoard-X15 > (http://beagleboard.org/x15) and AM57xx EVM > (http://www.ti.com/tool/tmdxevm5728). > > The AM572x EValuation Module(EVM) provides an affordable platform to > quickly start evaluation of Sitara. ARM Cortex-A15 AM57x Processors > (AM5728, AM5726, AM5718, AM5716) and accelerate development for HMI, > machine vision, networking, medical imaging and many other industrial > applications. This EVM is based on the same BeagleBoard-X15 Chassis > and adds mPCIe, mSATA, LCD, touchscreen, Camera, push button and TI's > wlink8 offering. > > Since the EEPROM contents are compatible between the BeagleBoard-X15 and > the AM57xx-evm, we add support for the detection logic to enable > support for various user programmable scripting capability. > > NOTE: U-boot configuration is currently a superset of AM57xx evm and > BeagleBoard-X15 and no additional configuration tweaking is needed. > > This change also sets up the stage for future support of TI AM57xx EVMs > to the same base bootloader build. > > Signed-off-by: Steve Kipisz > Signed-off-by: Lokesh Vutla > Signed-off-by: Nishanth Menon Reviewed-by: Tom Rini -- Tom signature.asc Description: Digital signature ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH V5 7/7] board: ti: AM57xx: Add detection logic for AM57xx-evm
On 02/25/2016 01:06 AM, Lokesh Vutla wrote: > [..snip..] > [...] >> "setenv fdtfile dra72-evm.dtb; fi;" \ >> "if test $board_name = beagle_x15; then " \ >> "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \ >> +"if test $board_name = am57xx_evm; then " \ >> +"setenv fdtfile am57xx-beagle-x15.dtb; fi;" \ > > Is it the same dtb file for am57xx_evm as well? or is this intentional > and will be updated later? Yes - it should be the same dtb file for 2 reasons: A) At this point in patch, we dont want to break am57xx-evm - mentioned in diffstat to remind ourselves. B) we are attempting to move all these "cape" like variants into device tree overlays -> in which case the same dtb is reused even for am57xx-evm, and overlay with panel and touchscreen for the "gpevm" panel board. So, in almost with 80% certainty, we might not introduce a am57xx_evm.dtb in upstream - we really dont need to. In fact, upstream kernel and current master u-boot does bootup successfully, and would like to maintain it so (point A). -- Regards, Nishanth Menon ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH V5 7/7] board: ti: AM57xx: Add detection logic for AM57xx-evm
[..snip..] diff --git a/include/configs/am57xx_evm.h b/include/configs/am57xx_evm.h index 6308cab8e680..1fffdb18fbcd 100644 --- a/include/configs/am57xx_evm.h +++ b/include/configs/am57xx_evm.h @@ -88,4 +88,8 @@ #define CONFIG_SYS_SCSI_MAX_DEVICE(CONFIG_SYS_SCSI_MAX_SCSI_ID * \ CONFIG_SYS_SCSI_MAX_LUN) +/* EEPROM */ +#define CONFIG_EEPROM_CHIP_ADDRESS 0x50 +#define CONFIG_EEPROM_BUS_ADDRESS 0 + #endif /* __CONFIG_AM57XX_EVM_H */ diff --git a/include/configs/ti_omap5_common.h b/include/configs/ti_omap5_common.h index d164e6abd450..d373cbc44a16 100644 --- a/include/configs/ti_omap5_common.h +++ b/include/configs/ti_omap5_common.h @@ -117,6 +117,8 @@ "setenv fdtfile dra72-evm.dtb; fi;" \ "if test $board_name = beagle_x15; then " \ "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \ + "if test $board_name = am57xx_evm; then " \ + "setenv fdtfile am57xx-beagle-x15.dtb; fi;" \ Is it the same dtb file for am57xx_evm as well? or is this intentional and will be updated later? Thanks and regards, Lokesh "if test $fdtfile = undefined; then " \ "echo WARNING: Could not determine device tree to use; fi; \0" \ "loadfdt=load mmc ${bootpart} ${fdtaddr} ${bootdir}/${fdtfile};\0" \ ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot