-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uBoot bootargs are missing and can't boot #7
Comments
You just need to load the kernel into memory from ubi and jump to it. I don't think sf is meant for spi nand. bootargs is you kernel commandline. You should tell it what to mount as root there. saveenv should work too. But maybe if you use the sf command it breaks things. |
I have tried with As I have tried this
But it hangs when needs to load
|
I have tried
and uploaded via recovery and load it via
|
Can you see if you can read out the rootfs you've written in the rescue image? |
So I have managed to update kernel to support
and now I can mount it in rescue mode
and full list of mounted dir
also unmounting works normally
so I'm certain that ubifs image creation is valid and works as it should |
Stick |
OMG that WORKED SOM2D01 now can boot stand-alone without issues with this
Thanks a lot for help but curious why do we need that |
At the line it was getting stuck the kernel is disabling clocks of hardware it thinks are unused. If a clock is actually being used that can cause the system to lock up. Right now we need that because we don't have a perfect clock driver that knows the complete clock tree and the dependencies. That parameter should be in the bootargs in the devicetree but if you override the bootargs from u-boot it's needed there too.
Create an MD file so it's part of the repo |
Closing as is resolved and will all be documented in md file soon |
Opening this issue for making together uBoot
bootargs
as after rescue kernel and uBoot are flashed to SPI NAND device can't boot standaloneThere is already some people in issue #5 that have same issues and this is not resolved
I have extracted from original SDK
bootargs
And as we don't need most of this stuff we would need new one that will make us boot normally
1st issue I got in uBoot is no support for
nand
access and we have to do it withubi
so original will not be a lot of helpIf you query from uBoot
ubi info
So we can see UBI just need to adjust some things as is suggested in #5 by @fifteenhex but I don't know how to save in this case
I have tried
sf probe0
andsaveenv
but that just frooze and did nothingAlso do we need to separate
bootcmd
andbootargs
? or we could use it as one?The text was updated successfully, but these errors were encountered: