I would like to know if the following board would be compatible with the UP4000 and where to start on how to use it.
https://www.waveshare.com/wiki/RS485_CAN_HAT#Introduction

I do have doubts as the tutorial for this hat uses raspi-config, a raspian OS specific software. I guess that the UP board would be able to have the functionality to enable RS485 and allow ssh login through it as it is my goal.

Is there any documentation that relates the gpiochip and line to the 40pin interface?
Comments in the forum suggest the following:
https://github.com/up-board/up-community/wiki/Pinout
But I can't find the gpiochip(n) and line(m) mapping. Where can I find this?

Through some testing, I was able to toggle the blue LED, and some GPIO's that I configured in the BIOS as outputs. Here is what I've found:

For example, the following toggles the Blue LED:
gpioset gpiochip0 73=1
gpioset gpiochip0 73=0

The following toggles pin 13 (also referred to as UP pinout GPIO4, or Linux GPIO 27).
gpioset gpiochip1 75=1
gpioset gpiochip1 75=0

FYI - using a previous kernel with sysfs(Centos 7.x), I was able to toggle pin 13 using the following
echo "1" >> /sys/class/gpio/gpio432/value
echo "0" >> /sys/class/gpio/gpio432/value
But this is now deprecated.

Here are a few pin associations I've been able to verify:
gpioset gpiochip1 38=$value #this controls pin 18
gpioset gpiochip1 74=$value #this controls pin 15
gpioset gpiochip1 73=$value #this controls pin 29
gpioset gpiochip1 37=$value #this controls pin 31

I can control a pin using gpioset, but when I read the same pin back, it sets the output to 0.
For example
gpioset gpiochip1 75=1 #output is asserted hi
gpioget gpiochip0 75 #this value reads back as zero, and the output is set to 0 (low).

Lastly, when I read chip0, pin 72, all three (red, green, yellow) LED's turn off.
gpioget gpiochip0 72 #turns off three LEDs

And when I try to set gpiochip0 72=1, the LED's do not restore.

Any clarification would be helpful.

We have been using numerous Up Squared Boards since 2020. On our Up2Boards, Ubuntu 20.04 is running with kernel version 5.15.0-71-generic. Recenly we had some problem with logs which weren't be written to the storage hardware. I had checked syslog and turned out these belows logs were present, preventing our program from writting.

logs

kernel: [  453.189298] mmc0: mmc_select_hs400 failed, error -84
kernel: [  453.189727] mmc0: mmc_hs400_to_hs200 failed, error -110
kernel: [  543.361872] mmc0: cache flush error -110
kernel: [  543.361894] blk_update_request: I/O error, dev mmcblk0, sector 60097648 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0
kernel: [  543.361935] Aborting journal on device mmcblk0p2-8.
kernel: [  543.362313] mmc0: mmc_hs400_to_hs200 failed, error -110
kernel: [  543.363365] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: comm systemd-journal: Detected aborted journal
kernel: [  543.363435] EXT4-fs error (device mmcblk0p2): ext4_journal_check_start:83: comm rs:main Q:Reg: Detected aborted journal
kernel: [  543.377308] EXT4-fs (mmcblk0p2): Remounting filesystem read-only

HW Specification

CPU

processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model       : 92
model name  : Intel(R) Pentium(R) CPU N4200 @ 1.10GHz
stepping    : 10
microcode   : 0x28
cpu MHz     : 2267.052
cache size  : 1024 KB
physical id : 0
siblings    : 4
core id     : 0
cpu cores   : 4
apicid      : 0
initial apicid  : 0
fpu     : yes
fpu_exception   : yes
cpuid level : 21
wp      : yes
flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 ds_cpl vmx est tm2 ssse3 sdbg cx16 xtpr pdcm sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave rdrand lahf_lm 3dnowprefetch cpuid_fault cat_l2 ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust smep erms mpx rdt_a rdseed smap clflushopt intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts md_clear arch_capabilities
vmx flags   : vnmi preemption_timer posted_intr invvpid ept_x_only ept_ad ept_1gb flexpriority apicv tsc_offset vtpr mtf vapic ept vpid unrestricted_guest vapic_reg vid ple shadow_vmcs
bugs        : spectre_v1 spectre_v2 spec_store_bypass
bogomips    : 2188.80
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

Memory

              total        used        free      shared  buff/cache   available
Mem:          7.6Gi       1.6Gi       4.0Gi       311Mi       2.0Gi       5.5Gi
Swap:         2.0Gi          0B       2.0Gi

Disk

Disk /dev/mmcblk0: 58.25 GiB, 62537072640 bytes, 122142720 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: gpt
Disk identifier: 2F1E8F6D-CD11-4FAC-A321-4D677EC5FA54

Device           Start       End   Sectors  Size Type
/dev/mmcblk0p1    2048   1050623   1048576  512M EFI System
/dev/mmcblk0p2 1050624 122140671 121090048 57.8G Linux filesystem

