You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the image on the gnubee itself an image is created, but when booting it stops after "verifying checksum". Cross compiling just works.
Didn't yet analyze where the problem lies, but since it doesn't even start the image I would say it's the generated kernel.
Will test it later by replacing the kernel with a cross compiled kernel (don't know yet when).
The text was updated successfully, but these errors were encountered:
(Sorry for the delay).
I don't understand that last comment. The images linked there not lot related to this gnubee-tools package ... except that they are used on the same hardware.
Or are you saying that you installed those firmware images, then used gnubee-tool running on those images to build a new firmware image? That would be somewhat interesting, but not something that I want to spend any time on as those are very old images and I would likely just find there is something missing there.
If you cross-compile a firmware image with gnubee-tools, then boot the gnubee and build a new image natively there - and that doesn't work. Then I would be interested.
When building the image on the gnubee itself an image is created, but when booting it stops after "verifying checksum". Cross compiling just works.
Didn't yet analyze where the problem lies, but since it doesn't even start the image I would say it's the generated kernel.
Will test it later by replacing the kernel with a cross compiled kernel (don't know yet when).
The text was updated successfully, but these errors were encountered: