But when using our new firmware (suppose to have the same implementation) it does not work well. Any command will just make reboot the hardware and loose their state.
Can someone help us? Please? We can try to make a call or chat if required to close all our topics at once.
Hi Ricardo, regarding the firmware issue I will ping someone on the team to help with that.
For the second issue, it looks like the .git directory is not being uploaded to the builder. Do you have a .dockerignore file on your project directory?
You might get it to build on the builder but you would have to make some changes as I think the .git folder is ignored by balena CLI, and the CMD instruction on the dockerfile is intended to run make on a local volume so it won’t be very helpful as is to push this image to a device.
I already try to build using local docker (as you can see in the begin of this thread) but the hex simply doesn’t work when flash. Therefore I try to gave a shot by building in the device itself without luck.
Our goal is: to be able to compile a firmware and flash. And seems the supported github isn’t ok.
I understand, unfortunately you won’t get the file to build on device doing balena push which builds on our build server.
Looking at the build logs you shared and your message at the beginning of the thread I understand that you can build and flash the firmware in the balena-fin-coprocessor-firmata repository without issues, is that correct?
Is your custom firmware based on the source in balena-fin-coprocessor-firmata? Are you using the tools in that repository to build your custom firmware?
Is there anything else you can tell us about your custom firmware that might help us better diagnose the cause of the issue?
But after flash, the behaviour is not right. It reboots when calling any of the firmware commands using the firmware that was build straight from the balena-fin-coprocessor-firmata repository.
When re-flashing with the older version (firmware 2.0.1) everything gets back to normal. So is something wrong in the balena-fin-coprocessor-firmata repository that is not ok for balena 1.1.1
Hey @ricardoosorio, while we investigate the issue with the v3.0.x release of firmata, could you try basing your changes on the v2.0.1 tagged release for now? This one we know to be stable and would be best for your changes.