Trusted Firmware-A https://git.rulkc.org/pub/scm/arm/software/arm-trusted-firmware.git/atom?h=v1.3 2016-10-13T16:49:06+00:00 2016-10-13T16:49:06+00:00 davidcunado-arm david.cunado@arm.com 2016-10-13T16:49:06+00:00 urn:sha1:6bb37adc203567c2f9322dfbe34058a5f12d4c70 Final updates for v1.3 release 2016-10-13T16:48:29+00:00 davidcunado-arm david.cunado@arm.com 2016-10-13T16:48:29+00:00 urn:sha1:fd0201bc30e9fb9ada06e327974b408a6d6a85e0 Release v1.3: Minor updates to user guide 2016-10-13T16:45:12+00:00 David Cunado david.cunado@arm.com 2016-10-13T15:04:12+00:00 urn:sha1:49db6f1cbaf1c63a85e3d915944ac5514af09c90 Updated the user guide to clarify building FIP for AArch32. The instructions were previously specific to building a FIP for AArch64. Change-Id: I7bd1a6b8e810cfda411f707e04f479006817858e Signed-off-by: David Cunado <david.cunado@arm.com> 2016-10-13T14:18:11+00:00 Dan Handley dan.handley@arm.com 2016-10-11T15:17:11+00:00 urn:sha1:3a2879450fcb4154ad2ea05fffa53d4879f2f24e Update the release notes (readme.md) for the ARM Trusted Firmware v1.3 release. Change-Id: Ia1f4eb1897e63eeab7d69a593ba0ad91d50043f5 Signed-off-by: Dan Handley <dan.handley@arm.com> 2016-10-13T14:17:39+00:00 David Cunado david.cunado@arm.com 2016-10-04T15:06:37+00:00 urn:sha1:d4e748f30bb2b5da04d84bb935eb3189d5088165 Change-Id: I05991543d28e70b67be600b714990af6a8d7ba29 2016-10-13T14:17:39+00:00 David Cunado david.cunado@arm.com 2016-10-03T17:20:35+00:00 urn:sha1:6ad67cc858fb11c3c294933e7d6b668708901a85 Updated change-log.md with summary of changes since release v1.2. Change-Id: Ia1e18ff4b0da567cf12dfcb53e6317e995100bdf 2016-10-12T16:17:19+00:00 danh-arm dan.handley@arm.com 2016-10-12T16:17:19+00:00 urn:sha1:b314c9fa88271a5b88cdbcbfd6319405e0a4e30e PMF: Add documentation 2016-10-12T16:04:16+00:00 dp-arm dimitris.papastamos@arm.com 2016-09-08T10:54:22+00:00 urn:sha1:514a94c2dcee5cf72a0479ce20cf384898e84a97 Add a Performance Measurement Framework (PMF) section to the firmware design document. Change-Id: I5953bd3b1067501f190164c8827d2b0d8022fc0b Signed-off-by: dp-arm <dimitris.papastamos@arm.com> 2016-10-12T10:52:57+00:00 danh-arm dan.handley@arm.com 2016-10-12T10:52:57+00:00 urn:sha1:2c8df7c12cc0ed45bc9aa5f1b33668955a6623c4 Fix documentation of bootwrapper boot on juno 2016-10-12T10:42:06+00:00 Antonio Nino Diaz antonio.ninodiaz@arm.com 2016-04-20T10:55:14+00:00 urn:sha1:7486eb047563e1cd5f0efebe526699e37319bcbc The user guide incorrectly claimed that it is possible to load a bootwrapped kernel over JTAG on Juno in the same manner as an EL3 payload. In the EL3 payload boot flow, some of the platform initialisations in BL2 are modified. In particular, the TZC settings are modified to allow unrestricted access to DRAM. This in turn allows the debugger to access the DRAM and therefore to load the image there. In the BL33-preloaded boot flow though, BL2 uses the default TZC programming, which prevent access to most of the DRAM from secure state. When execution reaches the SPIN_ON_BL1_EXIT loop, the MMU is disabled and thus DS-5 presumably issues secure access transactions while trying to load the image, which fails. One way around it is to stop execution at the end of BL2 instead. At this point, the MMU is still enabled and the DRAM is mapped as non-secure memory. Therefore, the debugger is allowed to access this memory in this context and to sucessfully load the bootwrapped kernel in DRAM. The user guide is updated to suggest this alternative method. Co-Authored-By: Sandrine Bailleux <sandrine.bailleux@arm.com> Signed-off-by: Dan Handley <dan.handley@arm.com> Change-Id: I537ea1c6d2f96edc06bc3f512e770c748bcabe94