Since not every machine has this errors, but from time to time we have faced same issues.

Until today we have followed the process of unmount-mount -> fsck -> reboot. But this seems not the right solution for us.

Could there be any problem with emmc?

Any ideas from who also had encountered the same problem?

I am new enough to these boards/linux that any further info you want to share on stable hibernation with a quick wake up is also valuable to me, but I'm hoping someone can run 'cat /sys/power/mem_sleep' on an UP 4000 and let me know the options shown.

thank you.

=========
I have already tried the two solution from other post...

Method 1:
https://forum.up-community.org/discussion/comment/13367#Comment_13367

-install clean Ubuntu20.04.
-Install UP HAT pinctrl-upboard driver
-Clone the MRAA Project from up-division branch and add the UP4000 board name "UP-APL03" into src/x86/x86.c
-Build and install MRAA

Method 2:
https://forum.up-community.org/discussion/comment/13396/#Comment_13396

-Install Unbuntu 20.04 with "kernel 5.4.0 from PPA"
-Clone the MRAA Project from up-division branch and add the UP4000 board name "UP-APL03" into src/x86/x86.c
-Build and install MRAA

I have search the forums and all over the internet for an answer and have found nothing. I am attempting to set up a simply IR Receiver for use in a python program I am working on. I have tried setting it up through LIRC, through serial connection on each UART pin and have gotten nowhere. If anyone else has any input to help me get this working it would be greatly appreciated.

Board: UP4000
OS: Ubuntu 22.04
IR Receiver: DF Robot (DFR0094)

I'm evaluating how is the best way to use these boards (mainly Up-4000 for now) for some embedded projects, all Linux based and I'm mainly interested about using Ubuntu with only CLI, no direct user access.

After reading many messages I didn't find any FAQ related to Up-4000 and typical things to do, like install an OS, drivers, etc., especially on Linux.
Am I missed it ?

I also have few other specific questions.

1. What is the best way to develop something on the board ?
   i.e. for embedded development I usually prefer a cross-development environment and not having any GUI installed on the board.
   There are tested solutions out there maybe using IDE like IntelliJ or VisuaStudio ?
   If yes somebody has links/suggestions ?

2. For debug what is available ?
   Does the board has a Jtag ?
   A generic Gdb connected remotely is possible ?
   Or the only way is to connect a keyboard and monitor and go with a local GUI and development environment installed on the board itself ?

3. What would be the more supported language/environment to develop an app for the board ?
   The app would use different peripherals, like ZigBee probably interfaced via USB and probably others via the GPIO (SPI/I2C, etc.)
   I was thinking for example to use node.js and Kotlin but I'm not sure about the peripherals support.
   Maybe Python is better supported ? Or C/C++ ?
   Any suggestion ?
   Any language/environment is OK as long as there is some support for the specific peripherals on board.

4. On production there is the necessity to update the software, often OS and application on the field in unmanned way.
   There is a way, a mechanism to do that with these boards ?
   Some kind of service suggested ?

I do have a lot of more questions but these are the most important in order to decide if I can use these board for projects.

Thank you in advance for any help !!

Stefano

