Raspberry Pi Compute Module 4 Released!
-
Built on the same 64-bit quad-core BCM2711 application processor as Raspberry Pi 4, Compute Module 4 delivers a step-change in performance over its predecessors: faster CPU cores, better multimedia, more interfacing capabilities, and, for the first time, a choice of RAM densities and a wireless connectivity option.
You can find detailed specs here,
- 1.5GHz quad-core 64-bit ARM Cortex-A72 CPU
- VideoCore VI graphics, supporting OpenGL ES 3.x
- 4Kp60 hardware decode of H.265 (HEVC) video
- 1080p60 hardware decode, and 1080p30 hardware encode of H.264 (AVC) video
- Dual HDMI interfaces, at resolutions up to 4K
- Single-lane PCI Express 2.0 interface
- Dual MIPI DSI display, and dual MIPI CSI-2 camera interfaces
- 1GB, 2GB, 4GB or 8GB LPDDR4-3200 SDRAM
- Optional 8GB, 16GB or 32GB eMMC Flash storage
- Optional 2.4GHz and 5GHz IEEE 802.11b/g/n/ac wireless LAN and Bluetooth 5.0
- Gigabit Ethernet PHY with IEEE 1588 support
- 28 GPIO pins, with up to 6 × UART, 6 × I2C and 5 × SPI
Compute Module 4 IO Board
The IO board provides:
- Two full-size HDMI ports
- Gigabit Ethernet jack
- Two USB 2.0 ports
- MicroSD card socket (only for use with Lite, no-eMMC Compute Module 4 variants)
- PCI Express Gen 2 x1 socket
- HAT footprint with 40-pin GPIO connector and PoE header
- 12V input via barrel jack (supports up to 26V if PCIe unused)
- Camera and display FPC connectors
- Real-time clock with battery backup
More details:
https://www.raspberrypi.org/products/compute-module-4/?variant=raspberry-pi-cm4001000, https://www.raspberrypi.org/blog/raspberry-pi-compute-module-4/ -
@salmanfaris at last they update their design. T
What you think on the updated connector. I felt like its more fragile and high chance for corottion issue due to humidity for long term use. -
@Suhailjr But I think since it's not a plug and plug play system and it will laying on the PCB for the long term, it might be fine. for me, it's similar to the Intel Edison and the PICO-IMX7 System-on-Module
Recent Posts
-
@rafitc99 said in NMCLI AP Mode config error | Connection activation failed: No suitable device found for this connection | Raspberry Pi 3 Model B Rev 1.2:
host="MyRPiAPMode"
sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host
sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared
sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk
sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword"
sudo nmcli radio wifi on
sudo nmcli con up $hostHi @rafitc99, Are you able to set up the AP when trying the commands individually?
-
I was trying to configure AP mode in Raspberrypi by using Network Manager. I'm using the below script. but it is throwing some errors.
Bash Script to set AP Mode
host="MyRPiAPMode" sudo nmcli con add type wifi ifname wlan0 con-name $host autoconnect yes ssid $host sudo nmcli con modify $host 802-11-wireless.mode ap 802-11-wireless.band bg ipv4.method shared sudo nmcli con modify $host wifi-sec.key-mgmt wpa-psk sudo nmcli con modify $host wifi-sec.psk "SomeRandomPassword" sudo nmcli radio wifi on sudo nmcli con up $hostError ----
Connection 'MyRPiAPMode' (60965f2a-f510-48ef-afaf-0864242d0c06) successfully added. Error: Connection activation failed: No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name)).nmcli con (After script execution)
NAME UUID TYPE DEVICE Wired connection 1 9589ff1a-9923-3de3-a8a4-90b319661878 ethernet eth0 MyRPiAPMode 60965f2a-f510-48ef-afaf-0864242d0c06 wifi --nmcli dev
DEVICE TYPE STATE CONNECTION eth0 ethernet connected Wired connection 1 wlan0 wifi unavailable -- lo loopback unmanaged --I tried to make it availble via sudo nmcli radio wifi on
But not working.this is the log
-- Journal begins at Sat 2021-08-07 09:28:21 IST. -- Aug 10 15:06:19 NWPI-b5b072 NetworkManager[16140]: <info> [1660124179.9816] audit: op="connection-update" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" args="802-11-wireless-security.psk" pid=25120 uid=0 result="success" Aug 10 15:06:20 NWPI-b5b072 NetworkManager[16140]: <info> [1660124180.0902] audit: op="radio-control" arg="wireless-enabled" pid=25125 uid=0 result="success" Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4241] agent-manager: agent[641f99ab55d9691c,:1.692/nmcli-connect/0]: agent registered Aug 10 15:06:21 NWPI-b5b072 NetworkManager[16140]: <info> [1660124181.4281] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0573] agent-manager: agent[70ee130ba0f26cd7,:1.696/nmcli-connect/1000]: agent registered Aug 10 15:06:52 NWPI-b5b072 NetworkManager[16140]: <info> [1660124212.0614] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0370] agent-manager: agent[cc77ef461499c164,:1.700/nmcli-connect/0]: agent registered Aug 10 15:07:23 NWPI-b5b072 NetworkManager[16140]: <info> [1660124243.0414] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8406] agent-manager: agent[79b01af218789b42,:1.702/nmcli-connect/0]: agent registered Aug 10 15:07:41 NWPI-b5b072 NetworkManager[16140]: <info> [1660124261.8446] audit: op="connection-activate" uuid="60965f2a-f510-48ef-afaf-0864242d0c06" name="MyRPiAPMode" result="fail" reason="No suitable device found for this connection (device eth0 not available because profile is not compatible with device (mismatching interface name))." -
Raspberry Pi Zero 2 W uses the same Broadcom BCM2710A1 SoC die as the launch version of Raspberry Pi 3, with Arm cores slightly down-clocked to 1GHz, bundled into a single space-saving package alongside 512MB of LPDDR2 SDRAM.
Here are the highlights:
Broadcom BCM2710A1, quad-core 64-bit SoC (Arm Cortex-A53 @ 1GHz) 512MB LPDDR2 SDRAM 2.4GHz IEEE 802.11b/g/n wireless LAN, * Bluetooth 4.2, BLE 1 × USB 2.0 interface with OTG HAT-compatible 40 pin I/O header footprint MicroSD card slot Mini HDMI port Composite video and reset pin solder points CSI-2 camera connector H.264, MPEG-4 decode (1080p30); H.264 encode (1080p30) OpenGL ES 1.1, 2.0 graphicssrc: https://www.raspberrypi.com/news/new-raspberry-pi-zero-2-w-2/
-
@vishnumaiea :grin: :hand_with_index_and_middle_fingers_crossed:
-
@salmanfaris Yeah, just like features and price, long term support is also crucial in determining the efficacy of a microcontroller. What RPi has done with the new introduction of the MCU is close to perfection. Like you said, they had everything ready before the release and that how it should be. No other manufacturer has ever done this before. RPi understands their users and what they seek, as always. With that, they have been able to pull something off that no other manufacturer could.
RP2040 is not just going to be used in hobby spectrum, but also high volume commercial applications. And that's why I said before it is setting off a REVOLUTION. It's just a matter of time RP2040 supersedes ATmega328 in popularity. Microchip has to worry again! 🤭