chargebyte/chargebyte-bsp

Wrapper for chargebyte GmbH's Yocto BSP and distribution

chargebyte-bsp's Issues

Cannot build NodeJs for EvachargeSE

Hello everybody,

I've been exploring Everest's features and am working on an EvachargeSE. I'm currently facing an issue building nodeJs (v16.20.2) because of the EvachargeSE CPU architecture, which doesn't seem to be supported.

Is there a way around this? Or perhaps a different version of nodeJs that can be built under Yocto Kirkstone?

Flash built image to EvachargeSE

Hello there,

Thanks to your repo, I can create an image for the Evacharge, however I don't now how to flash the image to the board.
While I can use the provided mfgtools to flash the image that generated by stib, here we have different structure the output.
Could you please share how to flash the yocto image on the board ?

Huy Truong,

repo sync does not work as expected

Hey guys,

we found a minor issue with the interaction between repo sync and the manifest. It seems that if we edit the default.xml manifest and then we issue repo sync, repo will fetch the manifest that is currently set in this repository and wont use the one we locally had modified. The solution we found was to specify the manifest file we wanted to use for the sync with repo sync -m default.xml.

Is this the expected behaviour of repo? I would not expect we needed to specify the manifest file.