Differences

This shows you the differences between two versions of the page.

--- internal:proddocs:5200 [2024/02/23 09:22] – [Raspberry Pi CM4 Resetting Instructions] tamas
+++ internal:proddocs:5200 [2024/09/11 09:40] (current) – [PCB Programming Instructions] tamas
@@ Line 15: / Line 15: @@
 Once the PCB has been assembled and quality checked, the unit can now be programmed.
-Navigate to http://192.168.16.47/ and sign in with the following credentials:
+Navigate to http://192.168.16.32/ and sign in with the following credentials:
 <adm info>email: production@osukl.com
@@ Line 34: / Line 34: @@
 <note warning>Do not connect a normal P19 board via USB to the programming rig, you will break it.</note>
-For both methods, wait 5 minutes and then the board will be programmed automatically.
+For both methods, wait 5-10 minutes and then the board will be programmed automatically.
 ===== Unit Assembly Instructions =====
@@ Line 80: / Line 80: @@
 ===== Packing Instructions =====
 ===== Raspberry Pi CM4 Resetting Instructions =====
@@ Line 86: / Line 87: @@
   git clone --depth=1 https://github.com/raspberrypi/usbboot
+  cd usbboot
+  make
+  cd recovery
+  ./update-pieeprom.sh
+Mount the Raspberry Pi CM4 on the test IO board. Connect the IO board to the host Linux computer with USB to USB cable.
+Now use rpiboot on Linux computer to start the CM4 in Mass Storage Mode.
+  cd usbboot
+  sudo ./rpiboot
+Power up the IO board and expecting the following result:
+  RPIBOOT: build-date Feb 22 2024 version 20221215~105525 58548dc3
+  Waiting for BCM2835/6/7/2711/2712...
+  Loading embedded: bootcode4.bin
+  Sending bootcode.bin
+  Successful read 4 bytes
+  Waiting for BCM2835/6/7/2711/2712...
+  Loading embedded: bootcode4.bin
+  Second stage boot server
+  Cannot open file config.txt
+  Cannot open file pieeprom.sig
+  Loading embedded: start4.elf
+  File read: start4.elf
+  Cannot open file fixup4.dat
+  Second stage boot server done
+After a few moments, one or more drives will appear on the host Linux computer. You can display these devices using the following:
+  lsblk
+Which will produce output similar to the following:
+  NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
+  sda           8:16   0 223.6G  0 disk
+  ├─sda1        8:17   0   529M  0 part /media/user/boot
+  ├─sda2        8:18   0    99M  0 part /media/user/rootfs_A
+  ├─sda3        8:19   0    16M  0 part /media/user/rootfs_B
+  └─sda4        8:20   0   223G  0 part /media/user/homefs
+You now need to clear the device that is mounted at /media/user/boot, which is sda1, as follows:
+  sudo rm -R /media/user/boot
+  sync
+Power off the device then one final action is needed to reset that to factory settings:
+  cd usbboot
+  sudo ./rpiboot -d ./recovery
-Mount the Raspberry Pi CM4 on the test IO board. Connect the IO board to the host Linux computer with USB to USB cable
+Reboot the IO board and the device’s bootloader will be replaced with the default:
+  RPIBOOT: build-date Feb 22 2024 version 20221215~105525 58548dc3
+  Loading: ./recovery/bootcode4.bin
+  Waiting for BCM2835/6/7/2711/2712...
+  Loading: ./recovery/bootcode4.bin
+  Sending bootcode.bin
+  Successful read 4 bytes
+  Waiting for BCM2835/6/7/2711/2712...
+  Loading: ./recovery/bootcode4.bin
+  Second stage boot server
+  Loading: ./recovery/config.txt
+  File read: config.txt
+  Loading: ./recovery/pieeprom.bin
+  Loading: ./recovery/pieeprom.bin
+  Loading: ./recovery/pieeprom.sig
+  File read: pieeprom.sig
+  Loading: ./recovery/pieeprom.bin
+  File read: pieeprom.bin
+  Second stage boot server done