so I've been trying to boot but have yet to be successful. I'm using a cm4 lite and I've tried the desktop and OMV images. I was able to get the default raspberry pi os to boot
Flashing issues beyond "MS Windows used for flashing" is something that has not been reported before.
Are you using the same CM4 that worked for you previously? Do you have a different CM4 to test with?
I assume you have tried different USB flash dongles?
We have a legacy downloads page with older versions of our OS. Would you like to try an older version to see if that works for you? https://www.axzez.com/legacy-downloads
In your original post you said: "I had a set up working where the pi was booting from USB that no longer works". Did it just all of the sudden stop working? Can you elaborate about the circumstances around this in more detail please?
Here is a customer who had an issue similar to what you are reporting, which is not similar to the issue of OP of this thread: https://www.axzez.com/forum/interceptor-carrier-board/c4-module-stuck-in-boot/dl-ceb77670-d4bb-4c97-b024-cb0d13e3a9c9 In this case, we had the guy send in his system, we tested it, and found that it took a really long time to get to BCM-USB-MSD (05) in the boot order, but when we gave it enough time it did eventually get to that point and did load the OS Installer on the USB flash drive. We ended up sending his system back to him with no change. At the time, we wrote this to the customer:"Further testing with different CM4 modules show that your CM4 was unique.  We believe they had a software issue on your CM4 board that we’ve now fixed since we let it cycle through until it successfully used our USB flash drive and installed our OS and updates.  There are no longer any issues with this module and it boots as expected, like all of the other CM4s.  I’ve rebooted it multiple times now, with and without the USB flash drive, and there were absolutely no issues.  My USB keyboard/mouse work perfectly and I see nothing wrong with either board."
Let's see if you just let the system run for 10 minutes if it finally makes it our OS Installer screen. The bootloader should repeat itself until it finds something to boot. If after that time it does not, we'd like for you to at least try a different CM4 module.
HI. I had a set up working where the pi was booting from USB that no longer works, and when I attempt to boot now I tun into much the same issue that's being described in a number of posts.
The USB I'm using has an image that was written following the instructions:
1. Download the img file from our Software Downloads page.
2. Use Raspberry Pi Imager to write it directly to your USB flash drive.
Also "just buy the v2 board with SD Card support" cannot be the answer to this issue.(As I saw posted in another thread). I use this device and board to lab test things.
If I have to get a different I/O board I'll just spend half the price and get the official board. I got this board like right after it came out to support the project, before I was even ready to use it (during the rpi shortage).
Can we get support for a resolution to this? Even some explanation of what may have caused this would be helpful at this time. Thank you.
Nowhere are we saying that you should buy the v2 of our board to resolve any issues. That is not a solution we will ever provide. If you have a link to where we said that this is a solution to a board not working properly, please share it. I expect that it is a misunderstanding, though.
"Can we get support for a resolution to this?" Of course. The only issue we have right now with any customer is the Windows OS being used to write our OS Installer software to a USB Flash Drive. We don't yet know why only some people experience this issue with the Windows Operating System, but every customer that HAS experienced this has resolved it by using a different system (Not Windows) to write our OS Installer to the USB Flash Drive.
From the looks of your screenshot, I expect that this is what you are experiencing and that there is no issue with the board. We are glad to work with you on this to help you resolve your issue like we have done for other customers. We're here to help.
How did you write the OS you downloaded? The process should be:1. Download the img file from our Software Downloads page.2. Use Raspberry Pi Imager to write it directly to your USB flash drive.
If I had to guess, based on your screenshot, I'd say the image was not written to the USB flash drive successfully. I see "USB2[1]" is connected and enabled and I would guess that you are using HUB port 2 for the flash drive and perhaps port 1 for a USB keyboard/mouse. (based on speed) But it didn't like what was written to the flash drive.
If you scan through the forums, you'll see that some people have experienced issues writing the img file to USB flash drives while on Windows OS.If it is not a Windows OS issue, would you mind trying one of the other images we have to see if they work?
whelp I had it working exactly how I wanted. Then I shut it down to clean up the mess of cables, and now it won't boot off the ssd that I installed to.
If you install the OS on the SSD, you’ll still need to keep the USB flash drive plugged in because the bootloader is stored on the flash drive. The CM4 cannot boot directly from an SSD—it can only boot from an SD Card, eMMC, or USB. Since you have a Lite board without onboard eMMC, you’ll need either our new Interceptor v2 board with SD Card support or to continue booting from USB. While the OS and all your work are on the SSD, the USB flash drive is required only for booting. Once booted, the SSD serves as the primary storage and operating location.
I do not use Windows. I use Ubuntu 22.04.5 LTS 64bit. In my experience this is not an issue limited to Windows users.
HI. I had a set up working where the pi was booting from USB that no longer works, and when I attempt to boot now I tun into much the same issue that's being described in a number of posts.
The USB I'm using has an image that was written following the instructions:
1. Download the img file from our Software Downloads page.
2. Use Raspberry Pi Imager to write it directly to your USB flash drive.
Also "just buy the v2 board with SD Card support" cannot be the answer to this issue.(As I saw posted in another thread). I use this device and board to lab test things.
If I have to get a different I/O board I'll just spend half the price and get the official board. I got this board like right after it came out to support the project, before I was even ready to use it (during the rpi shortage).
Can we get support for a resolution to this? Even some explanation of what may have caused this would be helpful at this time. Thank you.
How did you write the OS you downloaded? The process should be: 1. Download the img file from our Software Downloads page. 2. Use Raspberry Pi Imager to write it directly to your USB flash drive.
If I had to guess, based on your screenshot, I'd say the image was not written to the USB flash drive successfully. I see "USB2[1]" is connected and enabled and I would guess that you are using HUB port 2 for the flash drive and perhaps port 1 for a USB keyboard/mouse. (based on speed) But it didn't like what was written to the flash drive.
If you scan through the forums, you'll see that some people have experienced issues writing the img file to USB flash drives while on Windows OS. If it is not a Windows OS issue, would you mind trying one of the other images we have to see if they work?