Supporting the Raspberry Pi 5 #413
Replies: 22 comments 63 replies
-
|
There are more commits for the Raspberry Pi 5 support on the branch rpi5. |
Beta Was this translation helpful? Give feedback.
-
|
One thing 'solved': https://www.raspberrypi.com/documentation/computers/raspberry-pi-5.html#uart-connector |
Beta Was this translation helpful? Give feedback.
-
|
...also tried with the newest release of compilers from here: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for appreciating Circle and for being interested in the Raspberry Pi 5 support. There have been some recent modifications to the rpi5 branch, which I pushed yesterday. So please be sure to use the latest sources. I don't know, which firmware you have in your EEPROM. There was an important firmware change recently. Please ensure, that you have the option Your Config.mk is OK. Please use the GCC-12.2.Rel1-based toolchain. That's the currently recommended one. The three files, you have listed, should be sufficient for the RPi 5 on the SD card. I did not test network boot. I cannot say, if it is working with Circle. On the RPi 5 the serial console is by default the dedicated UART connector ("ttyS11"). If you want to use the UART at GPIO pins 14/15 ("ttyS1") you have to add the following option to Config.mk: The HDMI screen support in the RPi 5 firmware is not like the support for the earlier models. Many configuration options are missing. Raspberry Pi OS is generating the display output in the Linux kernel now, but Circle still relies on the firmware. Unfortunately some displays do not work any more with it. I don't think, the firmware honors your On the RPi 4 and 5 you need the following option in Config.mk, if you want to run a sample program without an attached HDMI screen: Otherwise the 'CScreenDevice' instance will not initialize (returns FALSE) and the sample will not run. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks alot for the comprehensive feedback and hints! Much appreciated! I'll keep you informed about my progress! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, My screen seems to be not supported on that level... :-( All other PIs are happy, though? Seems Pi5 is a diva?! thanks again and happy hacking, pottendo PS: btw, I'm booting over the network - easier workflow for me! |
Beta Was this translation helpful? Give feedback.
-
|
You are welcome and thanks for the feedback. It's good, that it is working now
so far.
I guess, each HDMI display, which needed special settings in config.txt or
cmdline.txt on earlier RPi models can have problems on the RPi 5 with Circle.
But writing a kernel mode display driver to solve this would be a huge task.
Unfortunately Ethernet is not supported yet. The NIC is in the RP1 southbridge
now and needs a totally new driver. I had not the time to port it yet.
USB should work. If it does not, please give it a try with SD card boot.
I also had problems with USB boot here. Perhaps the device is not reset
sufficiently to work at the moment.
|
Beta Was this translation helpful? Give feedback.
-
|
ok, will try - though I filed an issue already... sorry to be too quick. |
Beta Was this translation helpful? Give feedback.
-
|
no, confirmed with SDCard boot: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your RPI(5) support. I use USPi under FreeRTOS/LwIP platform, updated since long time with your Circle updates (RP3B+, RPI4 and 5). I have also an USB problem on the RPI5 (devices detection problem during boot) who seems not exits when HDMI is not connected. Very strange, for example if RF keyboard works, I need to remove HDMI for get FTDI cable detected. |
Beta Was this translation helpful? Give feedback.
-
|
You are welcome. Yes, there seems to be still a strange problem with the new
USB support for the RPi 5 in Circle.
Honestly I did most of the USB testing without a HDMI display connected,
because my display, which I'm normally using on the RPis does not work with
the RPi 5. So your problem report is new to me. I have to test this with the
display of my development PC or buy a new HDMI display.
I will have a look on the u-Boot sources. Thanks for info.
|
Beta Was this translation helpful? Give feedback.
-
|
I think, I was a little quick with condemning the new Circle USB driver for the Raspberry Pi 5. I did a test with sample/39-umsdplugging and many USB devices now with a HDMI display attached and everything was working well. @aniplay62 Did the problems, you described, happen with an original Circle sample with the latest source from the rpi5 branch? You wrote, you have ported the USB support to USPi, which is different. |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately currently I do not have enough feedback to judge about the quality of the new Circle USB driver for the Raspberry Pi 5. More (also positive) feedback from other users would help. To make it simple, I attached a binary of the sample/39-umsdplugging with all necessary files to be installed on a SD card or USB flash drive (if USB boot is enabled). This requires a HDMI display connected, which works with the RPi 5. After boot please attach USB flash drives (or other USB devices) you have and see, if they are detected. Thank you in advance! |
Beta Was this translation helpful? Give feedback.
-
|
Your lastest change, delay after USB device reset, seems fix the problem. I tried with cold/warn (watchdog) reset. Tried with USPi ;-) |
Beta Was this translation helpful? Give feedback.
-
|
OK. But in the end this doesn't tell, if the USB support for RPi 5 in native Circle is working well or not. I didn't fully realize in the first read, that you are using a port of the xHCI driver from Circle in your own project. This is out of scope for this discussion board. |
Beta Was this translation helpful? Give feedback.
-
|
This is my macb driver from u-boot sources, there are some changes for the RP1 like PHY reset via GPIO and leds settings. I reinit all after unplug/plug the cable. Else I think, it's changes for LwIP. |
Beta Was this translation helpful? Give feedback.
-
|
@aniplay62 I think, that's what open source is all about. Thanks again. |
Beta Was this translation helpful? Give feedback.
-
|
@pottendo I'll need a few days to sort this problem out and to complete this driver. Yes, such a HDMI display driver would be great, but is probably an immense task. |
Beta Was this translation helpful? Give feedback.
-
|
@pottendo The driver for the Ethernet NIC of the Raspberry Pi 5 is on the rpi5 branch now. Most of the network samples should work, very few and the docs still need an update (e.g. 06-ethernet, 38-bootloader). @aniplay62 I used a coherent memory region to place the RX/TX rings and DMA buffers, because I had problems with the way the U-Boot driver was managing the data cache. I did not get it reliable under heavy load. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the positive feedback! I will try to support WLAN with the help of @aniplay62. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I have a wifi that works, if my base of work is Zerowi, I use also the Richard Miller's emmc file. I just changed the init routine, I don't know anything, but it works (it's the same chip as the RPI4). int emmcinit(void) |
Beta Was this translation helpful? Give feedback.
-
|
No., but if FIQ is enabled with some method (<=> RPI4), where to use it? |
Beta Was this translation helpful? Give feedback.
-
|
I understand your problem. But design decisions have to be made, and perhaps they had other applications in mind than you. For example as a desktop PC replacement the RPi 5 is much more suitable than the RPi 4, because it has an immense CPU power. This is also good for synthesizers, which are often programmed using Circle. My goal is to support the RPi 5 as good as I can for the bare-metal applications, which are possible with it. On the RPi 4 a specific ARM stub was used to have the chance to enter EL3 for FIQ setup. But on the RPi 5 the ARM stub is actually the Trusted Firmware, which is difficult to replace. There is a small chance, that the Trusted Firmware allows setting up the FIQ on the GIC, but I searched for related information and haven't found it so far. It would be good for example to have the FIQ for the dedicated UART, which is connected to the UART socket. This UART is not in the RP1. |
Beta Was this translation helpful? Give feedback.
-
|
I try a also dedicated UART but it's a Zilog Z8523L (a Z85230 in3V3) used for synchronous frames on lot of GPIO pins ;-), GIC is a V2 but something is different with the RPI4, changes GICD_ITARGETSR produce no effects (re-reading is good, but it's always routed to core 0). |
Beta Was this translation helpful? Give feedback.
-
|
Yes, some kind of the good old Z8530 SCC, I know it. ;) According to my notes GICD_IGROUPR0 can only be accessed in secure mode, and GICD_CTLR + GICC_CTLR have a different layout in secure mode, which is needed to enable the FIQ. Secure mode is managed by the ARM Trusted Firmware. I guess, for the Raspberry Pi 5 a modified version is used, which is not available in source code for the public. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, like me. The first time inside this machine, a |
Beta Was this translation helpful? Give feedback.
-
|
The Raspberry Pi 5 support has been merged to the develop branch to be part of the next release. The branch rpi5 has been deleted. |
Beta Was this translation helpful? Give feedback.
-
|
Circle 46 with initial Raspberry Pi 5 support has been released. |
Beta Was this translation helpful? Give feedback.
-
|
There is initial I2S audio support for the Raspberry Pi 5 on the develop branch. It's currently interrupt driven. Some applications could have problems with the interrupt load, but MiniSynth Pi works and its repo has been updated. I'm still working on the DMA support. Also the currently used I2S clock is not very precise, because the Audio PLL is not supported yet. |
Beta Was this translation helpful? Give feedback.
-
|
hi, |
Beta Was this translation helpful? Give feedback.
-
|
That would already work with the interrupt-driven support, but the RPi 5 does
not have a headphone jack for PWM output. That's why PWM sound output is not a
priority. The new driver is for I2S sound, which requires an external
interface. They are not expensive, but provide a better sound quality.
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I'm trying circle on RPI5 using raspberry pi probe (UART connector), but I cannot see any UART logs from /dev/ttyACM0. Do I need to add additional settings? |
Beta Was this translation helpful? Give feedback.
-
|
To see the logger output from the Circle sample programs via the UART connector of the Raspberry Pi 5, you have to add the option |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the response.
I tried that, but it didn't work... Before: After: |
Beta Was this translation helpful? Give feedback.
-
|
Can you please extract the contents of the attached archive to an empty SD card, connect your debugprobe (via the U socket) to the UART connector, run a terminal program and start the RPi 5 with this SD card. I tested it here using a debugprobe and it works. The RPi 5 blinks 5 times and then generates some log output from Circle sample/04-timer. This is the Config.mk, that I used: |
Beta Was this translation helpful? Give feedback.
-
|
04-timer-rpi5.zip worked fine. Thanks a lot! I'll check the differences... |
Beta Was this translation helpful? Give feedback.
-
|
The I2S DMA support for the Raspberry Pi 5 is on the develop branch. Unfortunately there is still an issue with it. With greater chunk sizes the audio quality is becoming bad for unknown reason. I did many tests, but unfortunately didn't found the reason so far. As a workaround the chunk size is currently limited to a maximum of 128. Smaller chunk sizes may give an even better quality. You can define |
Beta Was this translation helpful? Give feedback.
-
|
The I2S driver is now using the pll_audio as the clock source and the issue, mentioned above, is fixed. With this clock source the timing is much more accurate. The update is on the develop branch. |
Beta Was this translation helpful? Give feedback.
-
|
PWM sound is implemented on the Raspberry Pi 5 now using the RP1 DMA controller. It's on the develop branch. You need an external adapter like the one, which is described here. The left channel has to be connected to GPIO12 (SoC numbers), the right channel to GPIO13. Alternatively the left channel can be moved to GPIO18 by defining |
Beta Was this translation helpful? Give feedback.
-
|
Oh, and for what it's worth, I've an initial test build of MiniDexed for the Pi 5 now too: probonopd/MiniDexed#638 Massive thanks @rsta2 - circle is amazing :) Kevin |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for testing this. I'm glad to see MiniDexed working on the RPi 5! |
Beta Was this translation helpful? Give feedback.
-
|
hi, I'm still waiting to get a i2s audio interface for my PIs - will then also try to get it working on Pi5; will let you know. bye, pottendo
|
Beta Was this translation helpful? Give feedback.
-
|
@pottendo If the problem with MiniDexed remains, you should ask a question in the MiniDexed discussion forum. |
Beta Was this translation helpful? Give feedback.
-
|
No, there is no problem -I think. |
Beta Was this translation helpful? Give feedback.
-
|
The HDMI sound support does work on the Raspberry Pi 5 now. The source code is currently on the develop branch. |
Beta Was this translation helpful? Give feedback.
-
|
Some functions of the new Raspberry Pi 5 with 2 GB RAM (with BCM2712D0 SoC) currently do not work with Circle. AFAIK this affects the WLAN and |
Beta Was this translation helpful? Give feedback.
-
|
The new Raspberry Pi 5 with 2 GB (with BCM2712D0 SoC) is now supported on the develop branch in the same level like the previous Raspberry Pi 5 versions. Please note that the firmware must be updated and a new device tree overlay file must be placed in the overlays/ directory on the SD card. See the file boot/README on the develop branch for more info! |
Beta Was this translation helpful? Give feedback.
-
|
@rsta2 i was looking into buying the zynthian v5.1 to use for my own circle based projects since it has the stuff on board that i need, but it seems to use the pi5. They are not selling the v5 for pi4 anymore it seems. If i understand correctly the current version of circle does not support the mipi dsi based screens (like the original rpi touchscreen) because of the way the display is handled on the rpi 5 hardware. Is that right, and in that case do you plan to add support for this in the future? Or is this like a very difficult task that may some day be coming, but not soon? Thanks for the hard work and continuing development on Circle! |
Beta Was this translation helpful? Give feedback.
-
|
That's right and I'm currently not planning to implement a kernel-mode-like display driver for Circle, which would be necessary. I already tried it and aborted this. |
Beta Was this translation helpful? Give feedback.
-
|
i understand, so i guess if you need a display better stick with the pi4! |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I tried the USB ethernet CDC (a Waveshare adapter with a RTL8153) first on the CM4, it works fine. But on the RPI5, I have some problems, the ping works and the DHCP sequence works too but, as for the rest with Wireshark I see a lot of [TCP retransmission] and no connections. With my limited USB knowledge, on the RPI5 I see wMaxPacketSize at 1024 while on the CM4 I have 512 and yet it works, so I don't understand. I increased the size of the ping with -s and priori beyond 512 bytes there are ethernet checksum errors. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there are problems with the RTL815[23], connected to some xHCI
controllers. Please use the on-board Ethernet NIC of the RPi 4/5.
|
Beta Was this translation helpful? Give feedback.
-
|
These lines added to SendFrame() seems fix the problem. DMA_BUFFER (u8, BufferOut, nLength); |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will try it soon. |
Beta Was this translation helpful? Give feedback.
-
|
I tried a RTL8152 adapter on a RPi 4B. Unfortunately I got a "Cannot set device address (4)" error (USB transaction error), so the device is not usable. I do not have a RTL8153 adapter. Earlier I tried the RTL8152 adapter with a RPi 5, and got transfer timeout errors there. This is not a surprise, because the xHCI controller does not support the complete-on-NAK option, which is supported by the DW HCI USB driver. That's why a read request is not completed immediately, when there is no data available from the NIC and the driver runs in a timeout after a second. This is caused by the network device model of Circle, which polls the NIC receiver with synchronous transfers. Because this works with all on-board NICs and also with RTL815[23] adapters, connected to RPi models, which do not have an on-board NIC, it is not a priority to solve this. Circle supports only one active network interface, and it makes not much sense to use an external adapter, if there is an on-board NIC already like on all RPis with xHCI controller. BTW. Circle already provides a DMA buffer in |
Beta Was this translation helpful? Give feedback.
-
|
I can't try on my single RPI4B, but all transfers works fine on the CM4 and the RPI5. I have removed the 1S delay and increased speed by using FreeRTOS events (m_bTransferCompleted is an event so there are switch to the task who use SendFrame or ReceiveFrame), before I used MsDelay(1) for timeout, bad idea for ethernet frames... boolean XHCIEndpointTransfer (TXHCIEndpoint *pThis, TUSBRequest *pURB, unsigned nTimeoutMs)
{
unsigned nTimeout = 1000;
assert (pThis != 0);
assert (pURB != 0);
assert (nTimeoutMs == USB_TIMEOUT_NONE); // TODO
USBRequestSetCompletionRoutine (pURB, XHCIEndpointCompletionRoutine, 0, pThis);
#ifndef USE_FREERTOS_EVENT
assert (pThis->m_bTransferCompleted);
pThis->m_bTransferCompleted = FALSE;
#else
xEventGroupClearBits(pThis->m_bTransferCompleted, 1);
#endif
if (!XHCIEndpointTransferAsync (pThis, pURB, nTimeoutMs))
{
return FALSE;
}
#ifndef USE_FREERTOS_EVENT
while (!pThis->m_bTransferCompleted)
{
MsDelay (1);
if (--nTimeout == 0)
{
LogWrite (From, LOG_DEBUG, "Transfer timed out");
#ifdef XHCI_DEBUG
XHCIUSBDeviceDumpStatus (pThis->m_pDevice);
#endif
uspi_EnterCritical ();
pThis->m_pURB[0] = pThis->m_pURB[1];
pThis->m_pURB[1] = 0;
uspi_LeaveCritical ();
pThis->m_bTransferCompleted = TRUE;
return FALSE;
}
}
#else
if (xEventGroupWaitBits(pThis->m_bTransferCompleted, 1, pdTRUE, pdFALSE, (uint32_t)kc_ticks2sec * nTimeout / 1000) == 0)
{
LogWrite (From, LOG_DEBUG, "Transfer timed out");
#ifdef XHCI_DEBUG
XHCIUSBDeviceDumpStatus (pThis->m_pDevice);
#endif
uspi_EnterCritical ();
pThis->m_pURB[0] = pThis->m_pURB[1];
pThis->m_pURB[1] = 0;
uspi_LeaveCritical ();
return FALSE;
}
#endif /* USE_FREERTOS_EVENT */
DataMemBarrier ();
return USBRequestGetStatus (pURB) ? TRUE : FALSE;
}
static void XHCIEndpointCompletionRoutine (TUSBRequest *pURB, void *pParam, void *pContext)
{
TXHCIEndpoint *pThis = (TXHCIEndpoint *) pContext;
assert (pThis != 0);
#ifndef USE_FREERTOS_EVENT
assert (!pThis->m_bTransferCompleted);
pThis->m_bTransferCompleted = TRUE;
#else
extern volatile uint32_t ulInterruptFlag;
if (ulInterruptFlag)
{
uint32_t xNeedSwitch = pdFALSE;
xEventGroupSetBitsFromISR(pThis->m_bTransferCompleted, 1, &xNeedSwitch);
if(xNeedSwitch)
vTaskSwitchContext();
}
else
{
xEventGroupSetBits(pThis->m_bTransferCompleted, 1);
}
#endif /* USE_FREERTOS_EVENT */
}
boolean USBCDCEthernetDeviceReceiveFrame (TUSBCDCEthernetDevice *pThis, void *pBuffer, unsigned *pResultLength)
{
assert (pThis != 0);
assert (pThis->m_pEndpointBulkIn != 0);
assert (pBuffer != 0);
DataMemBarrier ();
#ifndef USE_FREERTOS_EVENT
if (!pThis->m_bTransferCompleted)
#else
if (xEventGroupWaitBits(pThis->m_bTransferCompleted, 1, pdFALSE, pdFALSE, 1) == 0)
#endif
{
return FALSE;
}
if(pResultLength == 0)
{
return TRUE;
}
*pResultLength = pThis->m_ResultLength;
assert (pThis->m_pEndpointBulkIn != 0);
USBRequest (&pThis->m_URB, pThis->m_pEndpointBulkIn, pBuffer, FRAME_BUFFER_SIZE, 0);
// do not retry if request cannot be served immediately
USBRequestSetCompleteOnNAK (&pThis->m_URB);
USBRequestSetCompletionRoutine (&pThis->m_URB, USBCDCEthernetDeviceCompletionRoutine, 0, pThis);
#ifndef USE_FREERTOS_EVENT
assert (pThis->m_bTransferCompleted);
#else
xEventGroupClearBits(pThis->m_bTransferCompleted, 1);
#endif
if (!USBHostControllerSubmitAsyncRequest (USBFunctionGetHost (&pThis->m_USBFunction), &pThis->m_URB, 0))
{
#ifndef USE_FREERTOS_EVENT
pThis->m_bTransferCompleted = TRUE;
#else
xEventGroupSetBits(pThis->m_bTransferCompleted, 1);
#endif
_USBRequest (&pThis->m_URB);
return FALSE;
}
return TRUE;
}This is a record to see the system's response with a VNC access on the rtl8153, at the bottom of the text in uS, green curve is the task switch (mame at left), in red interrupt (long line is USB interrupt, sys_timer_3 used for poll main macb network with 300 uS period), long green line is 1mS tick. 
|
Beta Was this translation helpful? Give feedback.
-
|
Receive task lwIP2b, Send task lwIP0 |
Beta Was this translation helpful? Give feedback.
-
|
Nice, but what does this have to do with Circle and the RPi 5 support? |
Beta Was this translation helpful? Give feedback.
-
|
Nothing because you already have the answers, it was just to say that it worked thanks to you :-) |
Beta Was this translation helpful? Give feedback.
-
|
Most features of other RPi models are supported for the RPi 5 now in Circle. So this can be closed. |
Beta Was this translation helpful? Give feedback.
-
There is some initial Circle support for the new Raspberry Pi 5 on the branch rpi5. Please see the file doc/rpi5.txt for more information.
Beta Was this translation helpful? Give feedback.
All reactions