I get the following error when trying to build the latest version (2.13.1+rev1) of resin-raspberrypi:

ERROR: balena-native-17.06.0-dev+git73136d1985f28a34705f537e90636cf208734048-r0 do_compile: Function failed: do_compile (log file is located at /home/bruno/dev/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.06.0-dev+git73136d1985f28a34705f537e90636cf208734048-r0/temp/log.do_compile.25317)
ERROR: Logfile of failure stored in: /home/bruno/dev/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.06.0-dev+git73136d1985f28a34705f537e90636cf208734048-r0/temp/log.do_compile.25317
Log data follows:
| DEBUG: Executing shell function do_compile
| # WARNING! I don't seem to be running in a Docker container.
| # The result of this command might be an incorrect build, and will not be
| # officially supported.
| #
| # Try this instead: make all
| #
| 
| bundles/17.06.0-dev already exists. Removing.
| 
| ---> Making bundle: dynbinary-balena (in bundles/17.06.0-dev/dynbinary-balena)
| Building: bundles/17.06.0-dev/dynbinary-balena/balena-17.06.0-dev
| Created binary: bundles/17.06.0-dev/dynbinary-balena/balena-17.06.0-dev
| 
| # github.com/docker/docker/cmd/mobynit
| /home/bruno/dev/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.06.0-dev+git73136d1985f28a34705f537e90636cf208734048-r0/recipe-sysroot-native/usr/lib/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
| gcc: error: unrecognized command line option ‘-no-pie’
| 
| WARNING: exit code 2 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/bruno/dev/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.06.0-dev+git73136d1985f28a34705f537e90636cf208734048-r0/temp/log.do_compile.25317)
ERROR: Task (virtual:native:/home/bruno/dev/resin-raspberrypi/build/../layers/meta-resin/meta-resin-common/recipes-containers/balena/balena_git.bb:do_compile) failed with exit code '1'

gcc complains about the -no-pie option which it does not support.
Is there any minimum version of gcc required?

There was an issue discovered in the picamera firmware for the v2 camera, that the image is flipped horizontally, compared to the v1 camera by default. The fix has been applied in raspberrypi/firmware@20958cd and we should pull at least that version for our compilation as well.

For reference, the first meta-raspberrypi that has those changes as well is 5d79d24.

Front conversations

On RPI2 - and most probably on all our devices - systemd at boot reports:

[ 5.339571] systemd[1]: [email protected]: Cannot add dependency job, ignoring: Unit [email protected] failed to load: No such file or directory.

Add lcd_rotate pre-commented and documented in the config.txt in raspberypis. The same way we have it for display_roate.

This applies to the Raspberry Pi 7" LCD screen.

From @imrehg on December 1, 2017 22:54

Not all the boards use labels when selecting the root partition. For example raspberrypi uses root=mmcblk0pX .

Copied from original issue: balena-os/meta-balena#918

I am using the CentOS as host OS.

$ uname -r
4.18.3-1.el7.x86_64

but there is one last error to build the image as below. Can anyone give insights to solve?

