Raspberry pi 5 status

bxbzq said:
SHA512 is correct.
I used dd command and it looks success.
Click to expand...

Hmm, not sure if sha512 is totally correct though. Is this "improperly formatted" message normal?
% sha512sum -c CHECKSUM.SHA512-FreeBSD-14.2-RELEASE-arm64-aarch64-RPI FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz: OK
sha512sum: WARNING: 2984186 lines are improperly formatted
Click to expand...
 
I don't know if this is normal, i've never used sha512sum with the -c parameter.

Try without it and copy the resulting hash into your clipboard, and use the search function of your browser to compare the hash with the one in my previous post.
 
eternal_noob said:
I don't know if this is normal, i've never used sha512sum with the -c parameter.

Try without it and copy the resulting hash into your clipboard, and use the search function of your browser to compare the hash with the one in my previous post.
Click to expand...
1740045974543.png


I'm convinced the hash code of the downloaded image file is correct.
 
bxbzq said:
Hmm, not sure if sha512 is totally correct though. Is this "improperly formatted" message normal?
Click to expand...
I've just downloaded the image and the checksum file, put them together in a direction, run the command and didn't receive any error message.
Code: 
iso $ sha512sum -c CHECKSUM.SHA512-FreeBSD-14.2-RELEASE-arm64-aarch64-RPI
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img.xz: OK
iso $

"improperly formatted" I saw this message a lot in the past when I was on Linux, it's a common error, but is not relevant if the hash is the same, it's not difficult to verify just run the command sha512sum without any option and compare with the checksum file using your eyes only, not fun but it works ;)
 
this is what i do when i need to verify checksum of a file when there is no checksum file provided by but a hash instead.

1. Calculate hash of downloaded file.
sha256sum file-x-y-z > checksum
2. Copy the original hash and replace current file hash with the original one
$EDITOR checksum
Code: 
## current file hash
c9b25de21a3b1934187476d7f6d79d724b73355a01046b059264ed4fa72fc2bc  file-x-y-z
## replace current hash with original hash
2fa9906bcfa80ca875807baafc3a53dc14ad08c0d2774a2ad9af9478e3870b3c  file-x-y-z
3. Run checksum control with -c flag to verify hash from a file.
Code: 
sha256sum -c checksum
file-x-y-z: OK
 
After multiple downloads and burns using different tools (raspberry imager, dd and win32diskimager) and under different systems(raspberry, FBSD and windows), i believe the image file I download is correct, even the sha512 checksum gives me "improperly formatted" message. Followed the instructions downloaded RPi5_UEFI_Release_v0.3.zip and copied the 3 files to the root of EFI partition of SD card. The problem is when I try to boot the system it stops the half way. See attached picture.
 

Attachments

  • IMG_7438.JPEG
    IMG_7438.JPEG
    1.1 MB · Views: 290
Can you write same image to a USB flash drive stick and boot from a USB flash drive stick on your Raspberry Pi 5? The last 3 lines in your photo detail the problem as being a bad file system 'inode' that the FreeBSD boot sequence can not read the /bin/sh file to execute that file that does not exsist. A solution write image to a USB Flash drive, then fsck the UFS file system on the USB flash drive stick in an unmounted condition. Correct the filesystem error in the UFS filesystem. Mount Then make an image of the corrected filesystem USB flash drive stick. Write this corrected image to your SD card to boot with. Tell us how it goes for you. Sorry for complicated instructions, for a bad image file. Other may suggest other methods to fix problems, or try a 14.1 image in place of a 14.2 image?
https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.1/
https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.2/
 
wb7odyfred said:
Can you write same image to a USB flash drive stick and boot from a USB flash drive stick on your Raspberry Pi 5? The last 3 lines in your photo detail the problem as being a bad file system 'inode' that the FreeBSD boot sequence can not read the /bin/sh file to execute that file that does not exsist. A solution write image to a USB Flash drive, then fsck the UFS file system on the USB flash drive stick in an unmounted condition. Correct the filesystem error in the UFS filesystem. Mount Then make an image of the corrected filesystem USB flash drive stick. Write this corrected image to your SD card to boot with. Tell us how it goes for you. Sorry for complicated instructions, for a bad image file. Other may suggest other methods to fix problems, or try a 14.1 image in place of a 14.2 image?
https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.1/
https://download.freebsd.org/ftp/releases/ISO-IMAGES/14.2/
Click to expand...
This is helpful tip. I wrote the image to a USB flash drive then I can boot using it. I thought SD card was the only option to boot with.
 
Does anyone know gpiozero alternative on FreeBSD? Plan to learn programming hardware on Raspberry Pi 5. Using python with gpiozero on Raspberry Pi OS makes the learning curve less tough for a beginner, like me. If possible, I'd still stick to FBSD. Apparently gpiozero is not in FBSD's port tree. Not sure if there is equivalent or alternative available.
Any suggestions are appreciated.
 
bxbzq
I don't know this software, but its github page gives some explanations, so you could try to build it by using "pip" or "virtual environment".
GPIO Zero is installed by default in the Raspberry Pi OS desktop image,available from raspberrypi.org. To install on Raspberry Pi OS Lite or other operating systems, including for PCs using remote GPIO, see the Installing chapter.
Click to expand...
If you’re using another operating system on your Raspberry Pi, you may need to use pip to install GPIO Zero instead. Install pip using get-pip and then type:
sudo pip3 install gpiozero
or for Python 2:
sudo pip install gpiozero
To install GPIO Zero in a virtual environment, see the Development page.
Click to expand...
github.com

GitHub - gpiozero/gpiozero: A simple interface to GPIO devices with Raspberry Pi

A simple interface to GPIO devices with Raspberry Pi - gpiozero/gpiozero
github.com github.com
 
I don't think it will work though. We have different GPIO naming schemes than Linux. They export GPIO Pins as device nodes.

github.com

GitHub - evadot/fbsd_gpio_py: CFFI-Based Python Bindings for FreeBSD libgpio

CFFI-Based Python Bindings for FreeBSD libgpio. Contribute to evadot/fbsd_gpio_py development by creating an account on GitHub.
github.com github.com

github.com

GitHub - ethanlmiller/python-GPIOfbsd: FreeBSD GPIO interface in Python3 using ctypes to interface with libgpio

FreeBSD GPIO interface in Python3 using ctypes to interface with libgpio - ethanlmiller/python-GPIOfbsd
github.com github.com

github.com

GitHub - tspspi/fbsdgpio: GPIO wrapper for FreeBSD (native, Python, ...)

GPIO wrapper for FreeBSD (native, Python, ...). Contribute to tspspi/fbsdgpio development by creating an account on GitHub.
github.com github.com
 
Phishfry said:
The reason I say you may have to make a pin factory is that Pins on FreBSD use a GPIOBus/Pin-Number arrangment while Linux uses BCM Numbers for the pins. So you neeed some shim.
Click to expand...

I loaded bcm283x_pwm and some gpio modules that are not in kernel, but still couldn't see any gpio device in /dev. What am I doing wrong?
Also, dmesg | grep gpio gives me nothong.
% kldstat
Id Refs Address Size Name
1 49 0xffff000000000000 13358c8 kernel
2 1 0xffff000001336000 25478 umodem.ko
3 2 0xffff00000135c000 28630 ucom.ko
4 1 0xffff0000dfc00000 3b000 fusefs.ko
5 1 0xffff0000dfc3b000 36000 if_rtwn_usb.ko
6 5 0xffff0000dfc71000 79000 wlan.ko
7 1 0xffff0000dfcea000 3f000 rtwn.ko
8 1 0xffff0000dfd29000 22000 wlan_wep.ko
9 1 0xffff0000dfd4b000 23000 wlan_tkip.ko
10 1 0xffff0000dfd6e000 26000 wlan_ccmp.ko
11 1 0xffff0000dfd94000 22000 mac_ntpd.ko
12 1 0xffff0000dfdb6000 23000 bcm283x_pwm.ko
13 1 0xffff0000e0c00000 29000 gpiokeys.ko
14 1 0xffff0000dfdd9000 23000 gpioiic.ko
15 1 0xffff0000e0c29000 23000 gpiopps.ko
16 1 0xffff0000e0c4c000 23000 gpioths.ko
17 1 0xffff0000e0c6f000 23000 gpiospi.ko
Click to expand...
 
Here’s a simplified pinout (BCM numbering for key GPIO pins):

| **Physical Pin** | **BCM/GPIO** | **Function** | **FreeBSD GPIO Controller** |
|-------------------|--------------|----------------------------|-----------------------------|
| 1 | 3.3V | 3.3V Power | N/A |
| 3 | BCM2 (GPIO2) | SDA1 (I2C) | `gpio0.2` |
| 5 | BCM3 (GPIO3) | SCL1 (I2C) | `gpio0.3` |
| 7 | BCM4 (GPIO4) | GPIO | `gpio0.4` |
| 8 | BCM14 (TX) | UART TX | `gpio0.14` |
| 10 | BCM15 (RX) | UART RX | `gpio0.15` |
| 11 | BCM17 | GPIO | `gpio0.17` |
| 12 | BCM18 | PCM_CLK | `gpio0.18` |
| 13 | BCM27 | GPIO | `gpio0.27` |
| 15 | BCM22 | GPIO | `gpio0.22` |
| 16 | BCM23 | GPIO | `gpio0.23` |
| 18 | BCM24 | GPIO | `gpio0.24` |
| 19 | BCM10 (MOSI) | SPI0 MOSI | `gpio0.10` |
| 21 | BCM9 (MISO) | SPI0 MISO | `gpio0.9` |
| 22 | BCM25 | GPIO | `gpio0.25` |
| 23 | BCM11 (SCLK) | SPI0 SCLK | `gpio0.11` |
| 24 | BCM8 (CE0) | SPI0 CE0 | `gpio0.8` |
| 26 | BCM7 (CE1) | SPI0 CE1 | `gpio0.7` |
| 29 | BCM5 | GPIO | `gpio0.5` |
| 31 | BCM6 | GPIO | `gpio0.6` |
| 32 | BCM12 | GPIO | `gpio0.12` |
| 33 | BCM13 | GPIO | `gpio0.13` |
| 35 | BCM19 | PCM_FS | `gpio0.19` |
| 36 | BCM16 | GPIO | `gpio0.16` |
| 37 | BCM26 | GPIO | `gpio0.26` |
| 38 | BCM20 | PCM_DIN | `gpio0.20` |
| 40 | BCM21 | PCM_DOUT | `gpio0.21` |
 
bxbzq said:
but still couldn't see any gpio device in /dev. What am I doing wrong?
Also, dmesg | grep gpio gives me nothong.
Click to expand...
Like I mentioned above. We do GPIO differently.

They export pins to userland. aka /dev

We have a GPIO program and API but don't export pins to /dev.

You have to call the pins up as GPIO BUS / GPIO PIN in our program gpioctl or using libgpio API.

man gpioctl

gpio(3)

man.freebsd.org man.freebsd.org

Thread 65190

For Python and libgpio.
github.com

GitHub - ethanlmiller/python-GPIOfbsd: FreeBSD GPIO interface in Python3 using ctypes to interface with libgpio

FreeBSD GPIO interface in Python3 using ctypes to interface with libgpio - ethanlmiller/python-GPIOfbsd
github.com github.com
 
One of the problems I have being a novice programmer is I need a kickstart. Show me what to do.

It looks like we have two Python modules that do the sampe thing. Even named similarly. GPIOfbsd and fbsdgpio

The fbsdgpio github has the much valued example. A Hello World if you will.

github.com

fbsdgpio/samples/py/001_simple.py at master · tspspi/fbsdgpio

GPIO wrapper for FreeBSD (native, Python, ...). Contribute to tspspi/fbsdgpio development by creating an account on GitHub.
github.com github.com
 
I read through the two implementations on github, and gpioctl manpage, and they all mention the presence of /dev/gpioc0. I suppose I need /dev/gpioc0 to be there, otherwise how am I going to program it?
 
Here is a short link to an A.I. answer from grok/i You asked a question about /dev/gpioc0 for FreeBSD use. For those that DO NOT LIKE/ENCOURAGE AI answers as hints, that a man can use to google search and research for better answers by examining and reading the FreeBSD handbooks and forum posts. THEN PLEASE DO NOT follow this link I Grok AI answer. Use at your own discretion. If you find better detailed gpio pin ctrl information, please post your data below. Fred , that I did read and would use to find information to expand my own understanding about GPIO pins and control settings for FreeBSD programs and kernel use. Realize FreeBSD kernel and Linux Kernel are different, and use different ways to set and clear GPIO pins. Pin Numbering is different too. So do beware. Thank you for the previous posted GPIO pin information.
 
I'm convinced that FBSD 14.2 doesn't support GPIO on Pi 5. I'll give a try on 15.0-CURRENT. If no surprise, I'll move on to use Pi OS.
 
You must log in or register to reply here.
Back
Top