Posts made by José Luis Cánovas

Not a chance. Better look for a RPi3.

@John-Wright
bonjour is needed if you want to use http://omega-ABCD.local/, instead use http://192.168.3.1 when connecting to the omega's wifi access point.

@Patrick-Rainsberry

try with Omega's numeric IP, like 192.168.3.1 if connected to its AP.

@Scott-W-Wood the wiki is for Omega 1, not Omega2/+

Check @WereCatf 's source directory, specially first_time_setup.sh and my docker project on info about how to build from LEDE.
The OnionIoT repository is not ready yet, they will publish the source code in the future*.

Hopefully the docs will include cross compilation soon.

@Paul-Grant
check @WereCatf 's source directory, specially first_time_setup.sh and my docker project on info about how to build from LEDE.

The OnionIoT repository is not ready yet, they will publish the source code in the future*.

@Gian-Carlo-Salvati check this post:

download firmware

Rename the file to Omega2.bin (for the Omega 2+ anyway)

Copy omega2.bin to usb storage (FAT32)

Connect PC to Omega 2 via device supporting USB to serial connectivity

Hold the reset button down and power on the omega

Select option #2, install firmware from USB.

@Alec-Stewart said in Idea Dump:

al Omegas on Expansion docks to then create a tinie tiny web server? There's some obvious concerns: Powering all of the devices, configuring them to properly communicate with on

Use a stack of ethernet expansions. Then, use a switch and load balancer system for all the omegas.
If you want to stack them with direct GPIO, I see too much trouble to make it work fine.

It could look like this:

@Mathieu-Gosbee

• You don't need the full SDK, nor in Docker, nor in your host pc. You can download the toolchain directly, as you can find in the third answer of this thread.
• Omega2 comes with SSH already listening, you can use scp to copy the binary, no need for sftp. Also, for windows, I prefer moba xterm than putty, which is based in putty, but better UI. More info in the docs.
• If you want to use windows, there is a thread that shows how to use Bash on Ubuntu on Windows to develop on windows without docker or virtual machines.
• Unless you love to code on VIM through serial or SSH in the omega, you are probably using a text editor like Sublime Text or Atom, or a full IDE, like CLion, Visual Studio, etc. to code a serious project. Why bother copying the source code and compiling in the omega when you can set up a faster and standard (& this) workflow in your pc?
• If your project is so small that gcc can compile it inside the omega2, why not use another programming language, like python? Here the docs about the libraries and supported languages. Python even has a GPIO module that C doesn't.

@Mathieu-Gosbee said in Make command doesn't exist,:

It's faster for me to compile this on device

Check WereCatf's source repository, my docker project (check signature) or @Jackdaw 's links, make is not only for compiling, you could give it good use for other things inside the omega2.

@Ian-Marchant you have to select in make menuconfig ubos and ubus, compile with make.
Check this post in my docker project about getting onion libraries, it explains where the library files will appear. You don't need to add onion feeds, but the thread is full with problems and solutions.

@t-gabor said in I2C read - first byte garbage:

After finding it is not part of the offcial omega2 repo, compiled the packages using the Docker Omega2 SDK(Thanks @José-Luis-Cánovas), and installed it on my omega2.

A pleasure.

Here is the images repo. Use the b160 for omega2p. And here the docs.

Crickets and tumbleweed

@Richard-Berg
check 5 posts above, the Edit1, changing curl with your package.

@José-Luis-Cánovas said in [Project] Docker Omega2 SDK for Cross Compilation + CMake support:

Edit 1: Install curl before running the script:

First, we need to login as root in the container to gain privileges to install new packages.
With the docker container stopped, run:
[Run in your host's terminal (mac, windows, linux)]

$   docker start omega2-sdk-app-built
$   docker exec -ti --user root omega2-sdk-app-built bash

Now you are root user inside the container. Install the curl package.
[Run inside the docker container]

#   apt update && apt install -y curl
#   exit

Then, go back to the container as omega user with the usual:
[Run in your host's terminal (mac, windows, linux)]

$   docker start omega2-sdk-app-built
$   docker attach omega2-sdk-app-built

Run the script above.

This is because omega user haven't got sudo permissions, and I prefer not to run anything inside docker with root permissions. Because the --user root option in docker is an easy and explicit way to use root, I don't plan to change this.

If you need to, create your own Dockerfile with FROM jlcs/omega2-docker-built at the start, and you will have ready to go image for your project.

Also, tell me what packages you need, because I plan to add many others.

I refuse to read your post as is, and I don't have time now, so in the meantime, edit it and use markdown for code to format your post.
Use 3 ``` before and after a block text to get something like:

Your error here please.

ls --all from where? /? /root? /www?
If you have SSH access, reinstall the onion console package with opkg, assuming your problem is that you deleted it's files.

@anglo-marc the onion tutorial is for Omega 1, not Omega2. Did you use the MIPSel (little-endian) compiler?

In my docker project you can find a long conversation between another apprentice in compiling for Omega2 and me, and in the OP a little introduction to How to compile C code (right before the Edit 1)

If you have a toolchain already set, you don't need Docker. Everything said in the post that must be executed inside the docker container is what you must do with your own toolchain, if it is the right one, the MIPSel 24kc.

@Paul-Kourany it's always useful to post the kernel panic log to help debugging. If you have serial connection, open an issue with all the info you can.

@Rajeev-B
The second one is already listed, the first one isn't, but is common knowledge in this community, and should be listed.

Workaround for the second one, use console terminal, ssh o serial connection, and use passwd.

@David-W
oooh dear, wish it was that easy.
Nonetheless, you can build your custom firmware from LEDE sources (they have Omega2 support), but you lose some features, like the wifi driver, the wifi setup tools, etc.

For that I recommend 2 options:

• If you have a linux machine and would like to develop natively: @WereCatf 's source repository, with a first_time_setup.sh file to ease the start.
• If you know Docker and want to keep your host machine clean, I have a Docker project with (almost) everything set up to start building firmwares. Check my signature for that. The almost note is because I still have to add Onion feeds to Docker. Reading the comments you will find instructions to do it manually until I add it to the Dockerfile.

If you want some source code, here is Onion's repo.