- 30 Nov, 2012 2 commits
-
-
Vladimir Khusainov authored
- sf probe 0 - sf read a0000000 100000 f00000 reads a 15MB file into DDR for ~3sec.
-
Sergei Poselenov authored
UART0 and SPI in U-Boot. Use only with the respective .stp design!
-
- 29 Nov, 2012 1 commit
-
-
Yuri Tikhonov authored
Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
- 28 Nov, 2012 2 commits
-
-
Yuri Tikhonov authored
Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
- 27 Nov, 2012 1 commit
-
-
Yuri Tikhonov authored
Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
- 26 Nov, 2012 1 commit
-
-
Yuri Tikhonov authored
Signed-off-by:
Vadim Aleynikov <vadim_a@emcraft.com> Signed-off-by:
Alexander Potashev <aspotashev@emcraft.com> Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
- 23 Nov, 2012 6 commits
-
-
Alexander Potashev authored
-
Alexander Potashev authored
This is required for any code execution (including the Linux kernel) in the external RAM on SmartFusion2 (M2S).
-
Alexander Potashev authored
We will reuse this function on SmartFusion2 (M2S).
-
Yuri Tikhonov authored
There's no compatibility with A2F SPI now, so give the appropriate names to constants, and funtions. Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
In this case DDR Bridge buffering BUG isn't triggered. Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
- 21 Nov, 2012 1 commit
-
-
Yuri Tikhonov authored
We suspect some BUG in the buffering scheme. See RT records for details. Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
- 20 Nov, 2012 6 commits
-
-
Yuri Tikhonov authored
Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
This is to avoid slowing things down, when we'll switch to malloc in external mem. Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
This is more precise. Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
This allow to dramatically speed-up xfers on high SPI CLKs (previo- usly we got stuck at ~ 1MHz; higher clocks gave nothing because of program CPU execution latencies). Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Yuri Tikhonov authored
Use more compact macros to access reags instead of read/write. Signed-off-by:
Yuri Tikhonov <yur@emcraft.com>
-
Sergei Poselenov authored
Supported: - UART0 (57600) - SPI0 (non-DMA) - Ethernet - LPDDR - Env in SPI Flash
-
- 05 Nov, 2012 1 commit
-
-
Vladimir Khusainov authored
definition of CONFIG_MEM_NVM_UBOOT_OFF for those U-boot configuraitons that do not require that macro.
-
- 02 Nov, 2012 1 commit
-
-
Vladimir Khusainov authored
U-boot to run from eNVM at offset 0x20000: - to program that U-boot to eNVM: cptf 0x20000 ${loadaddr} ${filesize} 0 - to run that U-boot from eNVM: go 20375
-
- 02 Oct, 2012 1 commit
-
-
Sergei Poselenov authored
-
- 29 Aug, 2012 1 commit
-
-
Sergei Poselenov authored
are preformed manually, as per the test plan.
-
- 27 Jun, 2012 1 commit
-
-
Alexander Potashev authored
Take into account the delay t_{v(A_NE)} (4.5 ns) before the MCU outputs the chips select signal A[23].
-
- 25 Jun, 2012 1 commit
-
-
Alexander Potashev authored
* In order to switch the MCG to the PLL Engaged External mode (PEE mode), it must pass the FLL Bypassed External mode (FBE mode) as an intermediate step. See section `25.4.1 MCG Mode State Diagram` on page 656 of the K70 Reference Manual. * Enable and use the RTC clock for FLL when switching to the FLL Bypassed External mode (FBE mode). We do this in `clock_fei_to_fbe()` in `u-boot/cpu/arm_cortexm3/kinetis/clock.c` before switching to the FBE mode. This is required, because: * In order to switch to the PLL Engaged External mode (PEE mode), we must pass the FLL Bypassed External mode (FBE mode). * This FBE mode requires that there is a working FLL reference clock. * Only OSC0 clock (clock or oscillator at EXTAL0/XTAL0) or RTC clock (oscillator at EXTAL32/XTAL32) can be used as reference clock for FLL. * In the K**-SOM/DNI-ETH configuration, nothing is connected to EXTAL0, therefore we have to use the RTC clock as reference clock for FLL in the FBE mode. * Use RTC for FLL reference clock only on K**-SOMs, but not for TWR-K70F120M. To do that, we add a new U-Boot configuration option `KINETIS_FLLREF_RTC` that will control usage of RTC for FLL reference clock and define this configuration option only in `u-boot/include/configs/k70-som.h`. * Use in-MCU 20pF oscillator load.
-
- 18 Jun, 2012 2 commits
-
-
Alexander Potashev authored
* Use external oscillator at EXTAL1/XTAL1 as clock source for the main PLL on K70-SOM. * Do not change clock configuration for TWR-K70F120M.
-
Alexander Potashev authored
Either CONFIG_KINETIS_120MHZ or CONFIG_KINETIS_150MHZ must be defined. The TWR-K70F120M board has a 120MHz K70 MCU.
-
- 14 Jun, 2012 4 commits
-
-
Alexander Potashev authored
* Add build-time U-Boot option CONFIG_KINETIS_120MHZ or CONFIG_KINETIS_150MHZ to define the maximum core clock rate of the MCU. * Use different PLL configurations to reach to maximum clock rates and performance. * Use different LPDDR timings depending on the clock rate. * Use different clock dividers for internal flash and external NAND flash, as required by the respective datasheets.
-
Alexander Potashev authored
Kinetis K61 does not have an LCD controller.
-
Alexander Potashev authored
Increase NFC clock divider to put the NFC clock below rate limit. The maximum NFC clock rate (19.23MHz) was calculated as follows: 1. Assume we do not use NFC fractional divider, for simplicity. 2. Look at the "RANDOM DATA READ" diagram on page 86 of the NAND flash datasheet 5277m68a_1gb_nand.pdf and find out that data appear tREA nanoseconds after RE# goes low. tREA is 16ns, according to the Table 23: AC Characteristics: Norman Operation (3.3V) from page 78 of the NAND flash datasheet 5277m68a_1gb_nand.pdf . 3. Look at "Figure 14. Read data latch cycle timing in non-fast mode" on page 42 of the MCU datasheet K70P256M120SF3.pdf and find out that RE# must go high no later than tIS nanoseconds after the data has appeared. tIS is 11ns for both 120MHz- and 150MHz-limited K70 MCUs, see NFC specifications in the MCU datasheets: K70P256M120SF3.pdf and K70P256M150SF3.pdf. 4. Therefore the minimum RE# low pulse width is tREA + tIS = 16ns + 11ns = 27ns. 5. From the table Table 24. NFC specifications from the MCU datasheet K70P256M150SF3.pdf we can calculate the minimum T_L: NFC_RE# pulse width minimum value is T_L + 1 and is also 27ns, as already calculated. Therefore minimum T_L is 26ns. 6. Since we assume the NFC clock divider to be integer, the NFC clock duty cycle is 50%, therefore T_L is half of the clock cycle. Maximum NFC clock rate is therefore 1.0/2/26ns = 0.01923 GHz = 19.23 MHz.
-
Alexander Potashev authored
These strings will follow the selection of CONFIG_KINETIS_K61 or CONFIG_KINETIS_K70: 1. Hostname; 2. U-Boot prompt; 3. `platform_kinetis=[...]` in kernel parameters line; 4. Board name.
-
- 13 Jun, 2012 2 commits
-
-
Sergei Poselenov authored
-
Sergei Poselenov authored
are used in cmd_somtest.c module.
-
- 07 Jun, 2012 1 commit
-
-
Sergei Poselenov authored
-
- 05 Jun, 2012 1 commit
-
-
Alexander Potashev authored
Modify timings to support -6 LPDDR parts along with -5 parts.
-
- 30 May, 2012 1 commit
-
-
Vladimir Khusainov authored
-
- 23 May, 2012 3 commits
-
-
Sergei Poselenov authored
-
Sergei Poselenov authored
Actel board (the "Read Array" command there is 0xFF, not 0xF0).
-
Alexander Potashev authored
* Add Makefile target `lpc1850-eval_config`. * Set the system prompt to `LPC1850-EVAL> `. * Change CONFIG_MEM_NVM_LEN from 128 KBytes to 96 KBytes to match the size of the largest continuous region of internal SRAM on LPC1850. * Adjust clock configuration for the 180MHz maximum core clock rate on LPC1850: set the PLL1 multiplier value to 15. * Adjust SDRAM timings for the 180MHz maximum core clock rate on LPC1850. * Adjust NOR flash timings for the 180MHz maximum core clock rate on LPC1850. * Change default MAC address and IP address of the board defined in the U-Boot environment.
-