Andrew F. Davis | 817bbee | 2016-08-30 14:06:20 -0500 | [diff] [blame] | 1 | if AM33XX |
| 2 | |
| 3 | choice |
| 4 | prompt "AM33xx board select" |
| 5 | optional |
| 6 | |
| 7 | config TARGET_AM335X_EVM |
| 8 | bool "Support am335x_evm" |
| 9 | select DM |
| 10 | select DM_SERIAL |
| 11 | select DM_GPIO |
| 12 | select TI_I2C_BOARD_DETECT |
| 13 | help |
| 14 | This option specifies support for the AM335x |
| 15 | GP and HS EVM development platforms. The AM335x |
| 16 | GP EVM is a standalone test, development, and |
| 17 | evaluation module system that enables developers |
| 18 | to write software and develop hardware around |
| 19 | an AM335x processor subsystem. |
| 20 | |
| 21 | config TARGET_AM335X_BALTOS |
| 22 | bool "Support am335x_baltos" |
| 23 | select DM |
| 24 | select DM_SERIAL |
| 25 | select DM_GPIO |
| 26 | |
| 27 | config TARGET_AM335X_IGEP0033 |
| 28 | bool "Support am335x_igep0033" |
| 29 | select DM |
| 30 | select DM_SERIAL |
| 31 | select DM_GPIO |
| 32 | |
| 33 | config TARGET_AM335X_SHC |
| 34 | bool "Support am335x based shc board from bosch" |
| 35 | select DM |
| 36 | select DM_SERIAL |
| 37 | select DM_GPIO |
| 38 | |
| 39 | config TARGET_AM335X_SL50 |
| 40 | bool "Support am335x_sl50" |
| 41 | select DM |
| 42 | select DM_SERIAL |
| 43 | select DM_GPIO |
| 44 | |
| 45 | config TARGET_BAV335X |
| 46 | bool "Support bav335x" |
| 47 | select DM |
| 48 | select DM_SERIAL |
| 49 | help |
| 50 | The BAV335x OEM Network Processor integrates all the functions of an |
| 51 | embedded network computer in a small, easy to use SODIMM module which |
| 52 | incorporates the popular Texas Instruments Sitara 32bit ARM Coretex-A8 |
| 53 | processor, with fast DDR3 512MB SDRAM, 4GB of embedded MMC and a Gigabit |
| 54 | ethernet with simple connection to external connectors. |
| 55 | |
| 56 | For more information, visit: http://birdland.com/oem |
| 57 | |
| 58 | config TARGET_CM_T335 |
| 59 | bool "Support cm_t335" |
| 60 | select DM |
| 61 | select DM_SERIAL |
| 62 | select DM_GPIO |
| 63 | |
| 64 | config TARGET_PCM051 |
| 65 | bool "Support pcm051" |
| 66 | select DM |
| 67 | select DM_SERIAL |
| 68 | select DM_GPIO |
| 69 | |
| 70 | config TARGET_PENGWYN |
| 71 | bool "Support pengwyn" |
| 72 | select DM |
| 73 | select DM_SERIAL |
| 74 | select DM_GPIO |
| 75 | |
| 76 | config TARGET_PEPPER |
| 77 | bool "Support pepper" |
| 78 | select DM |
| 79 | select DM_SERIAL |
| 80 | select DM_GPIO |
| 81 | |
| 82 | endchoice |
| 83 | |
| 84 | endif |
| 85 | |
Madan Srinivas | eba13cd | 2016-05-19 19:10:43 -0500 | [diff] [blame] | 86 | if AM43XX |
Simon Glass | c5ec636 | 2016-09-12 23:18:37 -0600 | [diff] [blame] | 87 | |
| 88 | config SPL_EXT_SUPPORT |
| 89 | default y |
| 90 | |
Simon Glass | 0bdfc3e | 2016-09-12 23:18:39 -0600 | [diff] [blame] | 91 | config SPL_GPIO_SUPPORT |
| 92 | default y |
| 93 | |
Simon Glass | 9b53833 | 2016-09-12 23:18:40 -0600 | [diff] [blame] | 94 | config SPL_I2C_SUPPORT |
| 95 | default y |
| 96 | |
Madan Srinivas | eba13cd | 2016-05-19 19:10:43 -0500 | [diff] [blame] | 97 | config TARGET_AM43XX_EVM |
| 98 | bool "Support am43xx_evm" |
| 99 | select TI_I2C_BOARD_DETECT |
| 100 | help |
| 101 | This option specifies support for the AM43xx |
| 102 | GP and HS EVM development platforms.The AM437x |
| 103 | GP EVM is a standalone test, development, and |
| 104 | evaluation module system that enables developers |
| 105 | to write software and develop hardware around |
| 106 | an AM43xx processor subsystem. |
Andrew F. Davis | 817bbee | 2016-08-30 14:06:20 -0500 | [diff] [blame] | 107 | endif |
Madan Srinivas | eba13cd | 2016-05-19 19:10:43 -0500 | [diff] [blame] | 108 | |
Andrew F. Davis | 817bbee | 2016-08-30 14:06:20 -0500 | [diff] [blame] | 109 | if AM43XX || AM33XX |
Madan Srinivas | fb59e8e | 2016-05-19 19:10:42 -0500 | [diff] [blame] | 110 | config ISW_ENTRY_ADDR |
| 111 | hex "Address in memory or XIP flash of bootloader entry point" |
| 112 | help |
| 113 | After any reset, the boot ROM on the AM43XX SOC |
| 114 | searches the boot media for a valid boot image. |
| 115 | For non-XIP devices, the ROM then copies the |
| 116 | image into internal memory. |
| 117 | For all boot modes, after the ROM processes the |
| 118 | boot image it eventually computes the entry |
| 119 | point address depending on the device type |
| 120 | (secure/non-secure), boot media (xip/non-xip) and |
| 121 | image headers. |
Andrew F. Davis | 74c48a0 | 2017-01-06 16:32:12 -0600 | [diff] [blame] | 122 | default 0x402F4000 if AM43XX |
| 123 | default 0x402F0400 if AM33XX |
Madan Srinivas | fb59e8e | 2016-05-19 19:10:42 -0500 | [diff] [blame] | 124 | |
| 125 | config PUB_ROM_DATA_SIZE |
| 126 | hex "Size in bytes of the L3 SRAM reserved by ROM to store data" |
| 127 | help |
| 128 | During the device boot, the public ROM uses the top of |
| 129 | the public L3 OCMC RAM to store r/w data like stack, |
| 130 | heap, globals etc. When the ROM is copying the boot |
| 131 | image from the boot media into memory, the image must |
| 132 | not spill over into this area. This value can be used |
| 133 | during compile time to determine the maximum size of a |
| 134 | boot image. Once the ROM transfers control to the boot |
| 135 | image, this area is no longer used, and can be reclaimed |
| 136 | for run time use by the boot image. |
| 137 | default 0x8400 |
Madan Srinivas | eba13cd | 2016-05-19 19:10:43 -0500 | [diff] [blame] | 138 | endif |