FireFly RK3288 not booting

We’re glad to hear everything is fine. All the best and let us know if you need any help!

Hi @jviotti
How can add this Custom device to balenaCloud.
this is armv7 - can i follow below link to add as generic-aarch64

Hello, I think you found the correct CLI issue, but Im afraid generic-aarch64 wont work for armv7. Im asking the team what the procedure to create a generic device type for that would be. Will get back to you as soon as we have an update

Hi @karthi . If the SOC and BSP layer is the same, I would recommend adding your Firefly device as “Community” contributed device (documentation here: https://www.balena.io/docs/reference/hardware/versioning/#community ) which we would then work with you to have that board show up in the dashboard. For testing, I would suggest just grabbing a config.json from the ASUS app and provisioning them in there.

Hi @shaunmulligan

I will asus tinker boards config for now. right now I am setting up the github repo for RK3288. once done, i will make it public.

@alexgg @ErikHH Meanwhile please answer this post as well Custom imx6ull board

That would be awesome @karthi. Let us know once you have that!

I have used have setup yocto for this board (I just used ASUS Tinker S as reference ).

Hi @shaunmulligan @tmigone

Here is git repo, We have ported and tested the devices. Please add this to community devices

Thanks
KarthiG

Hi, we are discussing this internally. Will let you know once we have results. Thank you for the contribution!

Hi @karthi, thank you so much for the contribution and sorry for the late response. This is the first time we have had a fully external repo contribution for a community device type, all the others have been part of already existing repos we own in our github orgs. So we have had to think about how to include this in our workflows. What we propose is that we make a fork of your repo ( https://github.com/clodpi/balena-rockchip-rk3288 ) in our balena-os organisation, this will allow us to build and release images. Then whenever you have new updates or fixes, our downstream fork can consume those updates.

One note here is that you will need to be responsible for notifying our team to pull in the updates and trigger the new releases. The testing and support (including other users issues) of this device type will have to be undertaken by you as we don’t have the hardware (or team resources currently) to do so. Also notice that if Community boards are seen to not be maintained by the contributor for more than 6 months, we will discontinue the device type.

If all of the above sounds good to you, we will start the process of setting up the repo and doing the deployment. Let us know if you are happy and we can get it rolling. Once again, thank you very much for the contribution!!

@shaunmulligan looks good thanks

Hey @karthi I have forked the repo here: https://github.com/balena-os/balena-rockchip-rk3288 and we will be working on putting it into staging and then production in the next few days. With this repo, you can ping our team whenever you have new PRs for fixes to pull in and we will include them from your upstream repo.

Hi @karthi , I noticed meta-balena is at an older version v2.38.3 in your repository. If you wish, you can update BalenaOS before we put the images in the dashboard. Please let us know if you want the current 2.38.3 version, or you will update to a newer one.

A balenaOS update commit example would be: https://github.com/clodpi/balena-rockchip-rk3288/commit/6573ef1139d9ccbd37ba5338562670f34facebec

hi @acostach,

I have tested the 2.38.3 version and its working fine. for now you can put 2.38.3, Later I will update and let you know.

Thanks
KarthiG

Hi @karthi,

The images for your boards are now deployed and can be downloaded from the dashboard.

Thank you for your contribution!

thanks @acostach, We are working 2 more boards will make it public once done (IMX and ST)

Sounds great! Let us know when they’re ready and we’ll make sure they get to the dashboard

hi @karthi,

I’m trying to build the balena-rockchip-rk3288 image. I checked out the repository (with all submodules), but when I run the barys script I always get the error:

| make[2]: Entering directory '/home/osboxes/balena/balena-rockchip-rk3288/build/tmp/work/x86_64-linux/bison-native/3.0.4-r0/build'
| gcc     -I. -I./lib -I../bison-3.0.4 -I../bison-3.0.4/lib -isystem/home/osboxes/balena/balena-rockchip-rk3288/build/tmp/work/x86_64-linux/bison-native/3.0.4-r0/recipe-sysroot-native/usr/include  -isystem/home/osboxes/balena/balena-rockchip-rk3288/build/tmp/work/x86_64-linux/bison-native/3.0.4-r0/recipe-sysroot-native/usr/include -O2 -pipe -c -o lib/fseterr.o ../bison-3.0.4/lib/fseterr.c
| ../bison-3.0.4/lib/fseterr.c: In function 'fseterr':
| ../bison-3.0.4/lib/fseterr.c:77:3: error: #error "Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib."
|    77 |  #error "Please port gnulib fseterr.c to your platform! Look at the definitions of ferror and clearerr on your system, then report this to bug-gnulib."

How can I fix this error?

My goal is to build an image for a rk3188 chip and want to use your work on the rk3288 as starting point.

Thanks.

Hello,
we tried to download the img file from Balena website and install it on a Firefly 3288c device, but we couldn’t even find the way to install the OS.
The device does not even let us boot from USB, and the flashing tool from Firefly (Androidtool) does not recognize the IMG file downloaded from Balena.
We are able to install Android or Ubuntu, but couldn’t find a way to install Balena.
Any suggestion on how can we install it?

Hi @karthi , I’ve opened a ticket in your github integration repository regarding the necessity of a Yocto update for the balenaOS integration, could you please take a look and let me know? The ticket is Update yocto for balenaOS integration · Issue #3 · clodpi/balena-rockchip-rk3288 · GitHub

Thank you and please let me know if you are able to do the update so we can release newer images for these devices.