fficult to get working as the majority if not all
mainlined board use dual channel RAM.
Sorry I can't be more help, but trying to use the DDR blob is a good
starting point to get you going on mainline.
Good Luck!
--
Jack Mitchell, Consultant
https://www.tuxable.co.uk
t; Please let me know if you need help to test this.
>
> Thanks,
> Alistair.
>
Hi Alistair,
You need the following patch:
https://patchwork.ozlabs.org/project/uboot/patch/20211101044347.17822-1-yifeng.z...@rock-chips.com/
Please let me know if this fixes the issue for you as some people still
On 02/11/2021 08:02, Peter Robinson wrote:
> On Mon, Nov 1, 2021 at 10:32 PM Jack Mitchell wrote:
>>
>> On 01/11/2021 22:11, Peter Robinson wrote:
>>> On Mon, Nov 1, 2021 at 11:18 AM Jack Mitchell wrote:
>>>>
>>>> On 01/11/2021 09:07, Alper N
On 01/11/2021 22:11, Peter Robinson wrote:
> On Mon, Nov 1, 2021 at 11:18 AM Jack Mitchell wrote:
>>
>> On 01/11/2021 09:07, Alper Nebi Yasak wrote:
>>> I'm trying to make my gru-kevin's eMMC work properly (it times out while
>>> tuning for HS400 and st
i.c | 51 ++++
> drivers/mmc/sdhci.c | 18 +
> include/sdhci.h | 1 +
> 3 files changed, 70 insertions(+)
>
--
Jack Mitchell, Consultant
https://www.tuxable.co.uk
gt;
> return 0;
> }
> @@ -101,19 +333,28 @@ static int rockchip_sdhci_bind(struct udevice *dev)
> return sdhci_bind(dev, &plat->mmc, &plat->cfg);
> }
>
> -static const struct udevice_id arasan_sdhci_ids[] = {
> - { .compatible = "arasan,sdhci-5.1" },
> +static const struct sdhci_data rk3399_data = {
> + .emmc_set_clock = rk3399_sdhci_emmc_set_clock,
> + .get_phy = rk3399_emmc_get_phy,
> + .emmc_phy_init = rk3399_emmc_phy_init,
> +};
> +
> +static const struct udevice_id sdhci_ids[] = {
> + {
> + .compatible = "arasan,sdhci-5.1",
> + .data = (ulong)&rk3399_data,
> + },
> { }
> };
>
> U_BOOT_DRIVER(arasan_sdhci_drv) = {
> - .name = "rockchip_rk3399_sdhci_5_1",
> + .name = "rockchip_sdhci_5_1",
> .id = UCLASS_MMC,
> - .of_match = arasan_sdhci_ids,
> - .of_to_plat = arasan_sdhci_of_to_plat,
> + .of_match = sdhci_ids,
> + .of_to_plat = rockchip_sdhci_of_to_plat,
> .ops= &sdhci_ops,
> .bind = rockchip_sdhci_bind,
> - .probe = arasan_sdhci_probe,
> + .probe = rockchip_sdhci_probe,
> .priv_auto = sizeof(struct rockchip_sdhc),
> .plat_auto = sizeof(struct rockchip_sdhc_plat),
> };
>
--
Jack Mitchell, Consultant
https://www.tuxable.co.uk
ying to boot from MMC2
> Card did not respond to voltage select! : -110
> spl: mmc init failed with error: -95
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>
Hi Tomasz,
I'm hitting the same issue with a custom 3399 based
On 23/09/2020 19:23, Tom Rini wrote:
> This converts the following to Kconfig:
>CONFIG_WATCHDOG
>CONFIG_WATCHDOG_TIMEOUT
>CONFIG_WDT
>CONFIG_HW_WATCHDOG
>CONFIG_DESIGNWARE_WATCHDOG
>
> Signed-off-by: Tom Rini
Before setting this in stone, after much recent personal confusio
In order to correctly calculate the designware watchdog
timeouts, the watchdog clock is required. Implement required
clocks to facilitate this.
Signed-off-by: Jack Mitchell
---
drivers/clk/rockchip/clk_rk3399.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers
The timeout calculation is based on the clk being in KHz but
the clk api returns the clk value in Hz. Convert this to KHz
to calculate the correct timeout value.
Signed-off-by: Jack Mitchell
---
drivers/watchdog/designware_wdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 23/04/2020 12:38, Jagan Teki wrote:
> On Tue, Apr 21, 2020 at 7:54 PM Jack Mitchell wrote:
>>
>> Has anyone worked with an rk3399 based board with a single channel RAM
>> setup? I've looked at the current code and made some changes for only
>> setting up
Has anyone worked with an rk3399 based board with a single channel RAM
setup? I've looked at the current code and made some changes for only
setting up a single channel which basically consists of altering the
loops down to one channel, however u-boot is hanging while checking for
a successful freq
Looking at the original commit
https://lists.denx.de/pipermail/u-boot/2014-June/181599.html
It looks like it puts the result into the variable $filesize just as the
other commands which read files do.
Regards,
Jack.
On 26/09/2019 08:27, Adarsh Babu Kalepalli wrote:
> Hello,
>
> Commands "size
Hi,
On 25/04/2019 18:54, Jagan Teki wrote:
> Rockchip platform would require an explicit call to mkimage for
> creating bootable images which indeed specific to SoC family
> along with boot devices.
>
> Example of creating bootable image for rk3399 family with SD
> boot device as
>
> ₹ mkimage -
On 11/04/2019 01:16, U.Mutlu wrote:
> # CC Jagan
>
> There's a version mismatch error with the sunxi-fel tool from sunxi-tools
> ( https://github.com/linux-sunxi/sunxi-tools )
>
> ./sunxi-fel -v uboot u-boot-sunxi-with-spl.bin write 0x4310 my.env
> Stack pointers: sp_irq=0x2000, sp=0x
Hi,
On 03/04/2019 10:34, Urja Rannikko wrote:
> This affects RK3036, RK322X and RK3288 - the defconfig changes done by
> moveconfig.py for the veyrons were left out on purpose because they dont
> have an OTG port, and will get their config updated in the next commit.
>
> Signed-off-by: Urja Ranni
On 02/04/2019 21:59, Adam Ford wrote:
> I have a board with eMMC storage. I've been trying to find an elegant
> solution to burning the sdcard image to eMMC. I looked at using the
> USB mass storage gadget, but it's a bit slow. I was hoping to avoid
> having to boot all the way into Linux to do
On 01/04/2019 13:57, Lukasz Majewski wrote:
> Hi Anand,
>
>> From: Tobias Jakobi
>>
>> Rename board_usb_init() to exynos_usb_init() and call it
>> early in the Exynos EHCI driver when probing.
>>
>> This kind of works. After a 'usb start; usb stop; usb start'
>> cycle the attached devices are r
On 01/04/2019 10:49, Patrick DELAUNAY wrote:
>> From: Jack Mitchell
>> Sent: samedi 30 mars 2019 12:42
>>
>> On 29/03/2019 14:42, Patrick Delaunay wrote:
>>> This patch-set created after Marek remarks on patch
>>> board: stm32mp1: Add tx_fifo_sz_array
On 29/03/2019 14:42, Patrick Delaunay wrote:
>
> This patch-set created after Marek remarks on patch
> board: stm32mp1: Add tx_fifo_sz_array support
> http://patchwork.ozlabs.org/patch/1056452/
>
> This serie convert the DWC2 to driver model and use it for the
> stm32mp1 boards.
>
> USB de
On 29/03/2019 01:09, Kever Yang wrote:
> Use board_debug_uart_init() for UART iomux init instead of
> do it in board_init_f, and move the function to soc file so
> that we can find all the soc/board setting in soc file and
> use a common board file for all rockchip SoCs later.
>
> Signed-off-by:
On 29/03/2019 01:09, Kever Yang wrote:
> Use board_debug_uart_init() for UART iomux init instead of
> do it in board_init_f, and move the function to soc file so
> that we can find all the soc/board setting in soc file and
> use a common board file.
>
> Signed-off-by: Kever Yang
> ---
>
> arc
On 16/03/2019 14:07, g...@novadsp.com wrote:
> Greetings
>
> Our board has an AllWinner H5 with SPI flash and eMMC. Since SPI flash
> support for 'saveenv' is not currently mainline, I thought I'd simply use
> one of the eMMC boot blocks to persist the environment. However I keep
> running into im
On 09/02/2019 12:12, Heinrich Schuchardt wrote:
> Hello Simon, hello Philipp,
>
> since patch
>
> Merge tag 'for-master-20190201' of git://git.denx.de/u-boot-rockchip
> e5fd39c886485e3dec77f4438a6e364c2987cf5f
>
> booting on the Tinker Board (tinker-rk3288_defconfig) is broken.
>
> There is not
On 21/01/2019 17:55, Jack Mitchell wrote:
> Hi,
>
> Has anyone successfully used DFU on an rk3288 or dwc2_otg based board?
> When trying to download a binary to the board over DFU it currently
> seems to timeout and the transfer fails. I have tested the
> firefly-rk3288 and al
On 21/01/2019 17:55, Jack Mitchell wrote:
> Hi,
>
> Has anyone successfully used DFU on an rk3288 or dwc2_otg based board?
> When trying to download a binary to the board over DFU it currently
> seems to timeout and the transfer fails. I have tested the
> firefly-rk3288 and al
Hi,
Has anyone successfully used DFU on an rk3288 or dwc2_otg based board?
When trying to download a binary to the board over DFU it currently
seems to timeout and the transfer fails. I have tested the
firefly-rk3288 and also the Tinkerboard.
I have successfully used the same setup on an am335x b
On 15/01/2019 02:05, Kever Yang wrote:
> HI Jack,
>
>
> On 01/15/2019 01:28 AM, Jack Mitchell wrote:
>> I'm having issues flashing the emmc on my firefly board using USB. For
>> some reason it seems as though trying to write to the emmc flash sector
>> 0x40 fo
I'm having issues flashing the emmc on my firefly board using USB. For
some reason it seems as though trying to write to the emmc flash sector
0x40 for uboot spl+proper from the Maskrom/Loader doesn't work. Can
anyone elaborate on what I'm doing wrong, or another way I could achieve
this?
The curr
On 22/11/2018 21:12, Richard Röjfors wrote:
> It does not make sense to allow disable of a regulator that
> is defined always on.
>
> I found this because the new mmc code that tests if the mmc
> power can be switched off. That results in the rk3288
> firefly board to die since the regulator, whic
le(dev, enable);
> }
>
>
Another ping for this, I've just spent a few hours this morning
debugging the firefly-rk3288 failing to boot due to a required regulator
being disabled in the emmc reset routine. I came up with almost the
exact same patch, so
Reviewed-by: Jack Mitchell
le(dev, enable);
> }
>
>
Another ping for this, I've just spent a few hours this morning
debugging the firefly-rk3288 failing to boot due to a required regulator
being disabled in the emmc reset routine. I came up with almost the
exact same patch, so
Reviewed-by: Jack Mitchell
le(dev, enable);
> }
>
>
Another ping for this, I've just spent a few hours this morning
debugging the firefly-rk3288 failing to boot due to a required regulator
being disabled in the emmc reset routine. I came up with almost the
exact same patch, so
Reviewed-by: Jack Mitchell
On 17/07/13 08:11, Albert ARIBAUD wrote:
Hi Jack,
On Tue, 16 Jul 2013 14:44:22 +0100, Jack Mitchell
wrote:
Fighting with compiling u-boot today and dealing with problems related
to using a custom built openembedded toolchain, I found the need to
specify a custom location for the GCC lib
From: Jack Mitchell
Add support for defining the gcc lib in standalone examples as is
done in the main u-boot Makefile
Signed-off-by: Jack Mitchell
---
examples/standalone/Makefile | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/examples/standalone
support for a custom GCC lib
in the standalone examples Makefile.
I am no toolchain or u-boot expert, and as such to avoid the firey pits
of flamewar hell, this is an RFC ;)
--
Jack Mitchell (j...@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
36 matches
Mail list logo
