- 21 Jul, 2018 7 commits
-
-
Josua Mayer authored
Because nandargs is run earlier, if bootargs.scr doesn't overwrite the bootargs, root and rootfstype will be polluted with nand values. Signed-off-by:
Josua Mayer <josua.mayer97@gmail.com>
-
Josua Mayer authored
Most modern distros want to boot with an initramfs, so setting a default load address for it seems reasonable. Signed-off-by:
Josua Mayer <josua.mayer97@gmail.com>
-
Josua Mayer authored
U-Boot Distro-Boot has defined standard names for load addresses across all devices. Mass-replace all occurences of the old names. Signed-off-by:
Josua Mayer <josua.mayer97@gmail.com>
-
Josua Mayer authored
distro-boot would set a few variables explaining what device was selected to boot from. This is a bare minimum, just enough to boot Debian. devtype: boot device, e.g. mmc devnum: number of boot device, e.g. 0,1,2,... distro_bootpart: selected partition number prefix: base path where bootable files were found Signed-off-by:
Josua Mayer <josua.mayer97@gmail.com>
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 01 Jul, 2018 3 commits
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 27 Jun, 2018 1 commit
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 29 May, 2018 2 commits
-
-
Tony Lindgren authored
With u-boot related memory errors out of the way fixed with patch "LC15: Fix flakey ddr3 detection with ref_ctrl and ref_ctrl_final", we can now narrow down the kernel related errors easily. Playing with timing changes I narrowed down the kernel hangs to register sdram_tim3 where we need to increase the time for T_RFC. This is for "Minimum number of DDR clock cycles from Refresh or Load Mode to Refresh or Activate, minus one" according to omap5432 TRM. Maxing out the value for bits 12:4 made the new 4GB pyra's C02 and C03 boot reliably. And then looking at the timings again, the T_RFC value should be 187 - 1 (0xBA) and not 139 - 1 (0x8A). Note the Upper case B vs 8 :) Value 187 - 1 (0xBA) matches Samsung K4B8G1646D-MYK0 datasheet "[ Table 34 ] Timing used for IDD and IDDQ Measured - Loop Patterns" for DDR3-1066 8Gb memory. We are currently using 4Gb value 139 - 1 (0x8A). It is possible that this was caused by B vs 8 typo initially and then was not noticed because of the u-boot memory errors and getting confused with the memory datasheet for 4Gb vs 4GB while we have four 8Gb memory chips. However I also noticed that value 187 - 1 (0xBA) still won't work reliably with new board C05. And new C21 and my older revision board C50 still did not work at all. However, using value of 191 - 1 (0xBE) makes all of them boot reliably for me. So let's use value 191 - 1 (0xBE) for now, and adjust it if needed based on testing with more pyras. Note that we still can have pyra hang running two instances of memtester 1500M for about 10 minutes on bare CPU boards with no heat sink connected. The boards now boot reliably after that though, so presumably the pyra heat sink will solve this issue. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
Since commit 802bb57a ("ARM: DRA7: EMIF: Update SDRAM_REF_CTRL register value") we now do this in two phases. We are not currently configuring ref_ctrl and this seems to cause bogus memory errors early in u-boot that often happen if the board has been powered off for a while: SDRAM: identified size not same as expected size identified: 0 expected: 40000000 ... WARNING: DDR RAM is not working! (12000000) ... ### ERROR ### Please RESET the board ### Note that this does not solve the kernel related memory issues, but gets us to the point where u-boot starts reliably. Signed-off-by:
Tony Lindgren <tony@atomide.com>
-
- 28 May, 2018 2 commits
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 22 Feb, 2018 1 commit
-
-
H. Nikolaus Schaller authored
bootscr: beagleboneblack: switch mmc and kernelmmc definitions by experimentational result - deeper reason is not understood; this makes boot from µSD work again Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 21 Feb, 2018 2 commits
-
-
H. Nikolaus Schaller authored
kernel assumes to include "gta04" Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
H. Nikolaus Schaller authored
we have to do the same as for gta04, override the beaglerev variable or the findfdt command would overwrite the fdtfile variable by its own rules. Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 18 Dec, 2017 2 commits
-
-
H. Nikolaus Schaller authored
This helps in the situation of a completely empty battery where without this patch, charging would only begin after Linux has set up the charger. This might be 30 or 50 seconds after first automatic start - with a very weakly charged battery. So we simply enable the charger with 500mA by the boot.scr and then there is enough power from USB (it is <100mA if the OMAP is off) to boot into Linux and continue charging. This fixes issue: http://projects.goldelico.com/p/gta04-xloader/issues/279/Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
Andreas Kemnade authored
to avoid trouble with too weak equipment which cannot deliver 850mA without dropping the voltage too much (weak cables will be enough) is charge current is left at default level (500mA) Signed-off-by:
Andreas Kemnade <andreas@kemnade.info>
-
- 30 Nov, 2017 1 commit
-
-
Andreas Kemnade authored
phy was only enabled half in twl4030_usb_charger_enable(), parts were missing and there was a loop without a timeout making charger_enable hang when something else has not initialized the phy enough. Fix that by calling the apropiate phy init function Signed-off-by:
Andreas Kemnade <andreas@kemnade.info>
-
- 31 Jul, 2017 1 commit
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 13 Jul, 2017 1 commit
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 10 Jul, 2017 3 commits
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
Breno Lima authored
It's not necessary to define the processor in the defconfig file. The preferred method to select the SoC is via Kconfig file. Signed-off-by:
Breno Lima <breno.lima@nxp.com> Reviewed-by:
Fabio Estevam <fabio.estevam@nxp.com>
-
Breno Lima authored
UDOO Neo Board is a development board from Seco that has three models: - UDOO Neo Basic - UDOO Neo Basic Kick Starter - UDOO Neo Extended - UDOO Neo Full All versions are based on the i.MX6 SoloX processor. For more details about the UDOO Neo board, please refer to: http://www.udoo.org/udoo-neo/ This work is based on a previous commit of Francesco Montefoschi <francesco.monte@gmail.com>: https://github.com/fmntf/u-boot/commit/877b71184a5105e708024f232d36aed574961844 Only tested on the UDOO Neo Full board. Signed-off-by:
Breno Lima <breno.lima@nxp.com> Reviewed-by:
Fabio Estevam <fabio.estevam@nxp.com>
-
- 26 Apr, 2017 1 commit
-
-
H. Nikolaus Schaller authored
DRAM timings provided by Matthijs van Duin <matthijsvanduin@gmail.com> Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 24 Apr, 2017 4 commits
-
-
H. Nikolaus Schaller authored
Letux: bootscr: adapt GTA04 boot.scr to latest distribution kernel variable names and make it reset the environment when flashing Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
Josua Mayer authored
DeviceTree has a special node for passing certain boot arguments from the firmware on to the kernel: Enable the u-boot facility that sets chosen->stdout-path to the same serial console that u-boot itself was built to use. Signed-off-by:
Josua Mayer <josua.mayer97@gmail.com>
-
Josua Mayer authored
omap3_beagle defines CONFIG_BOOTCOMMAND in a way that it first runs the findfdt script. By setting beaglerev to undefined, findfdt can no longer override what has been set by the boardfile. Signed-off-by:
Josua Mayer <josua.mayer97@gmail.com>
-
Guillaume GARDET authored
Add support for distro_bootcmd on MMC and fall back to prior behavior if distro_bootcmd fails. Tested on Beagleboad xM to boot GRUB2 (and then Linux kernel) in EFI mode from MMC. Signed-off-by:
Guillaume GARDET <guillaume.gardet@free.fr> Cc: Tom Rini <trini@konsulko.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- 24 Mar, 2017 1 commit
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 17 Mar, 2017 1 commit
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-
- 28 Feb, 2017 6 commits
-
-
H. Nikolaus Schaller authored
does not solve the issue. This reverts commit 90d4a09f.
-
H. Nikolaus Schaller authored
does not solve the issue. This reverts commit 797396f3.
-
notaz authored
otherwise MLO reads some trash from fixed point of SD card (calling it "raw image") and tries to boot it.
-
notaz authored
allows to see messages from DRAM setup code.
-
notaz authored
zero variables (.bss) go to DRAM, non-zero (.data) go to SRAM in MLO.
-
notaz authored
-
- 26 Feb, 2017 1 commit
-
-
H. Nikolaus Schaller authored
Signed-off-by:
H. Nikolaus Schaller <hns@goldelico.com>
-