Version 30301 - 21st August 2018
Use the Reflashing Tool to install.
________________________________________
I decided to do a little 'tidy' of the OpenPeak firmware image. The third partition as provided by the 30291 reflasher is unused; it used to contain an earlier version of the OS for backup purposes, but I've never known it to work properly and it appears to have been ditched. In essence, that means 256MB of the 1GB internal storage is wasted and sat there empty.
What I've done is to take the final release of the OpenPeak firmware and make a few tweaks, re-versioning it as 30300.
UPDATE: A mere six years later, I've revisited the image and made another tweak, producing version 30301.
Following the shutdown of OpenPeak's servers, OpenFrames have been calling out into the wild for updates and config files, receiving no response. With the ownership of openpeak.net now uncertain, open for purchase by anybody, it seemed sensible to redirect these calls in the hope that we might one day be able to push EFI updates to locked-down devices. This represents the only way that OpenFrame 2 devices with locked EFI firmware can be unlocked, without flashing and replacing the soldered EFI chip.
If anybody can shed any light on the response an OpenFrame is expecting when it calls the server, that would be a big help. I really wish we had the old servers to query just one last time!
Because I'd not be able to afford the asking price for openpeak.net, and because binaries can't be modified in size without breaking them, I've opted instead for openbeak.net. There's a pun in there, if you look hard enough.
Other than the software update server configuration, this is what changed from 30291:
- Removed the empty backup partition (mmcblk0p3).
- Allocated the recovered space to the /media partition (mmcblk0p4).
- Enabled SSH and SCP by default.
- Added 'setpasswd' command for easily changing the default password.
- Enabled the 'update from USB stick' feature that was removed.
There are some technical details on the page for the update if you're interested in using the re-enabled local USB update feature, or want to see how the MMC is now laid out.
So, please give it a try if it seems interesting and let me know how it performs for you!