-
Notifications
You must be signed in to change notification settings - Fork 4
USB image for Gx6605s development board #96
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
Comments
I thought the current master branch have removed the support. I generated the image from older commit. |
@aisk: could you please mention the commit you are using for generating image?because I have the same problem with the master branch! |
@Dizgah I forked this repo on their gitlab mirror, which the maintainer run CIs to produced the binaries, and re-trigger the CI to get the binaries. This pipeline is the last commit which contains the USB image: https://gitlab.com/epoll/buildroot/-/pipelines/155882660 . |
@aisk, Thank you so much, I'm going to test it, but I have no idea why there are so many differences between the master and master_backup branch! While (same as usual) the master is the main release branch, there is nothing related to post-image for generating usb.img there and even it doesn't mention anywhere! |
@aisk Thanks for feedback |
@Dizgah I have no idea too 😢 |
@aisk even building based on the commit mentioned by you I don't have the image file.
I used csky_610_gx6605s_4.9_uclibc_br_defconfig configuration because I found it the only one related( Also I log the output to the build.log).
it's similar to the output based on the last commit on master_backup branch.
As you can see there are no rootfs.ext2 nor uImage in the output directory using b6cc3bd7 commit. |
@Dizgah I'm not dig into this, but I think maybe there was some steps which is runned by the gitlab ci runner, maybe you can check the gitlab config. @mtuxpe Hi I think this repo is used as a forum, not a regular git repo, so maybe we should keep this issue open, for maybe we can help someone in future? |
could you please mention commands you are using for building your image? and the content of the result output directory?
|
@Dizgah I have not running any command, just re-triggered the gitlab pipeline. The commands should be in |
@aisk thank you for clearing me, I am not experienced with Gitlab, then could you please explain to me how can I retriger that pipeline? |
Sorry, I'm not maitainer of this repo. |
@Dizgah I wrote a blog post for how to build the image: https://aisk.github.io/posts/build-csky-gx6605s.html |
I am trying to build a new USB image for Gx6605s development board:
git clone https://github.com/c-sky/buildroot.git
cd buildroot
git checkout e61b2fbafe1c53237ea3f9b0c57d6ae795e2027f
make CONF=thead_610_compat_next_glibc_br_defconfig
cd thead_610_compat_next_glibc_br_defconfig
make
After build :
ls -al images
-rw-r--r-- 1 msam msam 5285112 ago 18 08:44 Image
-rw-r--r-- 1 msam msam 243740 ago 18 08:39 linux-4.9.56.patch.xz
-rw-r--r-- 1 msam msam 3824 ago 18 08:32 readme.txt
-rw-r--r-- 1 msam msam 314572800 ago 18 09:01 rootfs.ext2
-rw-r--r-- 1 msam msam 20377600 ago 18 09:01 rootfs.tar
-rw-r--r-- 1 msam msam 76904368 ago 18 08:57 toolchain_thead_610_compat_4.9_glibc_br_defconfig_e61b2fbafe1c53237ea3f9b0c57d6ae795e2027f.tar.xz
What is the command line for manually generating USB image?
Or:
What is the setting on file thead_610_compat_next_glibc_br_defconfig to generate an USB image automatically?
The text was updated successfully, but these errors were encountered: