I want to try using it to run some home security CCTV. Ideally I'd like to apply some AI.

I need to update the Linux OS, and maybe the BIOS. I have looked at the download page, and nothing quite matches my board by name.

I run a few actual Raspberry Pi's with headless Ubuntu so I am comfortable working from the CLI.

Any pointers please?

Dazz

I have build an Image for UP-Board using Yocto Dunfell branch. The image is upboard-image-sato. I want ti install STMCubeProgrammer in it, but I am not able to do so. It would be great if I can install STMCUBEProgrammer in it.

STMCubeProgramme installer: https://www.st.com/en/development-tools/stm32cubeprog.html
Installation instruction on LINUX: https://karo-electronics.github.io/docs/software-documentation/flashtools/stm32-programmer/index.html

I built a Yocto image (dunfell 3.1.7) for the Upboard and copied the generated .hdd image to a bootable USB drive. However, after connecting the USB drive to the Upboard for flashing the eMMC, the system does not boot and keeps looping in the boot menu.

I followed the instructions provided in this link for building the Yocto image : https://github.com/AaeonCM/meta-up-board/tree/dunfell?tab=readme-ov-file

I have also attached the image for reference.

In Ubilinux 4 running on our UP Boards, we can see the TCO watchdog:

We cannot get the iTCO watchdog to show up under /dev/watchdog in Ubuntu. Have followed the instructions on your Github and set up Ubuntu desktop 20.04 correctly as per these instructions yet the iTCO watchdog doesn't display.

What kernel should we have installed to get the watchdog working? We installed:
Linux upxtreme-UP-WHL01 5.4.0-1-generic #2~upboard2-Ubuntu SMP Thu Jul 25 13:35:27 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux as per the instructions.

Should we be using a different kernel to get the iTCO watchdog on an UP Board? We don't want to use Ubilinux anymore so need this to work in Ubuntu.

P.S. we need the iTCO watchdog, not a softdog.

I have problems with the UP-3GHAT-A20-0001 module, on several occasions it disconnects from the USB bus and it is necessary to reselect the bus.
For example: ttyUSB6 connection disconnects, it is necessary to reselect ttyUSB0.
I have Linux Debian 12 installed:

[100931.181219] option1 ttyUSB6: GSM modem (1-port) converter now disconnected from ttyUSB6
[100931.181344] option 1-7.2.4:1.3: device disconnected
[100931.184994] qmi_wwan 1-7.2.4:1.4 wwan0: unregister 'qmi_wwan' usb-0000:00:14.0-7.2.4, WWAN/QMI device
[100934.732589] usb 1-7.2.4: new high-speed USB device number 9 using xhci_hcd
[100934.834395] usb 1-7.2.4: New USB device found, idVendor=05c6, idProduct=9003, bcdDevice= 0.00
[100934.834410] usb 1-7.2.4: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[100934.834416] usb 1-7.2.4: Product: UMTS/HSPA Module
[100934.834420] usb 1-7.2.4: Manufacturer: Quectel, Incorporated
[100934.841241] option 1-7.2.4:1.0: GSM modem (1-port) converter detected
[100934.841430] usb 1-7.2.4: GSM modem (1-port) converter now attached to ttyUSB0
[100934.841613] option 1-7.2.4:1.1: GSM modem (1-port) converter detected
[100934.841770] usb 1-7.2.4: GSM modem (1-port) converter now attached to ttyUSB1
[100934.841944] option 1-7.2.4:1.2: GSM modem (1-port) converter detected
[100934.842091] usb 1-7.2.4: GSM modem (1-port) converter now attached to ttyUSB2
[100934.842253] option 1-7.2.4:1.3: GSM modem (1-port) converter detected
[100934.842400] usb 1-7.2.4: GSM modem (1-port) converter now attached to ttyUSB3

Regards

Ruben

I would like to use some free GPIO pin (eg. pin 26) as a PPS device. Can anyone point me at a right direction of doing that? Kernel has pps-gpio module, but it needs to specify device in device tree, which is sadly not possible on x86 arch od UP Board.

For other platforms there are guides about how to enable it, eg here for a Pi, or this for Nvidia.

Any ideas what to do for UP4000?

Could anyone help with how to access GPIO pins from Python on an UP4000 running Debian?

Many thanks in advance.

UP HDMI IN Carrier Board
https://up-shop.org/default/up-hdmi-in-carrier-board.html

Could you please let me know how to set up the environment for this carrier board?

For now, I'm going to show my current status in the following:

up-board/up-community Wiki
https://github.com/up-board/up-community/wiki/Ubuntu-2004-LTS-GSG

I installed Ubuntu Desktop 20.04 image showed in the above page, and, applied the kernel patches provided in the following link.

Kernel repo link:
https://github.com/intel/linux-kernel-overlay/tree/lts2021-ubuntu

And, I found the string "INTC10C0" in the BIOS setting and the source file "ipu6-acpi.c".

BIOS:

• Sensor Model: [User Custom]
• Custom HID: INTC10C0

ipu6-acpi.c:

• { "INTC10C0", AR0234_NAME, get_sensor_pdata, NULL, 0, TYPE_DIRECT, NULL }, // AR0234 HID
• { "INTC10B1", LT6911UXC_NAME, get_sensor_pdata, NULL, 0, TYPE_DIRECT, NULL }, // Lontium HID

I also found the string LT6911UXC, so, by changing INTC10C0 to INTC10B1, and I could see the string "lt6911uxc". And, I found the I2C slave address of the chip LT6911UXC somewhere. I guessed the address is 0x2b, and by setting it in the BIOS setting, probably, the probing process of the chip LT6911UXC seemed to be passed.

And, refering to the document "Enable HDMI Capture on Yocto Tutorial.pdf" found in the page "UP HDMI IN Carrier Board", I using the sample Gstreamer command showed in the document, but, it doesn't work. The error message is like the following...

WARNING: erroneous pipeline: could not link camerasrcc0 to videoconvert0, neither element can handle caps video/xraw, format=(string)UYVY, width=(int)1920, height=(int)1080

I'm not familiar to gstreamer framework...

That is it for now. Any help would be greatly appreciated.
Thanks

We are a SME operating within the Marine Robotics field. We are currently developing a monitoring sea buoy for emergency robotics scenario.

For the sea buoy (and to evaluate the solution for coming fleet of autonomous underwater systems) we bought the up-board.

First impression is very good and also performances testing compiling time of large ROS2 projects. However, I noticed that SPI is not properly detected.

Did I miss something?

I noticed that support for Ubuntu 20.04 LTS was scheduled for Q3 2020. What is the status?

I hope you can help me, our demonstration deadline is in December and we need SPI to enable voltage monitoring onboard of the sea buoy through a raspberry-shield using both SPI and I2C (io explorer from abelectronics).

We already successfully used the shield in a raspberry pi 4 project (the rugged portable control station of this project). However, in the long term we would like to consider migration to x64 for all the subsystems.

Hope to receive help soon,

Vincenzo Calabrò
MDM Team CTO

We have quite a bunch of upboards and are now introducing the up-4000, ideally we would have yocto across the fleet, what would be the suggested approach for this?

i2c-3 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-10 i2c i915 gmbus dpb I2C adapter
i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-8 i2c i915 gmbus panel I2C adapter
i2c-6 i2c i915 gmbus ssc I2C adapter
i2c-4 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-11 i2c i915 gmbus dpd I2C adapter
i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-9 i2c i915 gmbus dpc I2C adapter
i2c-7 i2c i915 gmbus vga I2C adapter
i2c-5 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-12 i2c DPDDC-D I2C adapter