I am trying to connect the UP 4000 carrier board for WiFi and 5G module (This one: https://up-shop.org/default/up-4000-carrier-board-for-wifi-and-5g-module.html )

on a UP4000 but I can't find a guide or something to follow. Is there a wiki or something to do so?

I tried to do the bellow but in BIOS I have no PCI Express Configuration:
BIOS -> CRB Setup -> CRB Chipset -> South Closter Configuration -> PCI Express Configuration -> PCI Express Root Port 1 -> PCIe Speed => Change to Gen2.

BIOS -> CRB Setup -> CRB Chipset -> South Closter Configuration -> PCI Express Configuration -> PCI Express Root Port 1 -> PCIe Sekectable De-em => Change to Disable.
Thanks.

the question already have been asked here : https://forum.up-community.org/discussion/5191/problem-with-bios-for-spi-clock#latest.
but the BIOS provided made the I2C and SPI protocols stop working, reverting to the bios UPAPBM11 worked to get them working again, but I still have the BIOS problem.

So is there a working BIOS that can fix this problem, or a way to put the pin to output with code and not going into the BIOS?
I have to send the board in the sky, so I can't manually do it when it will be deployed, and since there is a possibility that the power come off and come back, I need to make the SPI working again.

I need to power cycle (switch-off then switch-on) a USB device attached to my UP 4000 while the UP board is on.

I tried to play with the uhubctl tool but it doesn't seem to be able to power off the USB connector. However, I observed that when I connect the USB device to the USB-C plug, the USB device is off, contrary to when it is connected to one of the 3 USB-A plugs (it remains on in this case). So, I still hope it should be possible to control in software the USB-C plug.

Does anybody know how to do that? Many thanks for any hints!

Thierry

I've installed the kernel 5.4.0 from PPA and the upboard-extras
I've created the GPIO, LED,... groups
But when I try to access the

cd /sys/class/gpio
root@up01:/sys/class/gpio# echo 432 > export
-bash: echo: write error: Invalid argument

If I use gpiodetect from pinctrl, I can well see the GPIO but I get errors doing accesses

arnaud@up01:/sys/class/gpio$ gpiodetect 
gpiochip0 [INT3452:00] (78 lines)
gpiochip1 [INT3452:01] (77 lines)
gpiochip2 [INT3452:02] (47 lines)
gpiochip3 [INT3452:03] (43 lines)
gpiochip4 [Raspberry Pi compatible UP GPIO] (28 lines)
gpiochip6 [ftdi-cbus] (4 lines)
arnaud@up01:/sys/class/gpio$ gpioget gpiochip4 0
gpioget: error reading GPIO values: Unknown error 517

The control of the LED is working well.
Is there some extra steps to do to get these working?

UP4000 with UP-APL03 R1.1 (UPAPBM11)(07/01/2022).

• Use lubuntu 18
• Bios UPAPBM11
• Installed the Upboard Kernel
• Configure support for the GPIO header (https://github.com/up-board/up-community/wiki/Ubuntu_18.04)
  But I get no returned chars on tty5.

I have many Up4000 board in my lab. So I tried to install in same condition and setup. Result is another 3 upboard can get chars from UART port.

How I can solve?

I am using c++. I already did the open() and ioctl() calls si Im just showing you the code that wont let me send the quick command.
if (write(busNumber, NULL, 0) != 0) { perror("could not ask the humidity sensor to take the measurement"); }

and

struct i2c_smbus_ioctl_data test;
test.read_write = I2C_SMBUS_WRITE;
test.command = 0;
test.size = I2C_SMBUS_QUICK;
test.data = NULL;
if (ioctl(busNumber, I2C_SMBUS, &test) < 0) {
   perror("ioctl error");
}

int the 2 cases I receive an Operation not supported error message, I believe it is because the quick command is not enabled, because doing a write with sending bytes is working.

is there a way that I could enable the quick command on my i2c bus? or that my code could bypass that.

Thank you

Please help me continue installing this board.
Thank you!

I also tested on Ubuntu 18.04.5 (kernel 5.4.0 from PPA) and Windows 10 Pro (Drivers Intel & Drivers provided UP 4000). I have not been successful, not enable and detected Wifi.

I'm interested in making it work on ubuntu 20.04

• I unpacked new , clean UP4000 from box.
• I installed clean Ubuntu20.04. there, no issue.

• Then I followed instructions on UP wiki and replaced kernel with 5.4.0 , again without issue. Restarted board, everything without issue.

• Then I clone mraa-master from git and updated src/x86/x86 as was sugested in different discussion :

@garyw said:
if you are using official mraa from Github with our up 5.4 kernel, you have add the UP4000 board name "UP-APL03" into src/x86/x86.c as

else if (strncasecmp(line, "UP-APL03", strlen("UP-APL03") + 1) == 0) {
platform_type = MRAA_UP2;
plat = mraa_up2_board();
}
}

, installed cmake, build-essential and so on... and compiled mraa.
Then I install it. Its all. No issue so far.

But regarding to mraa - there is issue to run it :

mraa-gpio version
Version v2.2.0 on Unknown platform

mraa-gpio list
No Pins

Can someone please get us step by step instructions, how to get mraa running on UP4000/Ububtu on "clean, just unpacked" UP4000 ?

I have an I2C Display, I would like to write onto it from my up4000 (linux)
What should I use for that ? I can't seem to have mraa working (any help ? is mraa supported on up4000? )

I have been able to use sysfs IO, and a C program to detect rising edges on some HAT pin (437).

Now my only problem left is writing on an I2C peripheral. I think 3 and 5 are the right pins, I think this is I2C controller 2 on the up4000. But then not sure what to do now.

Will I2c work with 3.3 or 5v ?

SOS

I have an I2C LCD display 16*2 very classic one, works with I2C with an arduino.

I would like to use it on my up4000 board, but I can't find any recipe.

Did someone ever manage to do that ?

The address of the display is 0x27
(Should I focus on libmraa ?)
Where can I find sample code that works.

I'm stuck

How can I have I2C work. (pins 3 and 5 on the hat connector are I2c One, right ?)
What kind of code can I use ?

everytime i try to install UBUNTU 20.04.5, Give me This error can you help me?

SOS.

Will there soon be a official support for Ubuntu 22.04 and kernel version 5.15 for the Up 4000? What is the limitations of using Ubuntu 22.04 now?

I have 2 up4000 boards, I need to communicate to a basic 16*2 I2c display.

What linux do I have to install. (can't I use that ubuntu server 20.04 HWE kernel ?)
What do I have to do ? Use libmraa ?

Please help I've been stuck for days now...