Deployment instructions for samples are incomplete

[jt-se]

Description

The instructions are good up until the final step, when they just... stop 😅

(I see the latest commits are fairly recent, so I assume this is just a work in progress)

Code

project-ocre.github.io/docs/samples/hello-world/index.md

Lines 38 to 43 in 3c79bdf

	The following steps will guide you to deploy the hello world sample to your device.
	1. To deploy the hello world sample, simply run the following in your terminal:
	```
	example code
	```

Setup

I followed the development environment setup instructions to use the devcontainer workspace. ✔️

I followed the instructions to set up a simulated device inside the development environment, and was able to run the ocre runtime. ✔

(.venv) vscode ➜ /workspaces/getting-started/runtime (main) $ ./build/zephyr/zephyr.exe 
WARNING: Using a test - not safe - entropy source
uart_1 connected to pseudotty: /dev/pts/1
*** Booting Zephyr OS build v4.0.0-rc1-10-gafce5329f772 ***
I: /lfs mount: 0

D: /lfs: bsize = 16 ; frsize = 4096 ; blocks = 30 ; bfree = 28


Ocre runtime started
I: Request create new container in slot:0
I: Request run container in slot:0
I: EVENT_CREATE_CONTAINER
I: File path: /lfs/ocre/images/hello.bin, size: 323
I: Loaded binary to buffer for container 0
I: Created container in slot:0
Hello World!
I: Started container in slot:0

ocre:~$

How do I go about deploying the compiled app (hello-world.nbx) onto the virtual Zephyr device? I see that it's running another hello-world "app", but it's not the WebAssembly-compiled container image.

Other

These instructions appear to be incomplete in the getting-started repository also. (Sorry if this issue is being reported in the wrong place.)

[ChrisProlls]

Same comment for me 👍
I wanted to give to Ocre a try with my ESP32 Espressif board but the docs stop when it became exciting !
(I used that part of the docs : https://docs.project-ocre.org/quickstart/first-app/first-container/)
Any news on the next step ?

[gonzolively]

Hi @ChrisProlls! (and @jt-se)

First, @jt-se , I'm so sorry I never replied to this issue. I categorized it and put it on the roadmap, but never replied!

Yes, unfortunately, you both are correct. As of now, the tooling required to load and run Ocre containers on the ocre-runtime is not in the repo. We're currently in conversation around designing these tools — i.e., what is needed, functionality, etc — and hopefully we'll start development on that soon. I'll keep this issue open to track any updates to this progress. Until then, see the workaround at the bottom of this issue!

Workaround

Not ideal, but in src/main.c you'll see a byte array (wasm_binary) that is essentially a hardcoded byte array of an actual WASM container. You can create your own WASM container, convert it to hex, and replace that array. Again, terrible workflow,w but it will work in the interim!

[jt-se]

First, @jt-se , I'm so sorry I never replied to this issue. I categorized it and put it on the roadmap, but never replied!

No worries. I appreciate the response, nonetheless.

Workaround

Not ideal, but in src/main.c you'll see a byte array (wasm_binary) that is essentially a hardcoded byte array of an actual WASM container. You can create your own WASM container, convert it to hex, and replace that array. Again, terrible workflow,w but it will work in the interim!

Thanks for this! I'll give it a try when I have a chance.

[ChrisProlls]

Thanks for the answer, no worries about work in progress ;)
I'll give it a try too !