- 31 Dec, 2020 2 commits
-
-
Andre Przywara authored
The H616 has quite a large chunk of continuous SRAM, and also the BROM allows to load eGON images far bigger than 32KB. U-Boot's SPL is actually relying on this, as we need more code for the PMIC and DRAM driver. Move the FEL stack backup buffers and the thunk address towards the end of SRAM C, so that we have a larger chunk of continuous SRAM available for the SPL. Signed-off-by: Andre Przywara <osp@andrep.de>
-
Andre Przywara authored
At the moment we assume the SPL load size to be limited to 32KB, even though many SoCs have more SRAM A1 or a large SRAM C directly after SRAM A1. To later allow to extend the SPL load size, let's introduce a SoC specific variable to hold the SRAM size after the SPL load address. This could either cover the whole of SRAM A1, or even SRAM C, if that is contiguous to SRAM A1. Eventually this variable is meant to hold the *usable* SRAM size, so not including regions that are used by the BROM code. However this value is very SoC specific and not documented, and the SPL size is limited by the thunk and stack buffers anyway at the moment, so the values used here right now are just taken from the respective manuals. Signed-off-by: Andre Przywara <osp@andrep.de>
-
- 08 Nov, 2020 1 commit
-
-
Andre Przywara authored
The "wdreset" command so far only covered a few SoCs. Add the watchdog data for the other ones as well. Signed-off-by: Andre Przywara <osp@andrep.de>
-
- 02 Oct, 2020 1 commit
-
-
Jernej Skrabec authored
-
- 29 Sep, 2020 1 commit
-
-
Icenowy Zheng authored
The non-IRQ stack is moved to near the end of the SRAM C, which is very high, and have no need to save. Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
-
- 14 Jun, 2020 2 commits
-
-
Priit Laes authored
Signed-off-by: Priit Laes <plaes@plaes.org>
-
Karl Palsson authored
The watchdog register isn't in the same place, nor uses the same values to trigger a reset. Signed-off-by: Karl Palsson <karlp@tweak.net.au>
-
- 20 Apr, 2020 1 commit
-
-
Karl Palsson authored
The watchdog register isn't in the same place, nor uses the same values to trigger a reset. Signed-off-by: Karl Palsson <karlp@tweak.net.au>
-
- 09 Jul, 2018 1 commit
-
-
Icenowy Zheng authored
Allwinner H6 is a new SoC with its memory map changed. Add its SoC info, including SRAM addresses and SID address. Signed-off-by: Icenowy Zheng <icenowy@aosc.io> Signed-off-by: Andre Przywara <osp@andrep.de>
-
- 27 Feb, 2018 1 commit
-
-
Jack Mitchell authored
As per the wiki[1] set ttbr0 to 0x44000 to enable the MMU. Transfer speed is increased from 191KB/s to ~800KB/s which is handy when transferring larger kernels and root filesystems. Tested on a custom H8/A83T board. [1] https://linux-sunxi.org/FEL/USBBoot
-
- 28 Feb, 2017 1 commit
-
-
Siarhei Siamashka authored
Use a hardwired L.NOP instruction from the OpenRISC reset vector as a way to check if the workaround is necessary. Because these L.NOP instructions are guaranteed to be there and are read-only, this is the most reliable non-invasive test. Reading SID would be less reliable because it is one-time programmable and theoretically may be set to zero on some boards. Signed-off-by: Siarhei Siamashka <siarhei.siamashka@gmail.com>
-
- 28 Dec, 2016 3 commits
-
-
Icenowy Zheng authored
H3 SID controller has some bug, that makes the initial value at 0x01c14200 wrong. This commit workarounds this bug by reading them with register access first. Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz> Reviewed-by: Bernhard Nortmann <bernhard.nortmann@web.de>
-
Bernhard Nortmann authored
This is a preparatory step. Instead of using memory-based access, we might want to retrieve SID keys (e-fuses) via SID registers. For this, it's convenient if the plain base address is available. Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
-
Icenowy Zheng authored
The V3s SoC looks like A10/13/20 in SRAM mapping and SID address. Add support for it. Signed-off-by: Icenowy Zheng <icenowy@aosc.xyz>
-
- 01 Dec, 2016 1 commit
-
-
Bernhard Nortmann authored
Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
-
- 29 Nov, 2016 3 commits
-
-
Bernhard Nortmann authored
open_fel_device() will automatically provide this member field, based on the SoC ID from FEL/BROM version data. The field will either receive a human-readable identifier, or the ID in 4-digit hexadecimal representation (for unknown SoCs). Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
-
Chen-Yu Tsai authored
The SID block in the A80 is at 0x01c0e000, with the e-fuses we care about at offset 0x200 within the block. Signed-off-by: Chen-Yu Tsai <wens@csie.org>
-
Chen-Yu Tsai authored
The R40 is marketed as the successor to the A20. The SRAM layout is the same as the A20, but there doesn't seem to be a secure SRAM block. The SID block is at a completely different address. The layout is the same as the newer SoCs, with the e-fuses at an offset of 0x200. Signed-off-by: Chen-Yu Tsai <wens@csie.org>
-
- 16 Nov, 2016 1 commit
-
-
Bernhard Nortmann authored
Besides having fewer lines of code, the #define macros should also prevent users from accidentally using these names without braces (i.e. as function pointers). Instead, this will cause compiler errors now. soc_info.c: add "A10s" label in comment for SoC ID 0x1625. Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
-
- 13 Nov, 2016 1 commit
-
-
Bernhard Nortmann authored
While at it, modify the former "sram_info" identifiers to carry a broader "soc_info" meaning. Signed-off-by: Bernhard Nortmann <bernhard.nortmann@web.de>
-