This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Kernel debug. Using the UART
#21
Yeah, great! I did it. I got the u-boot shell via uart3, can interrupt it and do anything. But I can't save any changes. I run "setenv bootdelay 10" for example, after that "saveenv", I do reboot and my bootdelay still 1 sec by default, so my question is - how can I save the changes ? Smile
Reply
#22
(12-10-2018, 12:23 PM)yandex Wrote: so my question is - how can I save the changes ?

That's a u-boot matter, which leads to recompile it with different options. So u-boot allows to set several configurable options. When using a pre-compile u-boot there's a chance that some option is not there. In linaro there's the option to use the overlay file to add new hardware and device-tree definitions for that, without to recompile.
In Armbian there's a different mode to boot from a small compiled script,  boot.scr, which contains several instruction at the same manner you found on the u-boot interactive shell. Then there's also the opportunity to add more files containing other scripts.

So by default the u-boot is looking for a certain type of file system, or to find the way to boot over ethernet, or USB media, or local media which might contain a extlinux.conf or boot.scr. But if you expect something custom, then fold your sleeve and go to compile your own u-boot.

Then you might get started by the default configuration and later you may browse over the configuration options to see that there's is also the way to store your own environment variables.

I can't recall all the steps, by now, but you may find some post on the forum which explain how to get on the compilation routines. Then at certain point you can get the rk3288-def_config to start from, later you might start make menuconfig and you are there to see all the available options. First just study something before changing, but even you compile a wrong u-boot, you may have a chance to revert to the previous one, because you got some experience.
Light blue words might be a link. Have you try to click on them? Big Grin
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)