Madan Srinivas | eba13cd | 2016-05-19 19:10:43 -0500 | [diff] [blame^] | 1 | if AM43XX |
| 2 | config TARGET_AM43XX_EVM |
| 3 | bool "Support am43xx_evm" |
| 4 | select TI_I2C_BOARD_DETECT |
| 5 | help |
| 6 | This option specifies support for the AM43xx |
| 7 | GP and HS EVM development platforms.The AM437x |
| 8 | GP EVM is a standalone test, development, and |
| 9 | evaluation module system that enables developers |
| 10 | to write software and develop hardware around |
| 11 | an AM43xx processor subsystem. |
| 12 | |
Madan Srinivas | fb59e8e | 2016-05-19 19:10:42 -0500 | [diff] [blame] | 13 | config ISW_ENTRY_ADDR |
| 14 | hex "Address in memory or XIP flash of bootloader entry point" |
| 15 | help |
| 16 | After any reset, the boot ROM on the AM43XX SOC |
| 17 | searches the boot media for a valid boot image. |
| 18 | For non-XIP devices, the ROM then copies the |
| 19 | image into internal memory. |
| 20 | For all boot modes, after the ROM processes the |
| 21 | boot image it eventually computes the entry |
| 22 | point address depending on the device type |
| 23 | (secure/non-secure), boot media (xip/non-xip) and |
| 24 | image headers. |
| 25 | default 0x402F4000 |
| 26 | |
| 27 | config PUB_ROM_DATA_SIZE |
| 28 | hex "Size in bytes of the L3 SRAM reserved by ROM to store data" |
| 29 | help |
| 30 | During the device boot, the public ROM uses the top of |
| 31 | the public L3 OCMC RAM to store r/w data like stack, |
| 32 | heap, globals etc. When the ROM is copying the boot |
| 33 | image from the boot media into memory, the image must |
| 34 | not spill over into this area. This value can be used |
| 35 | during compile time to determine the maximum size of a |
| 36 | boot image. Once the ROM transfers control to the boot |
| 37 | image, this area is no longer used, and can be reclaimed |
| 38 | for run time use by the boot image. |
| 39 | default 0x8400 |
Madan Srinivas | eba13cd | 2016-05-19 19:10:43 -0500 | [diff] [blame^] | 40 | endif |