Ah, you're right, seems like it's a stripped down version of fdisk. You could try opkg list | grep -i fdisk and try one of those and see if they're closer to the normal version of fdisk. Remember to opkg update first.. if you haven't done already

1. fdisk /dev/sdb
2. d <enter> - Delete every other partition you might have with multiple d <enter> - This 'd'eletes your partition(s)
3. n <enter> - Tell fdisk you want to add a 'n'ew partition
4. p <enter> - We'll add a 'p'rimary partition
5. <enter> x 3 - We want to use all space on the one partition we just added
6. t <enter> - In case it didn't choose linux partition 't'ype, lets make sure
7. 83 <enter> - The code for linux partition type
8. w <enter> - 'w'rite the changes to your device

Now you have /dev/sdb1 .. then just run mkfs.ext4 /dev/sdb1 and afterwards mount /dev/sdb1 <random directory> where <random directory> could be /mnt/usb

For fdisk, remember m for menu.. hope this works out for you!

@Theodore-Borromeo Yes it fixes the dependency so I'm able to compile it, but not link it. undefined reference to one or more of the functions.

Cloud Compile sounds fancy schmancy

Ah, you're right, seems like it's a stripped down version of fdisk. You could try opkg list | grep -i fdisk and try one of those and see if they're closer to the normal version of fdisk. Remember to opkg update first.. if you haven't done already

1. fdisk /dev/sdb
2. d <enter> - Delete every other partition you might have with multiple d <enter> - This 'd'eletes your partition(s)
3. n <enter> - Tell fdisk you want to add a 'n'ew partition
4. p <enter> - We'll add a 'p'rimary partition
5. <enter> x 3 - We want to use all space on the one partition we just added
6. t <enter> - In case it didn't choose linux partition 't'ype, lets make sure
7. 83 <enter> - The code for linux partition type
8. w <enter> - 'w'rite the changes to your device

Now you have /dev/sdb1 .. then just run mkfs.ext4 /dev/sdb1 and afterwards mount /dev/sdb1 <random directory> where <random directory> could be /mnt/usb

For fdisk, remember m for menu.. hope this works out for you!

Hehe, you need to read about fdisk on how to make new partitions

You could use fdisk. fdisk /dev/sdb

Add a partition to /dev/sdb .. then you'll get /dev/sdb1 .. and you can mkfs.ext4 /dev/sdb1

Did you try to mount /dev/sdb /mnt/sdb?

Sounds very strange. What channel does the Onion Omega AP use? https://en.wikipedia.org/wiki/List_of_WLAN_channels ..

That's the only thing I can see. If Onion Omega Wi-fi uses a channel your router don't check.

EDIT: And if there are only 5GHZ wi-fi networks around you, your Onion Omega will probably not detect those. But it's very rare that everyone is on the 5GHZ range hehe. And if your router is on the 5GHZ range, I don't know if it can find the 2.4GHZ ones. This is stuff that probably can be googled.

Thinking of it.. is your wi-fi router on the 5GHZ range?

EDIT2: Some errors here, this is stuff I don't know too much about. Of course when you scan with your PC it is your wifi-chip that does the job..

Thanks for the explanation. Never heard of PWM until now. New to electronics.

Very nice!

And very interesting too.. "new-expled - a program that uses GPIO pin access to control expansion dock led similar to the Omega supplied expled script" .. I know the GPIO's can only be set to 0 and 1.. but.. wondered how they could send in 0x0 - 0xFF.

EDIT: Just started reading from your sourcecode. Do you use their 'expled' binary to do your stuff?

Hi, I've been playing around with C and GCC on the Onion Omega for some days now. I just made some functions for manipulating the GPIO using C and have pushed it up to github. Remember you need gcc and Expansion Dock for this, and probably need to compile and link it on the Onion Omega itself.

https://github.com/huxflux/onion_omega_gpio

main.c is just testing the LEDs on the Expansion Dock to showcase that the functions are working. Nothing pretty, just chaotic.

All done on the Onion Omega.

Next is to find out how expled is done, since you can give values for each LED between 0x0 - 0xFF. Anyone know how he/she/they did it?

@Theodore-Borromeo That's what I thought, but it's not the case. Using -rpath options together with their libonionspi.so did nothing. I'm not sure what's going on.

Anyway, I was doing this for fun, and to prove a point. It is possible to compile and link on the Onion Omega using gcc. If you have the diskspace, since gcc is about 22MB.

Cloud compiling is coming soon. No need for this stuff.