time; make -j4 buildworld KERNELCONF=GENERIC-VCHIQ -DNO_CLEAN

time make -j4 buildworld KERNELCONF=GENERIC-VCHIQ -DNO_CLEAN 

 

# script /var/tmp/mw.out
Script started, output file is /var/tmp/mw.out

 https://people.freebsd.org/~rodrigc/doc/handbook/makeworld.html

Can /usr/obj be removed when finished?

This directory contains all the object files that were produced during the compilation phase. Normally, one of the first steps in the make buildworld process is to remove this directory and start afresh. Keeping /usr/obj around when finished makes little sense, and its removal frees up a approximately 2GB of disk space.

Can interrupted builds be resumed?

This depends on how far into the process the problem occurs. In general, make buildworld builds new copies of essential tools and the system libraries. These tools and libraries are then installed, used to rebuild themselves, and are installed again. The rest of the system is then rebuilt with the new system tools.

During the last stage, it is fairly safe to run these commands as they will not undo the work of the previous make buildworld:

# cd /usr/src
# make -DNO_CLEAN all

If this message appears:

--------------------------------------------------------------
Building everything..
--------------------------------------------------------------

in the make buildworld output, it is probably fairly safe to do so.

If that message is not displayed, it is always better to be safe than sorry and to restart the build from scratch.

 

FreeBSD ARM mailing lists

https://lists.freebsd.org/archives/freebsd-arm/2023-January/index.html 

Rebuild the FreeBSD kernel and install the kernel.

make -j4 buildkernel  KERNCONF=GENERIC-VCHIQ 

make  installkernel KERNCONF=GENERIC-VCHIQ

Read and follow 24.6 Rebuilding World from manual

https://people.freebsd.org/~rodrigc/doc/handbook/makeworld.html

shutdown now  // go into single user mode hit '2' or 'S' key during Beastie FreeBSD console boot

You have to hook 3.3V TTL Console serial port Uart0 pins 14 TXD (8), 15 RXD(10), GND (6), 3.3V (1) on the 40 pin connector of the Raspberry Pi 4B.  I used a Black Magic Probe serial port interface 4 wire interface Red 3.3V (1), Purple TXD (8), Green RXD (10), Black GND (6).

Edit  ESP EFI System Partition Fat32  msdos mounted boot file directory config.txt file to

contain the lines:

 

# https://www.vinnie.work/blog/2020-11-06-baremetal-rpi4-setup

# Disable pull downs

gpio=14,15,22-27=np   

# Enable jtag pins (i.e. GPIO22-GPIO27)

enable_jtag_gpio=1

enable_uart=1

# disable other peripherals

dtparam=i2c_arm=off
dtparam=spi=off

https://www.raspberrypi.com/documentation/computers/config_txt.html#enable_uart

enable_uart  

enable_uart=1 (in conjunction with console=serial0 in cmdline.txt) requests that the kernel creates a serial console, accessible using GPIOs 14 and 15 (pins 8 and 10 on the 40-pin header). Editing cmdline.txt to remove the line quiet enables boot messages from the kernel to also appear there. See also uart_2ndstage.

https://www.raspberrypi.com/documentation/computers/config_txt.html#enable_jtag_gpio

enable_jtag_gpio

Setting enable_jtag_gpio=1 selects Alt4 mode for GPIO pins 22-27, and sets up some internal SoC connections, thus enabling the JTAG interface for the ARM CPU. It works on all models of Raspberry Pi.

Pin #	Function
GPIO22	ARM_TRST
GPIO23	ARM_RTCK
GPIO24	ARM_TDO
GPIO25	ARM_TCK
GPIO26	ARM_TDI
GPIO27	ARM_TMS

https://www.raspberrypi.com/documentation/computers/config_txt.html#gpio

gpio  

The gpio directive allows GPIO pins to be set to specific modes and values at boot time in a way that would previously have needed a custom dt-blob.bin file. Each line applies the same settings (or at least makes the same changes) to a set of pins, either a single pin (3), a range of pins (3-4), or a comma-separated list of either (3-4,6,8). The pin set is followed by an = and one or more comma-separated attributes from this list:

• ip - Input

• op - Output

• a0-a5 - Alt0-Alt5

• dh - Driving high (for outputs)

• dl - Driving low (for outputs)

• pu - Pull up

• pd - Pull down

• pn/np - No pull

gpio settings are applied in order, so those appearing later override those appearing earlier.

Commands for enabling soft update, mount all the UFS Unix File System type partitions, turn all swap partitions on.

mount -u /
mount -a -t ufs

swapon -a

adjkerntz -i           //  Adjust the CMOS clock  to UTC not local time.

cp -Rp /etc /etc.old   // Save the old configuration files
mergemaster -p
cd /usr/src
make installworld    //  NO -j4 
mergemaster -iF      

cd /usr/src
make check-old

sysutils/libchk
sysutils/bsdadminscripts

make delete-old
reboot

make delete-old-libs

And this could have been avoided if user have followed source upgrade
delete-old{-libs}, which is well documented in /usr/src/UPDATING and I
----------------------------------------------
make buildworld [9]
make buildkernel KERNCONF=YOUR_KERNEL_HERE [8]
[1]
etcupdate -p [5]
etcupdate -B [4]
make delete-old [6]
instructions by performing mergemaster or etcupdate *before* make
<make sure you have good level 0 dumps>
make installkernel KERNCONF=YOUR_KERNEL_HERE
<reboot in single user> [3]
The order here is very important.
quote it here:
To upgrade in-place from stable to current

<reboot>
Cheers,

	make installworld

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook