Hi!
I wanted to ask if there is an image for the Sophos RED 15 and RED 50 devices?
I have only found instructions for Sophos RED 15W.
At the moment there are two devices next to me that would like to have OpenWrt installed 
Can I also use the 15W version on the 15?
The device has no WLAN.
RED15:
RED50:
Stats from RED15:
NAND boot...
Second program loader running in sram...
************
Tertiary program loader running in sram...
U-Boot 1.0.10-QorIQ-SDK-V1.6+gfe1d4f5 (Apr 22 2015 - 15:58:08)
CPU: P1010E, Version: 2.0, (0x80f90020)
Core: e500, Version: 5.2, (0x80212152)
Clock Configuration:
CPU0:533.333 MHz,
CCB:266.667 MHz,
DDR:333.333 MHz (666.667 MT/s data rate) (Asynchronous), IFC:66.667 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
Board: P1010RDB-PB, CPLD: v1.2, PCB: v1.0, Boot from: unknown
I2C: ready
SPI: ready
DRAM: Detected UDIMM Fixed DDR on board
128 MiB (DDR3, 16-bit, CL=5, ECC off)
Now running in RAM - U-Boot at: 07ef0000
Flash: None
L2: 256 KiB already enabled
NAND: 128 MiB
MMC: FSL_SDHC: 0
PCIe1: Root Complex of mini PCIe Slot, no link, regs @ 0xffe0a000
PCIe1: Bus 00 - 00
In: serial
Out: serial
Err: serial
Net: eTSEC1 [PRIME], eTSEC2
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x300000, size 0x100000
1048576 bytes read: OK
NAND read: device 0 offset 0x400000, size 0x800000
Stats from RED50:
U-Boot 2010.12 (Jun 13 2012 - 18:57:31)
CPU0: P1020E, Version: 1.1, (0x80ec0011)
Core: E500, Version: 5.1, (0x80212051)
Clock Configuration:
CPU0:533.333 MHz, CPU1:533.333 MHz,
CCB:266.667 MHz,
DDR:333.333 MHz (666.667 MT/s data rate) (Asynchronous), LBC:16.667 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: P1020RDB Rev
MB-351Z Ver.T03 2012-06-13
I2C: ready
DRAM: Configuring DDR for 666.667 MT/s data rate
DDR: 512 MiB (DDR3, 32-bit, CL=6, ECC off)
FLASH: 2 MiB
L2: 256 KB enabled
NAND: 256 MiB
EEPROM: NXID v0
eTSEC2 is in sgmii mode.
PCIE2: connected to Slot 1 as Root Complex (base addr ffe09000)
PCIE2: Bus 00 - 00
PCIE1: connected to Slot 2 as Root Complex (base addr ffe0a000)
PCIE1: Bus 01 - 01
In: serial
Out: serial
Err: serial
Net: eTSEC1: No support for PHY id ffffffff; assuming generic
eTSEC3: No support for PHY id ffffffff; assuming generic
Init switch to forwarding mode... Done
eTSEC1, eTSEC2, eTSEC3
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x0, size 0x100000
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
1048576 bytes read: OK
NAND read: device 0 offset 0x100000, size 0x1000000
And after the boot ... look what says hello:
OpenWrt login:
Update RED15:
I have managed to get into uboot.
Apparently there was an update that set the startup time to get into uboot to 0 seconds.
This made it impossible to get into uboot.
The following worked:
procd: - preinit -
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
f
- failsafe -
BusyBox v1.22.1 (2019-09-03 16:52:16 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
ash: can't access tty; job control turned off
_______ __ _______ _______ ______ _____ _______
| _ .-----.-----| |--.-----.-----| _ | _ | _ \ | _ | _ |
| 1___| _ | _ | | _ |__ --|. l |. 1___|. | \ |.| | 1___|
|____ |_____| __|__|__|_____|_____|. _ |. __)_|. | \`-|. |____ |
|: 1 | |__| |: | |: 1 |: 1 / |: |: 1 |
|::.. . | |::.|:. |::.. . |::.. . / |::.|::.. . |
`-------' `--- ---`-------`------' `---`-------'
send the following:
root@(none):/# fw_setenv bootdelay 2
root@(none):/# reboot
press any keys quickly so that we can interrupt the boot process
uboot should now be present, as the line begins with “=>”
Now I was able to start OpenWrt from a USB stick for the first test.
insert USB stick
boot from the USB stick:
run bootargs_owrt; usb start; fatload usb 0:1 0x1000000 kernel.bin; bootm 0x1000000;
BusyBox v1.36.1 (2024-09-23 12:34:46 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 23.05.5, r24106-10cc5fcd00
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
Now I just have to find out how to install OpenWrt properly.
I also connected an Internet connection to the WAN port for testing.
An IP was obtained via DHCP and I was able to surf the Internet on LAN1 without any problems.
The only error I have found so far is the product information on the status page. It says 15w instead of 15.
The tab for WLAN is completely missing, which is good.
Hi!
Thanks for this
I’ve followed the steps from the guide for my RED15, but I’m wondering about two things:
“Now I just have to find out how to install OpenWrt properly.” Any updates on this step?
Is there a way to always boot from USB using a command, or is it something that needs to be done manually each time? Maybe its obvious, but i am new to this
Thanks it advanced!
Hi!
Unfortunately not yet.
The two devices are still lying next to me.
Unfortunately I'm not a Linux expert when it comes to installing OpenWrt on certain storage regions.
I was hoping that someone here in the forum would have an idea.
In the meantime, I've even got my hands on two Sophos XGS 3300s, but even there OpenWrt can only be used to a very limited extent.
An installation on the USB stick would certainly be possible and by adjusting the boot order, booting would not be a big problem, but it would not be a good solution for me.
A modified OpenWrt is already running on the devices, so it should be possible to install OpenWrt somehow.
In the meantime, the CPU is already being desoldered here to find out a little more about the board:
Also looking for an image for a RED 50. Not sure the red 15 image is going to cut it re device trees and running one core instead of two with the p1020. Have looked at the filesystem for any hints on the LCD interface of which there are some as it would be rather nice to have status messages sent to it, even if just bootup/shutdown messages or errors. Five wires is maybe 4 bit parallel and ground?
I tried changing the root password in failsafe mode, but of course it doesn't update the flashed partition, so each reboot the original is restored. I have 'John' working for me on the password hash as I write this, it's a slow job as my wordlist searches failed. As it's already openwrt I just wonder if at the worst we can update some things and use it stock, or even load / unload wanted and unwanted modules. Of note is the /astaro folder from their joining with that firm. Thanks Hoerli for the Uboot tip, it worked great and fw_setenv/fw_printenv is used in many embedded boxes I find on my travels 
I think the display can be made to work again quite easily.
There are a few LCD packages that might work.
With OPNsense (FreeBSD) there is os-lcdproc-sdeclcd ( LCDProc for SDEC LCD devices) as a package.
This enabled me to reactivate the display on a Sophos XG 330.
However, it would be much more important to be able to install a suitable OpenWrt version on the device cleanly.
No matter whether 15 or 50.
Once that is done, the rest is (probably) not so difficult to implement.
Unfortunately, I still haven't fully understood how to partition the flash memory for the installation to work.
Apparently no one has stumbled across this thread in the last 4 months who is familiar with the matter and / or has no interest in the devices. 
Hi Hoerli,
Thanks very much for answering. I've extracted the device tree for the RED 50 originally as a fdt and reconstituted it with dtc, then also via uboot with the 'fdt' command. I'm still working on root access, but I think the filesystem could be remounted read write and carefully altered from safe mode a change done and carefully restart the unit. Unfortunately my low level abilities failed me in mounting a usb drive otherwise I would have dd'd out the mtd, which would be good to have a backup to revert if needed. I hope you find the method for the flash ok. I am looking at building a p1020 image with the source and the device tree, but it is a large job for a first-timer at such things here. LCD yes even in safe mode the LCD menu still works. I have a few mpc85xx machines around I would like to repurpose so this is a job worth doing.
Ok, I wish you luck with your work on this device and I'll try from this end to move things forward some more if I can.
Hello guys,
I'm also holding a RED 50 in my hand, so the topic is not dead. Has anyone found out anything? I will try to dump the whole firmware to a USB drive tomorrow. Maybe this will give us a hint about how the device works