i2cdetect -r -y 0

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I have an additional upboard with the previous kernel (4.4.0-2-upboard) here is looks sorted:

i2c-0 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-1 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-2 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-3 i2c i915 gmbus ssc I2C adapter
i2c-4 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-5 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-6 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-7 i2c i915 gmbus vga I2C adapter
i2c-8 i2c i915 gmbus panel I2C adapter
i2c-9 i2c i915 gmbus dpc I2C adapter
i2c-10 i2c i915 gmbus dpb I2C adapter
i2c-11 i2c i915 gmbus dpd I2C adapter
i2c-12 i2c DPDDC-D I2C adapter

And I can see the device here where is should be (0X33):

i2cdetect -r -y 0

0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- 33 -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

What am I missing?

Thanks in advance for any response.

I have an UP-Xtreme i12 and I want to install an Ubuntu 20.04 server.
I tried using Ubuntu 20.04.03, 20.04.05, and 20.04.06. I burnt the image on a USB stick using etcher. I am following the guidelines in https://github.com/up-board/up-community/wiki/Ubuntu_20.04

Unfortunately, with any of these versions, I get the same error during installation.
The error is "block probing did not discover any disks".

Any idea how to solve this issue?

I am having very weird problem which I have not able to figure out (yet). I have one of the first generation up-board which runs Debian with patched kernel 4.9 (https://github.com/emutex/ubilinux-kernel/commits/upboard-4.9). When I try to use different generic kernel version (5.19 amd64) I am getting weird error during the boot:

mmc0: unrecognised CSD structure version 0
mmc0: error -22 whilst initialising MMC card

Now if I boot Ubuntu with kernel version 5.19 from usb flash drive I can see the mmc and I can access it.

Any ideas what could be the issue?

Board: AAEON UP-CHT01/UP-CHT01, BIOS UPC1BM0S 06/04/2016
Ram: 4GB
MMC : 32GB

Thanks

First of all. Congratulation for a so nice Product (Up Board). We now have more than 200 pcs online for building automation.

After a long period of time we switch our main OS to Ubuntu 22.04. Are there any scedule to make a kernel for this Ubuntu version? I think it is very simular to Ubuntu 20.04. Our goal is, to bring out the image on autumn this year.

And ist the first HW-Version from the year 2016 compatible with it?

Greetings from Switzerland

We are able to use HDMI with audio using kernel driver snd_hdmi_lpe_audio, but it looks like the audio card does not define any controls, so it is not possible to have multiple
sources streaming towards HDMI/audio concurrently.
Has anyone had the same problem ? Is there a way to solve this ?.

Br,

After selecting things on the menu, it will eventually ask me to take out the flash drive and hit enter. After I did that, the installation is still not done and it has been over 24 hours. I also have Ethernet connected to the UP board so I'm not sure if that will have an effect on anything.

I am new to UP board so any help will be appreciated.

Thank you in advance

I tried to install newest linux arch kernel on Up Board (6.1).
All works well except GPIO.

I know, it requires a additional driver compliated with kernel.
I tried to merge only this driver (from older repo), but without much success.

I need only GPIO controll, without I2C, SPI etc.

Does anyone compile 6.x Linux kernel on Up Board?
Is it even possible for support to help me with that?

Thanks,
Marcin

I've attached a log from Ubuntu's boot-repair tool below in case it is helpful. Thanks in advance for your assistance!

boot-repair-4ppa130                                              [20210921_1938]

============================== Boot Info Summary ===============================

 => No boot loader is installed in the MBR of /dev/mmcblk0.

sda: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Unknown
    Boot sector info: 
    Operating System:  
    Boot files:        /boot/grub/grub.cfg


================================ 0 OS detected =================================


============================ Architecture/Host Info ============================

CPU architecture: 64-bit
Live-session OS is Ubuntu 64-bit (Ubuntu 18.04.5 LTS, bionic, x86_64)


===================================== UEFI =====================================

BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.

efibootmgr -v
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001
Boot0001* UEFI: Memorex USB Flash Drive PMAP, Partition 1   PciRoot(0x0)/Pci(0x14,0x0)/USB(6,0)/USB(0,0)/HD(1,MBR,0x483122d5,0x35d8,0x1340)..BO
This session has been detected as 'live' because /proc/cmdline contains (boot=casper)
This session has been detected as 'live' because df -Th / contains overlay



============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________


Partitions info (1/3): _________________________________________________________


Partitions info (2/3): _________________________________________________________


Partitions info (3/3): _________________________________________________________


fdisk -l (filtered): ___________________________________________________________

Disk mmcblk0: 30.6 MiB, 32096256 bytes, 62688 sectors
Disk sda: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk identifier: 0x483122d5
      Boot Start     End Sectors  Size Id Type
sda1  *        0 4284223 4284224    2G  0 Empty
sda2       13784   18711    4928  2.4M ef EFI (FAT-12/16/32)

parted -lm (filtered): _________________________________________________________

sda:31.5GB:scsi:512:512:unknown:Memorex USB Flash Drive:;
mmcblk0:32.1MB:sd/mmc:512:512:unknown:MMC SDM032:;

blkid (filtered): ______________________________________________________________

NAME    FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
sda     iso9660  2020-08-06-22-59-01-00                                                    Ubuntu 18.04.5 LTS amd64 
├─sda1  iso9660  2020-08-06-22-59-01-00               483122d5-01                          Ubuntu 18.04.5 LTS amd64 
└─sda2  vfat     EC34-71CF                            483122d5-02                          Ubuntu 18.04.5 LTS amd64 
mmcblk0                                                                                                             

df (filtered): _________________________________________________________________

       Avail Use% Mounted on
sda         0 100% /cdrom

Mount options: __________________________________________________________________

sda    ro,noatime,nojoliet,check=s,map=n,blocksize=2048

====================== sda/boot/grub/grub.cfg (filtered) =======================

Try Ubuntu without installing
Install Ubuntu
OEM install (for manufacturers)
Check disc for defects

==================== sda: Location of files loaded by Grub =====================

           GiB - GB             File                                 Fragment(s)
            ?? = ??             boot/grub/grub.cfg                             1


======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown BootLoader on sda

00000000  45 52 08 00 00 00 90 90  00 00 00 00 00 00 00 00  |ER..............|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  33 ed fa 8e d5 bc 00 7c  fb fc 66 31 db 66 31 c9  |3......|..f1.f1.|
00000030  66 53 66 51 06 57 8e dd  8e c5 52 be 00 7c bf 00  |fSfQ.W....R..|..|
00000040  06 b9 00 01 f3 a5 ea 4b  06 00 00 52 b4 41 bb aa  |.......K...R.A..|
00000050  55 31 c9 30 f6 f9 cd 13  72 16 81 fb 55 aa 75 10  |U1.0....r...U.u.|
00000060  83 e1 01 74 0b 66 c7 06  f3 06 b4 42 eb 15 eb 02  |...t.f.....B....|
00000070  31 c9 5a 51 b4 08 cd 13  5b 0f b6 c6 40 50 83 e1  |1.ZQ....[...@P..|
00000080  3f 51 f7 e1 53 52 50 bb  00 7c b9 04 00 66 a1 b0  |?Q..SRP..|...f..|
00000090  07 e8 44 00 0f 82 80 00  66 40 80 c7 02 e2 f2 66  |..D.....f@.....f|
000000a0  81 3e 40 7c fb c0 78 70  75 09 fa bc ec 7b ea 44  |.>@|..xpu....{.D|
000000b0  7c 00 00 e8 83 00 69 73  6f 6c 69 6e 75 78 2e 62  ||.....isolinux.b|
000000c0  69 6e 20 6d 69 73 73 69  6e 67 20 6f 72 20 63 6f  |in missing or co|
000000d0  72 72 75 70 74 2e 0d 0a  66 60 66 31 d2 66 03 06  |rrupt...f`f1.f..|
000000e0  f8 7b 66 13 16 fc 7b 66  52 66 50 06 53 6a 01 6a  |.{f...{fRfP.Sj.j|
000000f0  10 89 e6 66 f7 36 e8 7b  c0 e4 06 88 e1 88 c5 92  |...f.6.{........|
00000100  f6 36 ee 7b 88 c6 08 e1  41 b8 01 02 8a 16 f2 7b  |.6.{....A......{|
00000110  cd 13 8d 64 10 66 61 c3  e8 1e 00 4f 70 65 72 61  |...d.fa....Opera|
00000120  74 69 6e 67 20 73 79 73  74 65 6d 20 6c 6f 61 64  |ting system load|
00000130  20 65 72 72 6f 72 2e 0d  0a 5e ac b4 0e 8a 3e 62  | error...^....>b|
00000140  04 b3 07 cd 10 3c 0a 75  f1 cd 18 f4 eb fd 00 00  |.....<.u........|
00000150  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  94 80 00 00 00 00 00 00  d5 22 31 48 00 00 80 00  |........."1H....|
000001c0  01 00 00 82 e0 fd 00 00  00 00 40 5f 41 00 00 fe  |..........@_A...|
000001d0  ff ff ef fe ff ff d8 35  00 00 40 13 00 00 00 00  |.......5..@.....|
000001e0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
000001f0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 55 aa  |..............U.|
00000200


=============================== StdErr Messages ================================

File descriptor 63 (pipe:[80550]) leaked on lvs invocation. Parent PID 7838: /bin/bash

Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

I have the Waveshare 2-CH CAN Hat (https://www.waveshare.com/wiki/2-CH_CAN_HAT) that I am trying to get working correctly with the Up board.

I have gotten the HAT to work on the Up Squared thanks to the instructions in the posts https://forum.up-community.org/discussion/3811/solved-mcp2515-can-bus-ubuntu-18-04-intel-cpu#latest and https://forum.up-community.org/discussion/96/canbus-hat-support. I also used the kernel module code from @nukular, but tweaked a couple of things:

• oscillator_frequency was set to 16000000
• max_speed_hz is 10 * 1000 * 1000

The settings I passed to the kernel module which worked on the Up Squared are:

• gpio_int pin Linux 471 (or GPIO pin 23).
• busnum was 1
• chip_select 0

On the Up board, I've discovered that the busnum has to be 2 and the chip select has to be 1. Otherwise, I get errors in the dmesg logs.

My setup:
I have one Up Squared with the CAN hat and kernel module installed. I've verified it can talk over the CAN hat to another Up Squared with the same CAN hat and kernel module running.

I have one Up board with the CAN hat and kernel module installed.

The Up board and Up Squared board have wires connecting each other on the CAN0 interface, CAN0_H on the Up Squared is connected to CAN0_H on the UP board and CAN0_L on the Up Squared is connected to CAN0_L on the Up board.

The test I've been doing is to run candump can0 on the Up Squared and cansend can0 000#11.22.33.44 on the Up board.

Things I've tried:
I've tried using the following gpio pin options when loading the kernel module:

• 471
• 22
• 23

After using insmod to load the kernel module with one of the above options and setting up the can0 interface, I tried using cansend to send a message to the Up Squared. The Up Squared never receives the message.

Has anyone else been able to get the waveshare 2-CH CAN Hat working with the Up board?

Here is the output of dmesg logs:

[  941.544179] mcp2515_init: init
[  941.544206] mcp2515_init: irq for pin 471 is 157
[  941.559150] mcp2515_init: device created!
[  941.573040] CAN device driver interface
[  941.617122] mcp251x spi2.1 can0: MCP2515 successfully initialized.
[  969.439637] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 1644.014597] can: controller area network core (rev 20170425 abi 9)
[ 1644.014735] NET: Registered protocol family 29
[ 1644.026087] can: raw protocol (rev 20170425)
[ 1964.268386] mcp2515_init: exit
[ 2067.185173] mcp2515_init: init
[ 2067.185269] mcp2515_init: irq for pin 23 is 158
[ 2067.236835] mcp251x spi2.1 can0: MCP2515 successfully initialized.
[ 2067.236927] mcp2515_init: device created!
[ 2114.461978] up_irq_chip_set_type_parent: type:2, gc->label:up-pinctrl, offset:23
[ 2114.461984] up_irq_chip_set_type_parent: pin->irq:158, pin->soc_gpio.irq:138
[ 2114.461986] up_irq_chip_set_type_parent: no NULL
[ 2114.479256] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 2200.669503] x86/PAT: alsa-sink-HdmiL:2800 map pfn RAM range req uncached-minus for [mem 0x3c500000-0x3c556fff], got write-combining
[ 2234.067601] x86/PAT: alsa-sink-HdmiL:2800 map pfn RAM range req uncached-minus for [mem 0x3c500000-0x3c556fff], got write-combining
[ 2241.640608] mcp2515_init: exit
[ 2347.534458] mcp2515_init: init
[ 2347.534561] mcp2515_init: irq for pin 22 is 159
[ 2347.582054] mcp251x spi2.1 can0: MCP2515 successfully initialized.
[ 2347.582183] mcp2515_init: device created!
[ 2367.080299] up_irq_chip_set_type_parent: type:2, gc->label:up-pinctrl, offset:22
[ 2367.080305] up_irq_chip_set_type_parent: pin->irq:159, pin->soc_gpio.irq:137
[ 2367.080307] up_irq_chip_set_type_parent: no NULL
[ 2367.103268] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 2843.670977] mcp2515_init: exit

For reference, here is the kernel module code:

#include <linux/init.h>
#include <linux/module.h>
#include <linux/spi/spi.h>
#include <linux/can/platform/mcp251x.h>
#include <linux/gpio.h>
#include <linux/interrupt.h>

int busnum = 2;
int chip_select = 1;
int gpio_int = 471;

module_param(busnum, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(busnum, "busnum of spi bus to use");

module_param(gpio_int, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(gpio_int, "linux gpio number of INT gpio");

module_param(chip_select, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
MODULE_PARM_DESC(chip_select, "spi chip select");

int gpio_requested = 0;

struct spi_device *dev1;
static struct mcp251x_platform_data mcp251x_info = {
    .oscillator_frequency = 16000000,
};

static struct spi_board_info spi_device_info = {
    .modalias = "mcp2515",
    .platform_data = &mcp251x_info,
    .irq = -1,
    .max_speed_hz = 10 * 1000 * 1000,
};

static int __init mcp2515_init(void)
{
    int ret;
    struct spi_master *master;

    printk("mcp2515_init: init\n");

    ret = gpio_request(gpio_int, "sysfs");

    if(ret)
    {
        printk("mcp2515_init: could not request gpio %d\n", gpio_int);
        goto error_postgpio;
    }
    gpio_requested = 1;

    gpio_direction_input(gpio_int);

    ret = gpio_to_irq(gpio_int);
    printk("mcp2515_init: irq for pin %d is %d\n", gpio_int, ret);
    spi_device_info.irq = ret;
    spi_device_info.bus_num = busnum;
    spi_device_info.chip_select = chip_select;

    master = spi_busnum_to_master( spi_device_info.bus_num );
    if( !master )
    {
        printk("mcp2515_init: MASTER not found.\n");
        ret = -ENODEV;
        goto error_postgpio;
    }

    // create a new slave device, given the master and device info
    dev1 = spi_new_device( master, &spi_device_info );

    if( !dev1)
    {
        printk("mcp2515_init: FAILED to create slave.\n");
        ret = -ENODEV;
        goto error_postgpio;
    }

    printk("mcp2515_init: device created!\n");

    return 0;

    error_postgpio:
        gpio_free(gpio_int);
        return ret;
}

static void __exit mcp2515_exit(void)
{
    printk("mcp2515_init: exit\n");

    if( dev1 )
    {
        spi_unregister_device(dev1);
    }

    if(gpio_requested)
    {
        gpio_free(gpio_int);
    }
}

module_init(mcp2515_init);
module_exit(mcp2515_exit);
MODULE_LICENSE("GPL");
MODULE_AUTHOR("Jeff");
MODULE_DESCRIPTION("MCP2515 init");

I set up the board using these instructions: https://github.com/up-board/up-community/wiki/Ubuntu_18.04

I changed the I2C Speed setting in the BIOS under Advanced -> HAT Configuration, but the when I measure the clock speed using a logic analyzer I still see a frequency of ~385 khz.

I am using i2c-5 (physical pins 3/5).

I think I have the latest BIOS/kernel versions installed:
BIOS version: UPC1DM25
kernel version: 5.4.0-1-generic #0~upboard5-Ubuntu SMP Fri Jan 7 11:53:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

I also tried changing the I2C mode from ACPI to PCI, as suggested here, but I see no difference.

So, how can I change the I2C speed to 100khz?

SUBSYSTEM=="spidev", GROUP="spiuser", MODE="0660"

sudo groupadd spiuser
sudo adduser "$USER" spiuser

SUBSYSTEM=="i2c-dev", GROUP="i2cuser", MODE="0660"

sudo groupadd i2cuser
sudo adduser "$USER" i2cuser

SUBSYSTEM=="gpio*", PROGRAM="/bin/sh -c '\
        chown -R root:gpiouser /sys/class/gpio && chmod -R 770 /sys/class/gpio;\
        chown -R root:gpiouser /sys/devices/virtual/gpio && chmod -R 770 /sys/devices/virtual/gpio;\
        chown -R root:gpiouser /sys$devpath && chmod -R 770 /sys$devpath\
'"

sudo groupadd gpiouser
sudo adduser "$USER" gpiouser

#include <unistd.h>
#include <stdlib.h>
#include <stdio.h>
#include <errno.h>
#include <string.h>
#include <fcntl.h>
#include <getopt.h>
#include <sys/ioctl.h>
#include <linux/gpio.h>
#include <time.h>
#include <mraa.h>

#define HEADERPIN 11

void sleepMillis(uint32_t millis) {
  struct timespec sleep;
  sleep.tv_sec = millis / 1000;
  sleep.tv_nsec = (millis % 1000) * 1000000L;
  while(clock_nanosleep(CLOCK_MONOTONIC, 0, &sleep, &sleep) && errno == EINTR);
}

int main(int argc, char **argv)
{
	mraa_init();
	mraa_gpio_context gpio;

	if (!(gpio = mraa_gpio_init(HEADERPIN))) {
		fprintf(stderr, "Error exporting pin %d!\n", HEADERPIN);
		mraa_deinit();
		exit(1);
	}

	/* Check if the binary has root-permissions: if not,
	sleep for 100ms to give udev time to set the GPIO-permissions
	correctly for us to use the pin we just initialized above.
	!IMPORTANT! */
	/* Try uncommenting this or changing the amount of time
	we sleep and see what happens. */
	if(geteuid()) sleepMillis(100);

	if(mraa_gpio_dir(gpio, MRAA_GPIO_OUT) != MRAA_SUCCESS){
		fprintf(stderr, "Error setting pin-direction!\n");
		mraa_gpio_close(gpio);
		mraa_deinit();
		exit(1);
	}
	printf("Blink HIGH..\n");
	mraa_gpio_write(gpio, 1);
	sleepMillis(1000); //Sleep one second
	printf("Blink LOW..\n");
	mraa_gpio_write(gpio, 0);
	sleepMillis(1000); //Sleep one second
	mraa_gpio_dir(gpio, MRAA_GPIO_IN);
	mraa_gpio_close(gpio);
	mraa_deinit();
	exit(0);
}

#!/bin/bash
#Export GPIO3, or pin number 11 on the UP1-board
echo 3 > /sys/class/gpio/export
#Test if we have root-permissions and, if not, sleep for 100ms
if [ $EUID -gt 0 ]; then sleep 0.1; fi
echo out > /sys/class/gpio/gpio3/direction
echo 1 > /sys/class/gpio/gpio3/value
sleep 1
echo 0 > /sys/class/gpio/gpio3/value
sleep 1
#Set the pin back as INPUT and unexport it
echo in > /sys/class/gpio/gpio3/direction
echo 3 > /sys/class/gpio/unexport

import RPi.GPIO as GPIO
import time
#We need this
from os import geteuid

# Pin Definitions:
ledPin = 4

# Pin Setup:
GPIO.setmode(GPIO.BCM)
GPIO.setup(ledPin, GPIO.OUT) # LED pin set as output
#If we're not root, sleep 100ms in order for udev to set
#the permissions on the exported GPIO right
if(geteuid() > 0):
	time.sleep(0.1)

print("Here we go! Press CTRL+C to exit")
try:
	while 1:
		GPIO.output(ledPin, GPIO.HIGH)
		time.sleep(0.5)
		GPIO.output(ledPin, GPIO.LOW)
		time.sleep(0.5)
except KeyboardInterrupt: # If CTRL+C is pressed, exit cleanly:
	GPIO.cleanup() # cleanup all GPIO

import RPi.GPIO as GPIO
import time

# Pin Definitons:
ledPin = 4

# Pin Setup:
GPIO.setmode(GPIO.BCM)
GPIO.setup(ledPin, GPIO.OUT) # LED pin set as output

print("Here we go! Press CTRL+C to exit")
try:
 while 1:
     GPIO.output(ledPin, GPIO.HIGH)
     time.sleep(0.5)
     GPIO.output(ledPin, GPIO.LOW)
     time.sleep(0.5)
except KeyboardInterrupt: # If CTRL+C is pressed, exit cleanly:
 GPIO.cleanup() # cleanup all GPIO

And I run this command on terminal:

python3 ledblink.py 

I get this error message;

Traceback (most recent call last):
  File "ledblink.py", line 1, in <module>
    import RPi.GPIO as GPIO
  File "/home/rnd/.local/lib/python3.8/site-packages/RPi/GPIO/__init__.py", line 23, in <module>
    from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!

How can i fix that?

Edit1: According to wiki UPBoard supports RPi.GPIO library

1. During OS installation, the board hung up after I clicked "Install now". It should go to the next step within seconds. After waiting for around 10 minutes, I restarted the board and started over.
2. In my second attempt, it proceeded to the file copy step. But then showed an error message- "Error during copying files". It said that the hard disk might be faulty. I am attaching the screenshot here. Note that the USB drive I am using for OS installation is the same one I used to set up the other three boards (before and after). All worked without any problem.
3. I restarted the board and tried again. This time the OS was successfully installed. (3rd time)
4. After OS installation, when I started to use the board, it restarted several times suddenly without any reason.

Does anyone have any idea what could be the reason?

This url doesn't work either
https://launchpad.net/~aaeon-cm/+archive/ubuntu/5.4-upboard/+packages

Where can I find the packages allowing to install this kernel on an up
Thank you

There is a regression issue in kernel 5.4.0 relating to the i915 driver. The GPU hangs when doing hardware rendering or video decoding/encoding which we make plenty use of.

See the related launchpad issue:
system hang: i915 Resetting rcs0 for hang on rcs0

In general, isn't there an alternative to patching the kernel in order to obtain GPIO etc? Wouldn't a module suffice? I'm asking as a layman in all things kernel.

The kernel successfully registers the GPIO interrupt, but when the GPIO external signal changes, the interrupt function is not triggered and the number of corresponding interrupts counted by /proc/interrupts is always 0

My test code:

define IMU_TDK_42688_IRQ_NUM 430

static irqreturn_t irq_handler(int irq, void *dev_id)
{
printk("Interrupt in ");
return IRQ_HANDLED;
}
int init_irq_gpio_num(int gpio_num)
{
int irq_num = 0 ;
int ret = 0;
if(gpio_num <= 0)
{
pr_err("%s:Get gpio num error...",FUNCTION);
return -1;
}
if(gpio_request_one(gpio_num, GPIOF_IN, "MCU_sel") < 0) {
printk(KERN_ALERT "GPIO %d cannot be used\n", IMU_TDK_42688_IRQ_NUM);
return -EBUSY;
}
irq_num = gpio_to_irq(gpio_num);//GPIO to IRQ NUM
if(irq_num < 0)
{
pr_err("%s:gpio_to_irq error",FUNCTION);
return -5;
}

// ret = request_irq(irq_num,irq_handler , IRQF_TRIGGER_RISING|IRQF_TRIGGER_FALLING, "my_test_interrupt", NULL); 
ret = request_irq(irq_num,irq_handler , IRQF_TRIGGER_HIGH, "my_test_interrupt", NULL); //IRQF_TRIGGER_HIGH
if(ret != 0) {
    printk(KERN_ERR "can not get irq\n");
    return ret;
} 
printk("%s:Get imu irq succsess(irq_num=%d,gpio_num=%d)...",__FUNCTION__,irq_num,gpio_num);
ret = enable_irq_wake(irq_num);
printk("the enable_irq_wake  result is: %d\n", ret);



return irq_num;

}

static int __init test_interrupt_init(void)
{
printk("Start test_interrupt_init");
irq_num_test = init_irq_gpio_num(IMU_TDK_42688_IRQ_NUM);
if(irq_num_test < 0){
printk("test_interrupt_init failed!!");
return irq_num_test;
}
else{
printk("requist irq num =%d\r\n",irq_num_test);
return 0;
}

}
static void __exit test_interrupt_exit(void)
{

if(irq_num_test >0)
    free_irq(irq_num_test,irq_handler);
else
    printk("Skip free_irq irq_num=%d",irq_num_test);

gpio_free(IMU_TDK_42688_IRQ_NUM);

printk("Exit test_interrupt_exit");

}

sudo add-apt-repository ppa:aaeon-cm/5.4-upboard

with an error that '~aaeon-cm' user or team does not exist.

What do I do to fix this?

Also, BTW, the https://releases.ubuntu.com/20.04/ubuntu-20.04.2.0-desktop-amd64.iso does not exist, but I used the 20.04.3 version for my install image.

-Mark

switch serial1 with serial0

enable_uart=1
. sul file cmdline.txt
dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4
elevator=deadline fsck.repair=yes root wait
Ho riavviato il tutto, provo tramite Arduino IDE installato sul raspberry
ha caricare uno sketch ma non lo carica.
Come posso risolvere questo problema?

And I get the rt-preempt patch from
https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/5.4/older/
the rt-preempt version is 5.4.66-rt38

It compile ok!

when I load this kernel, after the ubuntu 18.04 start ok a few minute. The kernel will be dump, I can't use keyboard mouse ssh-remote and so on.

so how to solve this problom??
or where can get a other kernel which support upboard??

Stupid question-- is there a straightforward way to tweak Python modules/libraries for Raspberry Pi accessories so they're compatible with the UP Board? I was able get get some relay boards working by using MRAA and the appropriate MRAA numbering, but other serial-based relay boards and things like a PiJuice elude me.

Any pointers?

Thanks!

I bought a new UP board CHT01-A10-0232. My intention is to control GPIO using NodeJs.
I installed the new kernel from https://wiki.up-community.org/Ubuntu_18.04
I can control the pins with instructions from here: https://github.com/up-board/up-community/wiki/Pinout_UP2
When I try to install mraa following this: https://github.com/up-board/up-community/wiki/MRAA
when I run
sudo apt-get install nodejs nodejs-legacy npm
I get:

Note, selecting 'nodejs' instead of 'nodejs-legacy'
nodejs is already the newest version (8.17.0-1nodesource1).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
nodejs : Conflicts: npm
E: Unable to correct problems, you have held broken packages.

And then when I run npm install mraa
I get
/root/.cache/node-gyp/12.18.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
declarator attribute((deprecated(message)))
^
../src/mraajsJAVASCRIPT_wrap.cxx: At global scope:
../src/mraajsJAVASCRIPT_wrap.cxx:907:7: error: ‘Handle’ in namespace ‘v8’ does not name a template type
v8::Handle err;

I am stuck here.
Can somebody help me please?
Thank you!

I have an UP board and the wifi kit. I've been trying to set the wifi to act as a wireless access point/hotspot but to no avail. The 'hotspot' option from GUI is unavailable and following instructions used on PI like here failed as well.

The only difference I've made from the instructions is changing wlan0 to my interface which is something like wlx7cdd******* (tried wlan0 but doesn't work as well).

Does the wifi kit support access point? And if yes, any suggestions on where have I gone wrong?

I have 100s of UPBoards deployed remotely i do not have physical access to them.
1. They do not have screens attached to them
2. they are running 24/7

I have had some issues of the devices freezing.
the only way to fix this issue is to hard reset the device (unplugging and plugging back in again)... this is a major problem for me as i cannot gain access to them myself and they should not be freezing like they do..

On problematic devices i have pulled the sys and kernel logs and there is nothing in between the timespan of the device being down.

The last line logged in the Sys log was:
Aug 9 00:17:01 ubilinux CRON[14157]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
and then a complete system crash...

Rough Hardware Info:
1. I am powering the device over the 5V GPIO pin with a UPS designed specifically for the UPBoard...
2. I also am utilizing 2 USB ports (1 for a custom BLE dongle, 2 for a Wifi dongle)
3. I have a Custom PCB attached getting powered by the UPS
4. The Custom PCB Utilizes the C7 10 pin connector to connect to a 3G mini-PCie Telit Cellular module

That is a rough description of the hardware.. and most of the time everything seems fine..
however we do seem to "randomly" get complete OS freezes and the only fix is to recycle the power..

Is there any logs / things you can think of that i can look at to get a better understanding of what the problem is.. or do you have a possible solution that will fix the issue at its core.

This is urgent, as i say i have 100's nearly 1000's of UPboards and they are "randomly" experiencing this issue..

Regards,
David Hutchinson

My plan is to use the SPI pins on the board to send data to a DAC, and use additional pins to control Chip Select and LDAC, which is easy enough after looking through documentation.

But for directly using the SPI pins, I am using RPi.GPIO, and I’m not sure if it has direct support to perform an SPI transfer. If there is a better library for this, I would like to know. So, after all that, my question is: How do you write a program to use SPI on the Upboard in Python?

As a secondary question, Python presumably has ways to read in a .csv file from a USB through a library, yes?

Thanks!

• Strict timing restrictions on the neopixels can cause some problems on the UP2 board. I guess there are some solutions like using SPI. But I am fairly new to programming and I don't know anything about SPI or UPboard. So I don't know how to implement this solution. For ex. I saw this library; https://github.com/adafruit/Adafruit_CircuitPython_NeoPixel_SPI But I don't know if it's applicable to UP2 or not, and if so; how?

• If any of you have tried to use neopixel led rings on the UP2 board, can you share a guideline? For a real beginner..

We've currently installed Lubuntu 20.10 for our testing... Can anyone suggest any reasons for the "freezing" ?

Best regards,
A

I tried the solutions from this post however it didn’t work for us.

Could someone help me understand what is going on or where I should be looking?

I've attached a photo of the point at which all the boards hang.

Best,
A

I have been trying to build yocto poky linux(pyro) on host PC(ubuntus16.04.4 on VirtualBox).
But it has finished building　with following errors ,so I could not get builded image.

#

ERROR: linux-intel-4.9.81+gitAUTOINC+a2dfb1610d_c249d8e0ca-r0.1 do_unpack: Fetcher failure: Fetch command export [...my environment variable...]; git -c core.fsyncobjectfiles=0 checkout -B yocto-4.9 a2dfb1610d9dad34652a3c27c6c9d8751ed67af6 failed with exit code 128, output:
fatal: reference is not a tree: a2dfb1610d9dad34652a3c27c6c9d8751ed67af6

ERROR: linux-intel-4.9.81+gitAUTOINC+a2dfb1610d_c249d8e0ca-r0.1 do_unpack: Function failed: base_do_unpack
ERROR: Logfile of failure stored in: /home/apn/poky/build/tmp/work/corei7-64-intel-common-poky-linux/linux-intel/4.9.81+gitAUTOINC+a2dfb1610d_c249d8e0ca-r0.1/temp/log.do_unpack.8177
ERROR: Task ([...my home directry path...]/poky/meta-intel/common/recipes-kernel/linux/linux-intel_4.9.bb:do_unpack) failed with exit code '1'

#

I have used following procedure for building yocto poky linux(pyoro):

#

git clone -b pyro git://git.yoctoproject.org/poky.git
cd poky

git clone -b pyro git://git.yoctoproject.org/meta-intel.git

git clone -b pyro git://git.openembedded.org/meta-openembedded

git clone -b pyro https://github.com/emutex/meta-up-board

TEMPLATECONF=meta-up-board/conf source oe-init-build-env

bitbake upboard-image-sato

#

Is threre any mistake or missing procedure in my procedure?

I would appreciate any sort of help with this issue.

Will there be a kernel update to fix CVE-2021-33909 vulnerability?
According to https://www.linuxkernelcves.com/cves/CVE-2021-33909 it should be fixed in 5.4 stream (which I'm currently using at mine up2 board over ubuntu 18.04).

Barring that, has anyone had luck using the Sumo version of the Yocto BSP for the Up Board with the newer releases of Yocto? I guess the supported Linux kernel being 4.4 would likely be a potential issue. To support Ubuntu 20.04, there looks to be a 5.4 kernel, but I don't see evidence there is a Yocto recipe for this version of the kernel.

After all doing this. I installed i2detect and rund the command i2cdetect -y -r 5 and here is the result image:

When I unplug the pins 68 in the table disappears so I think it detects my sensor. The problem is that I dont know how to read data from sensor. According to driver document I tried to use code but I couldnt read any data. Here is my code I tried. But i dont know which side I am doing wrong. The problem is about the code or about the upboard. How can I read I2C data from terminal.

#include "bmi160.h"
#include <iostream>

using namespace std;


int main(int argc, char *argv[])
{

    struct bmi160_dev sensor;

    sensor.id = BMI160_I2C_ADDR;
    sensor.interface = BMI160_I2C_INTF;

    int8_t rslt = BMI160_OK;
    rslt = bmi160_init(&sensor);
    /* After the above function call, accel and gyro parameters in the device structure
    are set with default values, found in the datasheet of the sensor */



    /* Select the Output data rate, range of accelerometer sensor */
    sensor.accel_cfg.odr = BMI160_ACCEL_ODR_1600HZ;
    sensor.accel_cfg.range = BMI160_ACCEL_RANGE_2G;
    sensor.accel_cfg.bw = BMI160_ACCEL_BW_NORMAL_AVG4;

    /* Select the power mode of accelerometer sensor */
    sensor.accel_cfg.power = BMI160_ACCEL_NORMAL_MODE;

    /* Select the Output data rate, range of Gyroscope sensor */
    sensor.gyro_cfg.odr = BMI160_GYRO_ODR_3200HZ;
    sensor.gyro_cfg.range = BMI160_GYRO_RANGE_2000_DPS;
    sensor.gyro_cfg.bw = BMI160_GYRO_BW_NORMAL_MODE;

    /* Select the power mode of Gyroscope sensor */
    sensor.gyro_cfg.power = BMI160_GYRO_NORMAL_MODE;

    /* Set the sensor configuration */
    rslt = bmi160_set_sens_conf(&sensor);
    struct bmi160_sensor_data accel;
    struct bmi160_sensor_data gyro;

    /* To read only Accel data */
    rslt = bmi160_get_sensor_data(BMI160_ACCEL_SEL, &accel, NULL, &sensor);

    cout<<accel.z<<endl;


    /* To read only Gyro data */
    rslt = bmi160_get_sensor_data(BMI160_GYRO_SEL, NULL, &gyro, &sensor);

    /* To read both Accel and Gyro data */
    bmi160_get_sensor_data((BMI160_ACCEL_SEL | BMI160_GYRO_SEL), &accel, &gyro, &sensor);

    /* To read Accel data along with time */
    rslt = bmi160_get_sensor_data((BMI160_ACCEL_SEL | BMI160_TIME_SEL) , &accel, NULL, &sensor);

    /* To read Gyro data along with time */
    rslt = bmi160_get_sensor_data((BMI160_GYRO_SEL | BMI160_TIME_SEL), NULL, &gyro, &sensor);

    /* To read both Accel and Gyro data along with time*/
    bmi160_get_sensor_data((BMI160_ACCEL_SEL | BMI160_GYRO_SEL | BMI160_TIME_SEL), &accel, &gyro, &sensor);
}

efi: requested map not found.
esrt: ESRT header is not in the memory map.
CPLD verify error (expected: FFFFFFF, actual: 0)
up-pinctrl up-pinctrl: CPLD initialisation failed
Failed to find cpu0 device node
i8042: Can't read CTR while initializing i8042

I understand that GPIO buses on UP are driven by a CPLD, so does that mean my board is damaged? Or something else could be done to initialize all these correctly?
Thanks!

• graphics system including HDMI and GPU
• ethernet
• (optionally) USB
• limit amount of available/running cores
• turn off bluetooth/wifi, etc
• reduce clock frequency.
  On some other systems such things can be done in /boot/config.txt (e.g. on RPi).

What would be the way to that on the Up-squared (ubuntu 18.04 with 5.4.0 kernel)?

Thanks!

I obtained two 2Gb UP Boards through the Kickstarter program though I had no practical use for them at the time (and I still don't have a real use for them)! However I decided I'd

revive them to see what can be done with them. Too much time on my hands I guess.

The UP-boards were set with UBilinux ver 3 initially (one of the two boards has not been touched yet so that will still be as supplied). I upgraded to ver. 4 but with an ancient 4.4

long term kernel. I like to have a recent kernel and I don't like cross compiling. I also like to use Debian (which I use on ARM and MIPS platforms) but that is not available today on

UP-Board. I have an irrational dislike of Ubuntu after the mess up in GUI's in the ancient past, so I don't want that.

I now have one of my UP-Boards running with Linux kernel 5.11.16 (customised) and Debian Buster. I have a 1TB SSD attached (and boot from) to the USB3.0 OTG port which did cause me

problems due to the cables.

How did I do this? My first step was to attach a Sata drive (formatted ext4) to one of the USB2 ports and download Ubuntu which worked fine. This filled up the eMMC (16GB) when all the

software and build tools were loaded. Once I had set up the ssh daemon to accept sessions (could use the console but I don't), I set up the Sata drive with a dummy /usr/src directory,

downloaded the latest available kernel from kernel.org, unpacked it, copied the V4 config file from the UP-board to the linux-5.11.16 directory and performed a 'make oldconfig' on it.

This was a mistake in practice. After compilation, the size of the kernel would not allow a clean reboot so had kernel panics. This is due to the number of loaded modules into the

allocated DRAM space.

After searching the UP-Community, I found a minimal config file for UP board kernel suitable for kernel 4.9. After performing 'make oldconfig' followed by 'make menuconfig' I reduced

the number of loaded modules or changing some modules from '<*>' to '' and eliminating many uneccessary modules included when 'defconfig' was initially used. For the time being I

have also cut out the IPv6 section as I don't use that at present. After compilation, the kernel booted but there were loading errors which need non-free modules to be downloaded. In

particular the Realtek 8xxx firmware and i915 firmware. Thes modules are available from the 'net.

Having got a clean kernel compile I was able to 'make headers_install', 'make modules_install' 'make install' to boot the system. The 'make install' script takes care of updating GRUB

so I was able to choose between the old 4.4 kernel and my newly compiled 5.11.16 kernel (with some errors I admit). This was still booting (eventually) into Ubuntu in eMMC.

My next step was to update the UP-Board Bios as downloaded from the UP site. This version had a lot more options and I had a bit of a learning curve to understand some of the options.

At this stage, I could not understand the booting options nor the OTG options for the USB3 port. I hadn't realised that there was an expert mode for Bios configuration. I was quite

nervous about the EFI security locking me out. After some research and trial and error I understood the CRB section of options. I ran the update but I admit I was confused by the

procedures on screen, partly because some options were obscured and needed to scroll down the screen, and partly through my lack of understanding the update process. Too used to U-Boot

I guess!

Once I had got to successfuly update the new Bios, I set the Bios to initially boot from USB. I downloaded the Netinstall version of Debian Buster as an ISO and used Balena Etcher to

put the image on a clean microSD. I attached a new clean 1Tb SSD with a USB to Sata adapter to one of the USB2 ports. I also inserted the microSD (in a USB carrier) into a USB2 port.

Booting the UP-board from the MicroSD started the Debian install. I used the GUI intall method which, after a few mistakes or misunderstandings, I was able to get a good Debian buster

image on the SSD. Changing the boot options (Still had the choice of Debian or Ubuntu) in the Bios settings and removing the microSD carrier from the USB slot, I could boot from the

SSD into Debian. I manually updated the /etc/apt/sources.list to my preferences and performed an update/upgrade. I then loaded my desired software including the kernel build tools.

At thus stage I was still unable to use the USB3 port so I modified my kernel config for USB 3.0 OTG and other tweaks I felt necessary, then recompiled my kernel. After installing and

updating firmware modules (as above in '/lib/firmware), I still could not boot from the USB 3 port but USB2 ports worked fine. I was using a Lindy 31612 OTG microb to USB3 type A

female (UP have a similar cable in their shop) and the a USB type Male to Sata cable. I attached a spare SSD drive to the USB 3 port (using the aforementioned cables). The drive

produced a lot of error messages in 'dmesg' and '/var/log/kern.log' as the drive was attaching and detaching wildly. I thought the might have problems with power but that was not so. I

examined the male and female USB3 plug and socket an realised that not all pins mate and probably do not pass the correct signal pairs between each other. After much head scratching I

tried a spare WD Passport drive which has a USB3 MicroB and the drive attached and the error messages stopped. I was able to mount the drive and perform test file loading and deleting.

At this point, I rushed out and bought the cheapest USB external drive (for laptop backup) I could find with a microB connector. I forced the case of the drive open, removed the HDD

and carefully disconnected the MicroB to Sata pcb. I then powered the UP-board down, disconnected the SSD with Debian, etc. on it, attached the MicroB to Sata PCB and reassembled the

drive case as best I could. I attched the drive to the USB3 MicroB port on the UPboard via the Lindy 31612 and the external drive cable. I powered on the UP-board and after much

waiting, the UP-board brought up Debian with Xfce4 (my preferred GUI) using kernel (my variant) 5.11.16-upboard4.

I now have to update the kernel modules to, in particular, insert IPv6 and CIFS support. I am trying to keep as much of the kernel out of the limited 2Gb DRAM.

Have fun, Tony Pemberton

We use the script to reset the concentrator. By default is set on GPIO7. We try this script in all available GPIO pins, but it is still not working.

Any ideas?

Can anyone help me please?

There seems to be modules w1_gpio and w1_therm kernel modules in the linux-image-generic-hwe-16.04-upboard.

Are those fully supported? I can load them, but so far no luck getting them working with digital temperature sensor attached to GPIO pins.

Are there kernel sources available?

Br,
Jari

I have a new piece of UP Core 1GB.
I also have an installation flash drive with Lubuntu 18.04 (from which the installation works on another computer and some time ago I used the same installation on another piece of Up Core).
The HUB is connected to the USB and a keyboard, mouse, and flash drive are connected to it.
The keyboard and mouse work.
Once launched, the screen will prompt you to enter a password, and after entering it, you can set up Aptio Setup Utility 2017.

But it never starts loading the OS from the flash drive.
I also tried default settings and disconnecting the RTC battery.

Can you please advise how to install the OS?

Unfortunately, a camera I want to use with this board only supports up to kernel version 4.14. I'd like to be able to use the camera and the GPIO pins at the same time. I've not been able to find any older versions of the UP board kernel that enables the GPIO to be used.

Is there a link somewhere to an archive of old kernel versions that are pre 4.14?

I am using Up-board, I have built the image using Yocto-Pyro.
By default the Image is managed by systemV, I have added systemd by adding the line DISTRO_FEATURES_append = " systemd" in my local.conf file.
I build the image, the image booted and worked.
Now what I am trying to do is to make partition in external SD-card using parted utility. The partions fs is ext4.
(Partioning script)
yes | /usr/sbin/parted --script /dev/sda -- \
mklabel gpt \
mkpart primary ext4 1Mib 256Mib \
mkpart primary ext4 256Mib 512Mib \
mkpart primary ext4 512Mib 640Mib \
mkpart primary ext4 640Mib 768Mib \
mkpart primary ext4 768Mib 100%

While doing this I am getting an strange error that I could not figure out.
Error: Partition(s) 1, 2, 3, 4, 5 on /dev/sda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

Does anybody know how to encounter this error?

Thanks
Munawar Ali

We found spi in the kernel is stuck by irq, but we have no idea about that.

I've been testing an Up Board with a variety of I2C peripherals and encountering some problems with buggy I2C devices. Occasionally I will run into a situation where I2C read/writes will timeout, and the bus master loses arbitration. i2cdetect gets stuck. If I unplug the I2C devices, and replug them back in, everything usually works again, but this isn't a long term solution that works automatically. I need a system that can recover from faults like this.

I've read various articles such as AN-686 which discusses clocking out the problem.
https://www.analog.com/media/en/technical-documentation/application-notes/54305147357414AN686_0.pdf
I tried this out, and was able to sometimes recover the bus by using the GPIO pins attached to the I2C lines to toggle SCL ten times, and then SDA ten times. The bus would become available again, and i2cdetect would work again. However, I found other situations where it appears like the I2C master itself was stuck. I could unplug the I2C peripherals, and it was still stuck. Rebooting the Up Board did fix the problem, so it appears like it could be correctable in software.

I tried messing with the I2C driver but that did not fix anything.
echo -n "808622C1:00" > /sys/bus/platform/drivers/i2c_designware/unbind
echo -n "808622C1:01" > /sys/bus/platform/drivers/i2c_designware/unbind
echo -n "808622C1:00" > /sys/bus/platform/drivers/i2c_designware/bind
echo -n "808622C1:01" > /sys/bus/platform/drivers/i2c_designware/bind

Rather than doing these hacks that aren't working, is there a better way to recover?
(1) How to reset the onboard I2C master on the UpBoard without a reboot?
(2) How to clock out the bus to unlock any peripherals on the I2C bus?

I'm using Ubuntu 18.04 with the upboard kernel: 4.15.0-37-generic #40~upboard06-Ubuntu

Thanks.

I would to run python script after each start of my UP Board. For that, i used cron to do it.

In my crontab i wrote this :
@reboot sleep 90 && /usr/bin/python3.5 /usr/bin/myScriptPython.py

The problem is that my script does not always run, after starting of my UP Board.

So can you help me please ?

We are using a Up2 board with Yocto Sumo branch(linux kernel 4.14.92)

We are trying to use linux gpio 430 for interrupt handling. But, we dont see the interrupt handler invoked. Is it a known issue with workarounds as I see some fixes for 4.19 kernel

Code:
+static int register_gpio(void)
++{
++ if(gpio_request_one(IRQ_GPIO, GPIOF_IN, "MCU_sel") < 0) {
++ printk(KERN_ALERT "GPIO %d cannot be used\n", IRQ_GPIO);
++ return -EBUSY;
++ }
++ if ( (irq_line = gpio_to_irq(MCU_IRQ_GPIO)) < 0)
++ {
++ printk(KERN_ALERT "Gpio %d cannot be used as interrupt\n",IRQ_GPIO);
++ return -EINVAL;
++ }
++ if ( (irq_req_res = request_irq(irq_line, MCU_irq_handler, IRQF_TRIGGER_FALLING, "MCU_IRQ_GPIO", NULL)) < 0)
++ {
++ printk(KERN_ERR " registering irq failed\n");
++ return -EINVAL;
++ }
++ printk(KERN_INFO "select switch GPIO is registred\n");

++ return 0;
++}
++

Could UP Squared board supports tensorflow 2.0? As I tried to run tensorflow 2.0 and I receive an error message of illegal instruction (core dumped).

Although I solved this issue by downgrade the tensorflow version, but the keras requires a higher version of tensorflow to perform.

Anyone is facing this issue or solved this issue?

Thank you.

$ sudo setserial -g /dev/ttyS[01234]
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
/dev/ttyS4, UART: 16550A, Port: 0x0000, IRQ: 39

I've got a loop back on pin 8,10 and no longer have a working serial port.

Suggestions?

i'm new in the UP community and on the first day i got an annoying Issue:
I wanted to setup Ububtu on my UP-Squared following these instructions https://wiki.up-community.org/Ubuntu#Install_Intel_graphic_driver .

The first steps were quite simple but then i tried to update the grafics driver... The Update tool is outdated and in the "manual" way i don't know which grafic driver to choose.
Is there anybody who can tell me, what i need to install so the grafics is running with the latest driver?

A second question: Is there a way to check the functionality of the Intel grafic chipset? I performed some little KERAS scripts with TENSORFLOW as backend and the speed is, hm like on an really old Laptop without GPU...

NOTE: My board is https://up-shop.org/up-boards/106-up-squared-pentium-quad-core-8gb-memory128gb-emmc.html

Thanks in advance for a reply!

my UP board runs perfectly Ubuntu 18.04. I did install as well the fix for file /etc/pulse/default.pa like given as hint in the wiki.

However, when I open settings of Ubuntu and go to "Sound" I have still no device listed there. I try to get the Audio via the HDMI cable.

I'm sure you got that working. So those of you: could you pls help and tell me what's needed??
Thx in advance!!

thomas

linux-image-extra-virtual-hwe-18.04-upboard - Extra drivers for Virtual Linux kernel image
linux-image-generic-hwe-18.04-upboard - UP board Linux kernel image
linux-image-lowlatency-hwe-18.04-upboard - lowlatency Linux kernel image
linux-image-virtual-hwe-18.04-upboard - Virtual Linux kernel image
linux-signed-image-generic-hwe-18.04-upboard - Signed Generic Linux kernel image
linux-signed-image-lowlatency-hwe-18.04-upboard - Signed Lowlatency Linux kernel image

Did anyone encounter the same problem?

There is error message showed :

py@ubilinux4:~$ sudo add-apt-repository ppa:ubilinux/upTraceback (most recent call last):
File "/usr/bin/add-apt-repository", line 95, in
sp = SoftwareProperties(options=options)
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in init
self.reload_sourceslist()
File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 599, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for ubilinux/dolcetto
py@ubilinux4:~$

What should I do in order to have sucesfully added repository ?

I was using PWM to control a cooling fan with the up2 for a while now and it was working until a recent system update (with updates to linux and linux-firmware).
I get 'Device or resource busy' error, see:

$ echo 0 > /sys/class/pwm/pwmchip0/export
$ echo 3413333 > /sys/class/pwm/pwmchip0/pwm0/period
/usr/bin/echo: write error: Device or resource busy
$ echo 1706667 > /sys/class/pwm/pwmchip0/pwm0/duty_cycle
/usr/bin/echo: write error: Invalid argument
$ echo 1 > /sys/class/pwm/pwmchip0/pwm0/enable 

I am on arch linux:

$ uname -a                                                                                                                                                                    
Linux up2 5.6.3-arch1-1 #1 SMP PREEMPT Wed, 08 Apr 2020 07:47:16 +0000 x86_64 GNU/Linux
$ sudo pacman -Qs linux-firmware                                                                                                                                              
local/linux-firmware 20200316.8eb0b28-1
    Firmware files for Linux

The latest 5.0 BIOS is used with restored/optimized defaults, except quiet boot is disabled and at IGD panel two settings are disabled.

In dmesg there are three 'pwm' related messages:

$ dmesg | grep -i pwm                                                                                                                                                         
[  +0.105524] pwm-lpss 0000:00:1a.0: can't derive routing for PCI INT A
[  +0.000005] pwm-lpss 0000:00:1a.0: PCI INT A: not connected
[Apr13 11:46] pwm-lpss 0000:00:1a.0: PWM_SW_UPDATE was not cleared

Does anyone have a suggestion what might prevent me from echoing to the files in pwm0? What could be blocking the channel?
I tried also pwm pin 33, channel 1 but got the same error.

Thanks a lot in advance!

PS. I have some udev rules that lets the gpiousers group access to the pwmchip directory so I do not need sudo (in case you wondered), see:

$ cat /etc/udev/rules.d/50-pwm.rules                                                                                                                                          
SUBSYSTEM=="pwm", PROGRAM="/bin/sh -c '\
    chown -R root:gpiouser /sys/class/pwm && chmod -R 770 /sys/class/pwm;\
    chown -R root:gpiouser /sys/devices/pci0000:00/0000:00:1a.0/pwm/pwmchip* && chmod -R 770 /sys/devices/pci0000:00/0000:00:1a.0/pwm/pwmchip*;\
'"