-
Notifications
You must be signed in to change notification settings - Fork 49
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
Data folder is not flashed using Coral Dev Micro + Wireless Add-on board #47
Comments
please refer to this comment: google-coral/coralmicro-out-of-tree-sample#6 (comment) |
Hi, I confirm this bug.
I note the tags of this issue, and I suggest to change them, since it does not work regardless of the platform (I am using MacOS and Linux, the original reported of this issue Windows, and it is normal that this cannot work regardless of the platform). Regards |
It seems with a few modifications to the boards.txt and platform.txt this can be remedied, by implementing the below approach:
We have documented this on this page, with the changes needed also below. Boards.txt: Platform.txt: We will create a Pull Request for this if there are no objections. |
Description
Good afternoon,
I'm trying to create a simple HTTP server using Wi-Fi (and the add-on board). Code flashing is fine, but I suspect the /data files in the project are not being flashed to the board when the Dev Board Micro + Wireless Add-on is set on Arduino IDE.
Using the normal Dev Board Micro flashing the server works as intended, because the /data folder is flashed correctly.
Everytime I'm flashing using Sketch+Data option:
I'll put the code I'm using and the flash logs for both boards below.
Dev Board Micro + Wireless Add-on -> CameraStreamingHttp using WiFi
Dev Board Micro -> CameraStreamingHttp without WiFi.zip
Is there something missing in Arduino IDE to flash the /data folder together?
Click to expand!
Issue Type
Bug
Operating System
Windows 10
Coral Device
Dev Board Micro
Other Devices
No response
Programming Language
C++
Relevant Log Output
The text was updated successfully, but these errors were encountered: