TBSDTV Community Forum

O.K. slowly I am getting forward. Now I have u-boot-2014 running with 2G RAM and networking

I have only managed to boot the normal 3.0.35 kernel. Guess, my dtb files are somehow borked. If I try to start a newer kernel, it always stops directly after "Starting the kernel...".

Btw. how to I flash the new u-boot so that it loads automatically without every time using imx-loader-usb?

Btw. Just found a nasty bug in the u-boot: When you enter "printenv netboot" (or any other very long variable), the CPU is resetted.

Hmm, one step further, and one step back:

I flashed the u-boot to the emmc. This works nicely. However, u-boot cannot save (probably not load either) the environment variables.

Code: Select all

=> saveenv
Saving Environment to MMC...
Card did not respond to voltage select!
MMC init failed


The mmc dev seems to be hard coded, I guess. The correct mmc dev is 2 (for the internal mmc), but it probably wants to use some other dev.

O.K. found the config here:
include/configs/mx6sabresd.h

change

Code: Select all

#define CONFIG_SYS_MMC_ENV_DEV          1       /* SDHC3 */

to

Code: Select all

#define CONFIG_SYS_MMC_ENV_DEV          2       /* SDHC3 */

then saving to MMC works

Yeah, looking very good so far. Managed to save u-boot-2014 to emmc and can tftpboot kernel and then nfs boot rootfs. Great!

So, now I'm stuck at the same problem mentioned before that teh 3.10 kernel oopses about 30 sec after boot.

Code: Select all

INFO: rcu_sched self-detected stall on CPU { 1}  (t=2100 jiffies g=4294967289 c=4294967288 q=274)
CPU: 1 PID: 25 Comm: kworker/1:1 Not tainted 3.10.173.10.17_beta+yocto+g9260843 #1
Workqueue: events rtc_timer_do_work
Backtrace:
[<80011d7c>] (dump_backtrace+0x0/0x110) from [<80011f94>] (show_stack+0x18/0x1c)
 r6:00ebc000 r5:807db780 r4:807c78a8 r3:807c73b0
...


Not sure if this is kernel or dtb related.
At least I can now easily test different kernels and dtbs easily.

Not sure, never tried. I load mine every time with imx_usb just cause I like to play around alot so its easier if its not writen to flash.

You should be able to use the TBS mfg restore util I would think.

UDL

updatelee wrote:Not sure, never tried. I load mine every time with imx_usb just cause I like to play around alot so its easier if its not writen to flash.

You should be able to use the TBS mfg restore util I would think.

UDL

I looked through the mfg restore scripts (it uses Linux) and it was pretty easy. It is written to /dev/mmcblk0 exactly the same way as to sdcard. One can do that when the Matrix is booted to any Linux distro.

Code: Select all

echo 0 > /sys/block/mmcblk0boot0/force_ro
dd if=u-boot-2014-matrix.imx of=/dev/mmcblk0boot0 bs=512 seek=2
sync
echo 1 > /sys/block/mmcblk0boot0/force_ro
echo 8 > /sys/devices/platform/sdhci-esdhc-imx.3/mmc_host/mmc0/mmc0:0001/boot_config


I hope that this u-boot is stable enough to not change it anymore. I rather have kernel and rootfs easily modified, and that is best done via tftpboot and nfs.

NeuerUser wrote:O.K. slowly I am getting forward. Now I have u-boot-2014 running with 2G RAM and networking

I have only managed to boot the normal 3.0.35 kernel. Guess, my dtb files are somehow borked. If I try to start a newer kernel, it always stops directly after "Starting the kernel...".

Btw. how to I flash the new u-boot so that it loads automatically without every time using imx-loader-usb?

can you post this u-boot.bin?
Thanks.

Can anyone post a flashable u-boot with functional networking?

Edit: I've done it myself. I've posted it here for others to use if they'd like:
https://github.com/l3iggs/tbs2910-from- ... ses/latest

Instructions on flashing from Linux are also there.

Is it absolutely necessary to use new uboot to load mainline kernel embedded in fdt blob from SD card ( stock uboot is missing FDT support? )?