ERROR: balena-native-17.12.0-dev+git2fe3ad1568c1b783a9201fc3082452ad79d7f396-r0 do_compile: Function failed: do_compile (log file is located at /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.12.0-dev+git2fe3ad1568c1b783a9201fc3082452ad79d7f396-r0/temp/log.do_compile.17054)
ERROR: Logfile of failure stored in: /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.12.0-dev+git2fe3ad1568c1b783a9201fc3082452ad79d7f396-r0/temp/log.do_compile.17054
Log data follows:
| DEBUG: Executing shell function do_compile
| # WARNING! I don't seem to be running in a Docker container.
| # The result of this command might be an incorrect build, and will not be
| # officially supported.
| #
| # Try this instead: make all
| #
| 
| Package devmapper was not found in the pkg-config search path.
| Perhaps you should add the directory containing `devmapper.pc'
| to the PKG_CONFIG_PATH environment variable
| No package 'devmapper' found
| Removing bundles/
| 
| ---> Making bundle: dynbinary-balena (in bundles/dynbinary-balena)
| Building: bundles/dynbinary-balena/balena-17.12.0-dev
| Created binary: bundles/dynbinary-balena/balena-17.12.0-dev
| 
| # github.com/docker/docker/cmd/mobynit
| /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.12.0-dev+git2fe3ad1568c1b783a9201fc3082452ad79d7f396-r0/recipe-sysroot-native/usr/lib/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
| gcc: error: unrecognized command line option ‘-no-pie’
| 
| WARNING: /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.12.0-dev+git2fe3ad1568c1b783a9201fc3082452ad79d7f396-r0/temp/run.do_compile.17054:1 exit 2 from 'go build -ldflags '-extldflags "-static  -no-pie"' .'
| ERROR: Function failed: do_compile (log file is located at /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/x86_64-linux/balena-native/17.12.0-dev+git2fe3ad1568c1b783a9201fc3082452ad79d7f396-r0/temp/log.do_compile.17054)
ERROR: Task (virtual:native:/home/AAAA/resinOS/resin-raspberrypi/build/../layers/meta-resin/meta-resin-common/recipes-containers/balena/balena_git.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3771 tasks of which 3770 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  virtual:native:/home/AAAA/resinOS/resin-raspberrypi/build/../layers/meta-resin/meta-resin-common/recipes-containers/balena/balena_git.bb:do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
[000000036][LOG]Build for raspberrypi3 failed. Check failed log in build/tmp/log/cooker/raspberrypi3 .
[000000036][LOG]If build for raspberrypi3 succeeded, final image should have been generated here:
[000000036][LOG]   build/tmp/deploy/images/raspberrypi3/resin-image-raspberrypi3.resinos-img
[000000036][LOG]Done.

Due to balena-os/meta-balena#812 we want to update the wifi firmware to the one provided by Raspbian - as the issue above can't be reproduced with that version.

Update the dependant layers to Yocto Pyro.

There is a PR open here: #122

RPI3 has an on board firmware that should be installed by the BSP layer. Update the BSP layer to include this support.

Steps to reproduce issue

Connect to the HDMI connected to a monitor
Boot the device

Expected result

Resin logo splash screen should be visible

Actual result

RaspberryPi: No splash screen at boot

Other information

Reported by: Andrei Gherzan

Test configuration: RaspberryPi

Test case number: TC07

Test run: https://resinio.testlodge.com/projects/16238/runs/192879?tab=2&run_section_id=168778&executed_case_id=9333888#executed_case_9333888

This is caused by the set of console=tty1 in the kernel cmdline.
NOTE: If no console is provided to the kernel then it will default to tty0 which will link to the first display (i.e. serial port)

The U-boot configuration for RaspberryPi Zero and Zero WiFi differ in terms of serial console configuration which makes the latter hang the boot.

There is work upstream which unifies this support for a very similar case: RaspberryPi 3 and CM3. See http://u-boot.10912.n7.nabble.com/PATCH-v3-00-15-RPi-Properly-handle-dynamic-serial-configuration-td318851.html

It seems that occasionally when a container is started and the container udev triggers a udev replug, that the kernel will panic with this modem attached. This affects resinOS v2.7.5 on the raspberry pi family.

Front conversations

Check if the current sd8887_uapsta.bin firmware in the pi3 image is the latest. If it is not, then bump the linux-firmware revision to latest available (through an append similar to https://github.com/resin-os/resin-intel/blob/master/layers/meta-resin-genericx86/recipes-kernel/linux-firmware/linux-firmware_git.bbappend where you only specify the new revision) and then add the corresponding package here https://github.com/resin-os/resin-raspberrypi/blob/master/layers/meta-resin-raspberrypi/recipes-core/packagegroups/packagegroup-resin-connectivity.bbappend to make sure this firmware makes its way into the rootfs

Discussion: https://www.flowdock.com/app/rulemotion/resin-projects/threads/OQ1PVEwq2mpdX4HOvH4qI93Da0M

The hyperpixel should be supported, and does work with a prod OS for both the pi 3 & pi zero, if you add the overlays and config.txt lines from that readme. However, if you follow the same process on a dev build then the OS does not boot, and after a brief initial blinking the ACT light goes solid green.

This seems to be caused by the enable_uart=1 line in config.txt. If that is removed, dev builds then boot.

Unclear whether this is an actual bug, or simply something that needs to be better documented.

I have a custom kernel module that needs to get recompiled and it would help to be able to scan the notes to know when the kernel is updated (which triggers the need to recompile).

Hi all,

I tried to make an image for raspberry pi 3 target under master branch (by using ./resin-yocto-scripts/build/barys -r --shared-downloads $(pwd)/shared-downloads/ --shared-sstate $(pwd)/shared-sstate/ -m raspberrypi3 command) and I experienced the following problem:
...
NOTE: Running task 1755 of 3227 (/home/khang/Workspace/GIT/resinos/resin-raspberrypi/build/../layers/meta-openembedded/meta-oe/recipes-devtools/jq/jq_1.5.bb:do_compile)
NOTE: recipe jq-1.5-r0: task do_compile: Started
ERROR: jq-1.5-r0 do_compile: oe_runmake failed
ERROR: jq-1.5-r0 do_compile: Function failed: do_compile (log file is located at /home/khang/Workspace/GIT/resinos/resin-raspberrypi/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/jq/1.5-r0/temp/log.do_compile.31306)
ERROR: Logfile of failure stored in: /home/khang/Workspace/GIT/resinos/resin-raspberrypi/build/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/jq/1.5-r0/temp/log.do_compile.31306
NOTE: recipe jq-1.5-r0: task do_compile: Failed
ERROR: Task (/home/khang/Workspace/GIT/resinos/resin-raspberrypi/build/../layers/meta-openembedded/meta-oe/recipes-devtools/jq/jq_1.5.bb:do_compile) failed with exit code '1'
...

Could anyone have a solution, please?

Best regards,
Pascal
20171002045420.log
console-latest.log

I shut the device down and the power cycled it and the Bluetooth interface never initialised correctly. These are the logs from dmesg:

root@a6cfd31:~# dmesg | grep Blue*
[   15.275877] Bluetooth: Core ver 2.22
[   15.291339] Bluetooth: HCI device and connection manager initialized
[   15.291473] Bluetooth: HCI socket layer initialized
[   15.291482] Bluetooth: L2CAP socket layer initialized
[   15.291539] Bluetooth: SCO socket layer initialized
[   15.297374] Bluetooth: HCI UART driver ver 2.3
[   15.297378] Bluetooth: HCI UART protocol H4 registered
[   15.297380] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   15.297492] Bluetooth: HCI UART protocol Broadcom registered
[   17.368161] Bluetooth: hci0 command 0x0c14 tx timeout
[   19.449713] Bluetooth: hci0 command 0x0c25 tx timeout
[   19.866079] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   19.871695] Bluetooth: BNEP filters: protocol multicast
[   19.888387] Bluetooth: BNEP socket layer initialized
[   21.528158] Bluetooth: hci0 command 0x0c38 tx timeout
[   23.608167] Bluetooth: hci0 command 0x0c39 tx timeout
[   25.688217] Bluetooth: hci0 command 0x1003 tx timeout
[   27.768211] Bluetooth: hci0 command 0x1001 tx timeout
[   29.848213] Bluetooth: hci0 command 0x1009 tx timeout
[   37.848157] Bluetooth: hci0 command 0x1003 tx timeout
[   39.928160] Bluetooth: hci0 command 0x1001 tx timeout
[   42.008162] Bluetooth: hci0 command 0x1009 tx timeout

It seems related to agherzan/meta-raspberrypi#148

Although we're still debugging this one on our end, I wanted to create this issue in case anyone else has run into this.

Starting with release 2.7.4+rev1, all of our I2C reads began returning 0xFF. In 2.7.2+rev1 and prior, this behavior is not observed.

We have tested several releases since 2.7.4 (including 2.9.7+rev1) and find the same behavior. Reverting back to 2.7.2+rev1 or earlier always resolves this issue.

Note that scanning devices (via i2cdetect) behaves as expected. Even writing to the I2C device succeeds. We are performing our tests via a Debain container with privileged mode enabled on a Raspberry Pi 3.

Based on various reports, such as raspberrypi/linux#1866 , we should stick to using the OOT wifi module which also gets built in our OS.
At this point we ship both the 8192cu.ko and the rtl8192cu.ko wifi modules and none is blacklistedf which makes wifi on this adaptor break anyway

This was introduced after we have passed console=null to our kernel.
The issue here is a missing dependency on systemd-udev-settle. i.e. the trigger on the graphic and tty subsystems are not settled.
Also plymouth was depending on the console option to determine the output interface a --tty option should be passed to the daemon.

follow the guidance @ https://resinos.io/docs/custombuild/ but always failed at this step:

HostOS - CentOS7 Linux 3.10.0-862.9.1.el7.x86_64

=====
ERROR: resin-image-1.0-r0 do_rootfs: /home/AAAA/resinOS/resin-raspberrypi/build/tmp/deploy/images/raspberrypi3/u-boot.bin is an invalid path referenced in RESIN_BOOT_PARTITION_FILES.
ERROR: resin-image-1.0-r0 do_rootfs: Function failed: resin_boot_dirgen_and_deploy (log file is located at /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/resin-image/1.0-r0/temp/log.do_rootfs.99737)
ERROR: Logfile of failure stored in: /home/AAAA/resinOS/resin-raspberrypi/build/tmp/work/raspberrypi3-poky-linux-gnueabi/resin-image/1.0-r0/temp/log.do_rootfs.99737
ERROR: Task (/home/AAAA/resinOS/resin-raspberrypi/build/../layers/meta-resin/meta-resin-common/recipes-core/images/resin-image.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3135 tasks of which 3134 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/AAAA/resinOS/resin-raspberrypi/build/../layers/meta-resin/meta-resin-common/recipes-core/images/resin-image.bb:do_rootfs

The EGL bug was fixed in userspace in our base images

Description

Test serial port when switched to ttyAMA0.

Steps to reproduce issue

Have a new Raspberrypi 3 device provisioned or use one that is already provisioned with an image for this release that has no "Device Configuration" variables configured.
Attach a serial and start a text-based modem control - ex minicom by issuing a similar command to "minicom -b 115200 -o -D /dev/tty***". Replace the tty device accordingly to your host.
Set a "Device Configuration" variable as it follows: RESIN_HOST_CONFIG_dtoverlay=pi3-miniuart-bt-overlay

Expected result

Device should reboot.
You should see booting messages on serial. As well, getty should be advertised as spawned on ttyAMA0 with a login message similar to: Resin OS X.X raspberrypi3 ttyAMA0

Actual result

No output on serial, also having set "enable_uart = 1" in config.txt in addition to this

Other information

Reported by: Florin Sarbu

Test configuration: RaspberryPi 3

Test case number: TC19

Test run: https://resinio.testlodge.com/projects/16238/runs/215816?tab=2&run_section_id=218234&executed_case_id=10147497#executed_case_10147497

I built the image following the https://resinos.io/docs/custombuild/#bake-your-own-image.

using the tagged version 2.13.6.

looks like it succeeded. then I use the Etcher in Windows to flash the built image to SD card. but when booting, the RPI stopped at the yellow logo screen and can't boot correctly.

Anyone know why?

PS: if I flash (also using the Etcher) the downloaded image from resinos.io, it can boot correctly.

PS: the built image and the downloaded image have the same size. 1.68 GB (1,807,745,024 bytes)

On raspberry pi the Quectel EC20 modem was working fine on v2.3.0, but it seems the upgrade to the 4.9 kernel of raspberry pi may have caused them to stop working. I believe its related to some patches that were added to 4.9 as referenced here: https://lists.freedesktop.org/archives/libqmi-devel/2017-February/002067.html and here: http://www.spinics.net/lists/linux-usb/msg156311.html

We decided to stop using subtype_of and allow each application add any device type of the same architecture as the main device type the application was created with.

The Raspberry Pi doesn't have an RTC so if the unit fails to get the correct time, it can have trouble connecting to the OpenVPN server. I had that happen on a few networks where NTP was blocked and the unit was not able to connect.

For the Raspberry Pi units that don't have a physical hardware clock, the fake-hwclock package is very useful as it ensures that the clock moves forward after reboot and prevents the time going back to the year 2000.

An even better solution is to add this little device: https://www.ebay.co.uk/i/253056413179?chn=ps&dispItem=1&adgroupid=41920510205&rlsatarget=pla-325751485803&abcId=1128926&adtype=pla&merchantid=109797754&poi=&googleloc=9045006&device=c&campaignid=856841495&crdt=0

To set it up on the RPI, you run:

echo ds1307 0x68 | tee /sys/class/i2c-adapter/i2c-1/new_device

After that, the command hwclock starts to work:

root@resin:/# hwclock   
Sat Jan  1 23:18:01 2000  0.000000 seconds
root@resin:/# hwclock -w
root@resin:/# hwclock
Mon Aug 14 17:19:11 2017  0.000000 seconds

It would be great if support for the above was added to ResinOS out of the box.

Front conversations

Hi,

I am trying to build a LoraServer on a Raspberry Pi 3 with Stretch using resin.io but i cannot install postgresql and I from what I have looked this is due to the fact that this image is build on debian:stretch-slim.

To install it I simply use (I also tried to wget the repository and add the deb file):

`RUN apt-get update && apt-get install -y --no-install-recommends postgresql (also tried with postgresql-9.6) postgresql-client postgresql-contrib && rm -rf /var/lib/apt/lists/*`

On git push an error is displayed:

[main] Setting up postgresql-client-9.5 (9.5.4-3) …
[main] update-alternatives: using /usr/share/postgresql/9.5/man/man1/psql.1.gz to provide /usr/share/man/man1/psql.1.gz (psql.1.gz) in auto mode
[main] update-alternatives: error: error creating symbolic link ‘/usr/share/man/man7/ABORT.7.gz.dpkg-tmp’: No such file or directory
[main] dpkg: error processing package postgresql-client-9.5 (–configure):
[main] subprocess installed post-installation script returned error exit status 2
[main] dpkg: dependency problems prevent configuration of postgresql-9.5:
[main] postgresql-9.5 depends on postgresql-client-9.5; however:
[main] Package postgresql-client-9.5 is not configured yet.
[main] dpkg: error processing package postgresql-9.5 (–configure):
[main] dependency problems - leaving unconfigured

Which ends up with this message:

[main] Errors were encountered while processing:
[main] postgresql-client-9.5
[main] postgresql-9.5
[main] postgresql-contrib-9.5
[main] E: Sub-process /usr/bin/dpkg returned an error code (1)

And finishes with : [Error] Not deploying release.

Did anyone else had this problem ? How can it be fixed ?

Best regards,
becklo

Front conversations

All the bluez related operations should be handled from the container leaving the container to device the Bluetooth device (s0 or ama0), baudrate etc.

Deactivate brcm43438.service in resin.

hostapps update fails because it tries to do an atomic update (a move operation of a file to be updated in the same partition) but the free space available in the boot partition is less than the file size (kernel in our failure case) for which it tries to do the atomic update

Any help here would be immensely appreciated... I'm attempting to get the Hyperpixel up and running on the latest ResinOS.

I've seen others have had success, but I'm unable to sort out what to change. I've provided the overlay in the boot folder, but I'm unable to get anything to display when setting display_default_lcd=1

I've attached my custom config variables for reference.

We want to migrate to choosing the rootfs based on a counter. As we can't do this in the proprietary bootloader, we will need to integrate uboot first.

The current kernel doesnt have the patch set to include the vc4 driver
The required firmware is here:
https://github.com/raspberrypi/firmware/tree/master/modules/4.1.19%2B

Why is that for rpi3?

Amber has a PCA955 IO expander module. This IC has support in linux kernel, so I think we just need to enable: GPIO_PCA953X and GPIO_PCA953X_IRQ

config GPIO_PCA953X
	tristate "PCA953x, PCA955x, TCA64xx, and MAX7310 I/O ports"
	depends on I2C
	help
	  Say yes here to provide access to several register-oriented
	  SMBus I/O expanders, made mostly by NXP or TI.  Compatible
	  models include:

	  4 bits:	pca9536, pca9537

	  8 bits:	max7310, pca9534, pca9538, pca9554, pca9557,
	  		tca6408

	  16 bits:	pca9535, pca9539, pca9555, tca6416

config GPIO_PCA953X_IRQ
	bool "Interrupt controller support for PCA953x"
	depends on GPIO_PCA953X=y
	help
	  Say yes here to enable the pca953x to be used as an interrupt
	  controller. It requires the driver to be built in the kernel.

The new device type will have the slug fincm3 and will specify a subtype_of being raspberrypi3.

This was discussed in the architecture call (2018-05-01). See: https://docs.google.com/document/d/1TiA3kt7zU8ce9mlNl5EWymfQ41VWW_xPZGHSMgDORPw/edit

Switch bt to use ttyS0 (by using "dtoverlay=pi3-miniuart-bt" in config txt) and then also use "enable_uart=1" in config.txt and bt will not work. If instead one uses "force_turbo=1" or "core_g=freq=250" in config.txt then bt works on ttyS0.

Needs investigation on why "enable_uart=1" it not enough to make bt work (https://www.raspberrypi.org/documentation/configuration/uart.md)

Setting this config doesn't change the serial0 in cmdline accordingly which seems to be ttyS0 no matter what.

Pi Zero can be powered and accessed from single USB port (it appears as Ethernet device). That functionality is currently missing in ResinOS, as the necessary modules / kernel version are missing (they are included in 2016-05-10 release of Raspbian).

Full info: http://blog.gbaman.info/?p=791

Short guide:
https://gist.github.com/gbaman/975e2db164b3ca2b51ae11e45e8fd40a

The board is unable to connect to resin VPN when using an U-blox Toby-L210 modem in RNDIS mode.

The error reported by the openvpn is the following: https://openvpn.net/index.php/open-source/faq/79-client/253-tls-error-tls-key-negotiation-failed-to-occur-within-60-seconds-check-your-network-connectivity.html

If the modem is switched to ECM mode, the VPN connection works OK.

This bug is present on ResinOS v2.9.6, but not on v2.3.0.

Related Front link: https://app.frontapp.com/open/cnv_gswxkp

Front conversations

The fincm3 device type defines the provisioning instructions https://github.com/resin-os/resin-raspberrypi/blob/master/fincm3.coffee#L25. This ends up in the UI with a duplicated last step:

Your device should appear here in about 10 minutes. Have fun!
Your device should appear in your application dashboard within a few minutes. Have fun!

We should remove one of them.

Observed on the Balena Fin board (also on a custom rpi3 board), rpi3, rpi zero, rpi2

The raspberrypi firmware is currently producing a rainbow splash and a smaller rainbow splash to illustrate different warnings, at boot time. We should disable both of these in our production images.