diff options
author | Judah Fuller <[email protected]> | 2023-07-18 08:00:31 +0100 |
---|---|---|
committer | Judah Fuller <[email protected]> | 2023-07-18 08:00:31 +0100 |
commit | 8b2a129b52de685e8ceda860eb4c7f1bca9161da (patch) | |
tree | b253bb4d9263509643419fe5dbc7c5c8f3326b01 /CorOS-dev-environment | |
parent | e33ce60b3195cfe6a3a9cf5e94a0fbb184b0b0bb (diff) | |
download | OpenCortex-8b2a129b52de685e8ceda860eb4c7f1bca9161da.tar.gz OpenCortex-8b2a129b52de685e8ceda860eb4c7f1bca9161da.zip |
Add cortex emu to M1, fix MDLint errors
Diffstat (limited to 'CorOS-dev-environment')
-rw-r--r-- | CorOS-dev-environment/README.md | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/CorOS-dev-environment/README.md b/CorOS-dev-environment/README.md index e01f271..d2f1e24 100644 --- a/CorOS-dev-environment/README.md +++ b/CorOS-dev-environment/README.md @@ -4,7 +4,7 @@ You can use the Python tool for downloading the latest firmware. You can find it in this repository under the `Firmware-download` folder. This will download the latest CorOS version from the official NeuralDSP server. -***[Alternative] The old way*** +**_[Alternative] The old way_** The update process of the QC is done in 2 steps. First the download, after that the install. We can use this to our advantage to grab the actual update file. Once you downloaded the update **do not install it yet.** Get an SSH shell going and go to `/media/p4`. There you will find your update file. A registry of these file names is also available inside the `filesystems/README.md` of this folder. @@ -16,11 +16,11 @@ Once you've got the update file, you can put it inside the `filesystems` directo **The easier** way is to use `docker compose`. In the `docker-compose.yaml` file, all volumes are already defined. This means you only have to define the update file in the `environment` section. -**[Click here for ARM and M1](#Running-On-M1)** +**[Click here for ARM and M1](#running-on-m1)** To use this first run the service in detached mode. **Make sure to build the CorOS-emulation container first if you want to use the CorOS-build-env one!** -``` +```bash docker compose up -d --build ``` @@ -28,14 +28,15 @@ After that you can attach to the container using Docker Desktop and running the If Docker Desktop isn't your cup of tea, you can always do it the CLI way. First identify the container by running `docker ps` and look for your `opencortex/coros-<target>:latest` containers. -``` +```bash CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES e94bc7cd6045 opencortex/coros-emu:latest "/bin/bash -c 'while…" 5 minutes ago Up 5 minutes coros-emulation-coros-emu-1 a81a4c3249c9 opencortex/coros-dev:latest "/bin/bash -c 'while…" 41 minutes ago Up 41 minutes coros-build-env-coros-dev-1 ``` Then you can attach to it by running -``` + +```bash docker compose exec <NAME or CONTAINER ID> /bin/bash ``` @@ -43,7 +44,7 @@ docker compose exec <NAME or CONTAINER ID> /bin/bash When attached to the docker container's shell, there is one post-install step left. Run the following command: -``` +```bash ./init_system.sh ``` @@ -57,7 +58,7 @@ export QT_QWS_FONTDIR=/etc/fonts ## Running On M1 -To build the dev enviroment on M1 *you must enable Rosseta x86 Emulation* (Docker Desktop, Settings, In Development, Beta Features). +To build the dev enviroment on M1 _you must enable Rosseta x86 Emulation_ (Docker Desktop, Settings, In Development, Beta Features). Then you have to pull, build and compose the container in seperate steps, adding the platform flag to each step. Pull the base image: @@ -66,9 +67,10 @@ Pull the base image: docker pull docker.io/library/ubuntu:18.04 --platform linux/amd64 ``` -Build the cortex-dev image: +Build the cortex-emu and cortex-dev images: ```bash +sudo docker build . --platform=linux/amd64 -t cortex-emu sudo docker build . --platform=linux/amd64 -t cortex-dev ``` @@ -84,12 +86,10 @@ You can create a custom update package based on the mounted filesystem, by runni The update file should be available on your host machine at `filesystems/update-opencortex.bin.gz`. You can validate the update file by mounting it as the actual update file using the `UPDATE_FILE` environment variable and running `init_system.sh`. - ## Config for custom compiled QT For running GUI applications such as `ZenUI` it is possible to output the video to a virtual device. One of these posibilities is a simple VNC server. To enable this ability I have compiled QT from source using the following config: -``` +```bash ./configure -embedded arm -xplatform qws/linux-arm-gnueabi-g++ -nomake examples -nomake demos -opensource -qt-libtiff -qt-zlib -qt-libpng -qt-libmng -qt-libjpeg -optimized-qmake -qt-freetype -qt-gfx-vnc -no-webkit -no-javascript-jit -optimized-qmake -no-cups && make ``` - |