Part Number:66ak2h14
I have two EMVK2Hx boards that are connected via a custom backplane to allow HyperLink message passing. I have successfully run the HyperLink example application and established communication between the two boards. I'm now attempting to boot one board over HyperLink. I believe I have successfully configured the boot mode within the BMC console to allow CorePac0 to boot over HyperLink. With the RX device in HyperLink boot mode and the TX device running the HyperLink example application I believe the HyperLink connection is established correctly. Now I need to understand the default segment mapping for the RX device.
The only information that I have found regarding the HyperLink Boot ROM segment mapping was contained in a post from 2012. In that correspondence, dated April 17, 2012, Mr. Arun Mani indicated that the table would be included in the "next document version". To my knowledge this information is not contained in any TI documentation. If there is a document providing this information could you please direct me to it's location. Below is a copy of the table from the original post. I'm unclear as to the actual mapping of the four regions described as "Config Regs" with respect to the KeyStone II 66AK2H14 device.
Boot ROM Initialized HyperLink Segment Mapping | |||
Segment | Size | Translated Address | Description |
0 - N | Size of L2 | Global address of Core0 L2 to CoreN L2 | Global L2 |
N + 1 | 128k | 0x08000000 | XMC config |
N + 2 | 1Mb | 0x0bc00000 | MSMC config |
N + 3 | Size of MSMC memory | 0x0c000000 | MSMC memory |
N + 4 | 4Mb | 0x01c00000 | Config Regs |
N + 5 | 4Mb | 0x02000000 | Config Regs |
N + 6 | 4Mb | 0x02400000 | Config Regs |
N + 7 | 2Mb | 0x02800000 | Config Regs |
N + 8 | 512 Bytes | 0x21000000 | DDR Config |
(N + 9) – 63 | 4Mb | 0x80000000 (4Mb steps) | DDR Memory |
(1) Could you please provide an updated table that reflects the HyperLink Boot ROM Segment Mapping for a KeyStone II 66AK2H14 device?
(2) What is the proper way to bring CorePac0 out of Idle to start execution of the loaded code assuming the boot magic address has already been updated?
Thank you for your support.
Jack