@Jim-Brown I too am pretty familiar with Linux over a similar time period. However, I still keep getting thrown by the OpenWrt differences since it is in general a very much cut down version of Linux.
However, I can usually find what i want to know somewhere on the OpenWrt sites. The following are good starting points:
Surprised to hear that removing the sigaddset doesn't work for you - it seems to do so for me. I will have a closer look and get back to you as and when I find anything.
Thanks for the info on how you are building - this implies that the extra memory usage for new-gpio is down to the extra code functionality
@Enrico-Bermudez PLA has a very wide glass transition temperature range. Sitting on a car dashboard, parts will sag and conform to said dashboard. It doesn't flow well until up to extruder temperatures, but treat it a bit like a candy bar. Won't melt in your pocket though... ;)
The input to the PowerSwitch Tail is an optocoupler, with an input current range of about 3 - 30mA at a forward voltage of about 1.4V in the "ON" state. The modifications I have proposed will allow the Omega (whose I/O circuitry runs off a 2.5V supply) to provide at least 3mA when ON. If a 5V input is used instead of the Omega, the input current (with these modifications) becomes about 15mA, which is still well within the operating range for the PowerSwitch Tail's input current.
@will-burke Have had a play with the code you sent.
It all looks good and (as far as I can tell without having an I2c to SPI bridge myself) works as intented.
Except for getting the Aborted at the end.
I'm not sure why this would be so, but it seems to be due to creating i2cspi in i2c_spi_bridge.c on the stack rather than the heap. I made changes to i2c_spi_bridge.c to allocate i2cspi on the heap (this is the changed file: i2c_spi_bridge.c ). The changes consist of:
Changing the line:
SC18IS602 * i2cspi=new SC18IS602(SC18IS602_ADDRESS_000);
Replacing all instances of i2cspi. to i2cspi->
Ensuring that delete i2cspi; is called before exit.
Now all seems to be running OK.
I have also taken the liberty of making some small changes to the following files which I also attach:
onion-debug.c - the path is not needed in the #include since it is taken care of by the -I used in build_test1
build_test1 - have removed the -L and -l stuff from the link step. You are not actually linking to these libraries since you build the .o files and include them already in the link step.
@Matt-Ogborne I wonder if issues you may be having with pasting into the Console Text Editor (it appears you can't "paste" in from an external source) may be related to issues with your OS and/or browser.
I am using Windows 10 and Firefox browser and can copy text from a document under a completely separate program and paste it in Console Text Editor.
I cannot however copy a file from From File Explorer and then paste it - but that doesn't really surprise me.
@will-burke :-) Yes. Unless your I2C device has built in pull-up resistors you should always have a pull-up resistor on each of the I2C SDA and SCL lines. Only one resistor is needed on these lines no matter how many I2C devices you have connected. I2C protocol depends on these lines being pulled high when no I2C device is actively pulling them low.
Hi @Boken-Lin - Recieved my BLE expansion - but looking not sure how to control/see it . You speak of a page, but no link - can you please direct me in to the right place? I am running newest firmware. Thanks so much!
set up a TFTP server on another computer connected to your LAN/wireless network
host an image of the proper Omega firmware on the computer from http://repo.onion.io/omega/images/
connect the Omega in question to your LAN with the Ethernet Expansion
point the Omega to the TFTP server via your computer's IP and the image file name to flash it
This is the rough idea of how it will go, and we are still working on the documentation for it. We will be looking into this more this week.
well I got the tftp server set up with the image. having a hard time pointing the omega to the server ..
FTP and SCP are the only ones I know about since I use them and they do all I want.
However, a quick search also suggests that there is a SAMBA server available on the Omega. Doing opkg list samba* shows:
samba36-client - 3.6.25-5 - Samba 3.6 SMB/CIFS client
samba36-server - 3.6.25-5 - The Samba software suite is a collection of programs that implements the
SMB protocol for UNIX systems, allowing you to serve files and printers to
Windows, NT, OS/2 and DOS clients. This protocol is sometimes also referred
to as the LanManager or Netbios protocol.