Olimex Support Forum
1
A20 / Re: GPIO sysfs changes between...
Last post by adamor - Today at 12:03:11 pmHi kimfaint,
I think the difference is mainly that since Debian9 (if I remember well) Olimex switched from AllWinner custom kernel (3.x based) to mainline Debian based ones.
Hence all the I/O changed relatively and are managed quite differently.
We are facing similar issue on using uart2_rts and uart2_cts signals which could be enabled previously by mean of script.fex/script.bin files in the /boot but with Debian11 I wasn't able to use.
The solution I've found (albeit only in C/C++), which looks to works in both kernel case (Debian8 and Debian11) is to use the following sunxi gpio lib:
https://github.com/rubitwa/sunxi_gpio_lib
Even if you don't use C/C++ for you project you will find very easy to understand the concept.
The lib basically uses /dev/mem and base address to directly access the
This way only one file descriptor needs to be open and the access is very very fast.
I hope this will help your case.
Cheers,
Adamo
I think the difference is mainly that since Debian9 (if I remember well) Olimex switched from AllWinner custom kernel (3.x based) to mainline Debian based ones.
Hence all the I/O changed relatively and are managed quite differently.
We are facing similar issue on using uart2_rts and uart2_cts signals which could be enabled previously by mean of script.fex/script.bin files in the /boot but with Debian11 I wasn't able to use.
The solution I've found (albeit only in C/C++), which looks to works in both kernel case (Debian8 and Debian11) is to use the following sunxi gpio lib:
https://github.com/rubitwa/sunxi_gpio_lib
Even if you don't use C/C++ for you project you will find very easy to understand the concept.
The lib basically uses /dev/mem and base address to directly access the
This way only one file descriptor needs to be open and the access is very very fast.
I hope this will help your case.
Cheers,
Adamo
2
UEXT / MOD-LoRa-UEXT DIO5
Last post by kyrk.5 - February 02, 2023, 04:41:22 pmHello,
I try to use the MOD-LoRa-UEXT with a PIC32-PINGUINO-MICRO board together to realize a LoraWAN Node. My plan is/was to port the Microchip RN2483EU_1.0.6_RC4 Stack code.
https://github.com/MicrochipTech/RN2xx3_LORAWAN_FIRMWARE
While doing the porting to the PIC32, I have encountered a small issue. On the MOD-LoRa-UEXT the DIO0,1,2 are connected to the headers. However the stack from microchip looks like to relay on DIO0,1,5.
The microchip stack uses DIO5 for mode change check. DIO2 is for frequency hopping which as far as I see now, is not used at all.
So for me now the DIO2 is useless, instead of it DIO5 would help a little bit. However it looks like as it would be possible to read out an internal interrupt bit to see if a mode change is finished. So it is not a big deal at all. Maybe in the future a change of the design from DIO2 to DIO5 (or selecting with a solder jumper) could help to make the device more compatible with legacy libraries. Anyway the non -UEXT version have all pins tied to the pinheader.
I try to use the MOD-LoRa-UEXT with a PIC32-PINGUINO-MICRO board together to realize a LoraWAN Node. My plan is/was to port the Microchip RN2483EU_1.0.6_RC4 Stack code.
https://github.com/MicrochipTech/RN2xx3_LORAWAN_FIRMWARE
While doing the porting to the PIC32, I have encountered a small issue. On the MOD-LoRa-UEXT the DIO0,1,2 are connected to the headers. However the stack from microchip looks like to relay on DIO0,1,5.
The microchip stack uses DIO5 for mode change check. DIO2 is for frequency hopping which as far as I see now, is not used at all.
So for me now the DIO2 is useless, instead of it DIO5 would help a little bit. However it looks like as it would be possible to read out an internal interrupt bit to see if a mode change is finished. So it is not a big deal at all. Maybe in the future a change of the design from DIO2 to DIO5 (or selecting with a solder jumper) could help to make the device more compatible with legacy libraries. Anyway the non -UEXT version have all pins tied to the pinheader.
3
New Product Ideas / Re: Using locking barrel conne...
Last post by raily Rusive - February 02, 2023, 03:30:59 pmLocking barrel connectors are commonly used in industrial settings to provide a secure connection between boards and cables. They are known for their durability and reliability, making them an ideal choice for harsh industrial environments where equipment must withstand vibration, moisture, and other environmental factors.
One of the key benefits of using locking barrel connectors is their ability to prevent accidental disconnections. The locking mechanism ensures that the connection remains secure, even in environments where there is a lot of movement or vibration. This is particularly important in industrial settings, where any loss of connectivity could result in downtime and lost productivity.
Another advantage of using locking barrel connectors is their ease of use. They typically feature a simple, one-step design that makes it easy to connect and disconnect cables quickly and efficiently. This can be especially helpful in time-sensitive industrial environments where every second counts.
It's also worth noting that locking barrel connectors are often designed to meet specific industry standards, such as IP ratings for dust and water resistance. This means that they are able to perform in a wide range of environments, making them a versatile choice for a variety of industrial applications.
In conclusion, locking barrel connectors are an excellent choice for industrial boards that require secure, reliable, and durable connections. Whether you're connecting cables, powering devices, or transmitting data, these connectors can provide a solution that is both reliable and easy to use.
One of the key benefits of using locking barrel connectors is their ability to prevent accidental disconnections. The locking mechanism ensures that the connection remains secure, even in environments where there is a lot of movement or vibration. This is particularly important in industrial settings, where any loss of connectivity could result in downtime and lost productivity.
Another advantage of using locking barrel connectors is their ease of use. They typically feature a simple, one-step design that makes it easy to connect and disconnect cables quickly and efficiently. This can be especially helpful in time-sensitive industrial environments where every second counts.
It's also worth noting that locking barrel connectors are often designed to meet specific industry standards, such as IP ratings for dust and water resistance. This means that they are able to perform in a wide range of environments, making them a versatile choice for a variety of industrial applications.
In conclusion, locking barrel connectors are an excellent choice for industrial boards that require secure, reliable, and durable connections. Whether you're connecting cables, powering devices, or transmitting data, these connectors can provide a solution that is both reliable and easy to use.
4
AM3352 / Re: Can not connect Ethernet o...
Last post by LubOlimex - February 02, 2023, 09:25:54 amLAN1 is configured with default static IP address of 192.168.1.254. LAN2 is configured as DHCP. If you have trouble with one of them try using the other. The network settings can be edited in /etc/network/interfaces via a text editor (vi or nano).
Very important (!!!):
You need VLAN enabled to establish a proper connection to the board (as defined in IEEE 802.1Q). Make sure your hardware is compatible with IEEE 802.1Q. Make sure you have to enabled VLAN for the router/switch/bridge or the network card otherwise the Ethernet connection to the AM3352-SOM-EVB board will fail. You can find a lot guides online on how to enable VLAN (or VLAN tagging) for your specific hardware and operating system.
Very important (!!!):
You need VLAN enabled to establish a proper connection to the board (as defined in IEEE 802.1Q). Make sure your hardware is compatible with IEEE 802.1Q. Make sure you have to enabled VLAN for the router/switch/bridge or the network card otherwise the Ethernet connection to the AM3352-SOM-EVB board will fail. You can find a lot guides online on how to enable VLAN (or VLAN tagging) for your specific hardware and operating system.
5
A20 / Re: on A20 board bullseye cann...
Last post by LubOlimex - February 02, 2023, 08:33:11 amIt is not the problem with the Linux image since with the same software I see my SSD. So it is something else that is different between the two Linux images, maybe newer image requires slightly more power? How do you power the SSD and the LIME2 board?
6
A20 / Re: on A20 board bullseye cann...
Last post by dmalik - February 01, 2023, 11:36:25 pmboot witn bullsey on sd card
Quotesudo fdisk -l
Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mmcblk0: 14.41 GiB, 15476981760 bytes, 30228480 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x50a7dba6
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 20480 30228479 30208000 14.4G 83 Linux
7
A20 / Re: on A20 board bullseye cann...
Last post by LubOlimex - February 01, 2023, 12:33:11 pmAre you sure it is sda? Try with fdisk -l to see all listed devices. Did you first mount it before trying to access it?
I tested the base Linux image with a LIME2 board and SSD here and it works fine. The disk I used here was FAT32 formatted and I powered it via the LIME2 board using the sata cable set.
If the issue remains then it is probably something at your side - cabling, powering, disk formatting, etc, etc.
I tested the base Linux image with a LIME2 board and SSD here and it works fine. The disk I used here was FAT32 formatted and I powered it via the LIME2 board using the sata cable set.
If the issue remains then it is probably something at your side - cabling, powering, disk formatting, etc, etc.
8
AM3352 / Can not connect Ethernet on AM...
Last post by phuongnph - February 01, 2023, 12:14:26 pmHi everybody,
I'm connect AM3359-som and LAN8720A to get Ethernet connection. We use LAN1's slot, we changed dtb loaded, reboot the board. I see in AM335x-SOM wiki, it has the information of default IP address. So I just wondering that we need to config this IP address or not? If we need to change this IP address, can you give me a detailed instruction of this one.
I'm connect AM3359-som and LAN8720A to get Ethernet connection. We use LAN1's slot, we changed dtb loaded, reboot the board. I see in AM335x-SOM wiki, it has the information of default IP address. So I just wondering that we need to config this IP address or not? If we need to change this IP address, can you give me a detailed instruction of this one.
9
A20 / on A20 board bullseye cannot d...
Last post by dmalik - February 01, 2023, 12:39:45 amcfdisk: cannot open /dev/sda: No such file or directory (i boot on sd card with this image http://images.olimex.com/release/a20/ with base or minimal version !)
With boot on sd card with jessie, i can run on the ssd !
Help me
Thank's
excuse my bad english
With boot on sd card with jessie, i can run on the ssd !
Help me
Thank's
excuse my bad english
10
A64 / Re: Unexpected shutdowns after...
Last post by tioni - February 01, 2023, 12:33:43 amThe maximum frequency is OK as it is, @LubOlimex; this is not about that. When it becomes too hot, the board throttles a little bit. The heat system regulates the latter while cpufreq regulates the former, making the two effectively orthogonal.