birds like wires

Search

OpenPeak Firmware v30300

Latest Release: 6th November 2012

Download: Version 30300 – (136MB) MD5

  • This software is not supported or endorsed by OpenPeak or O2. Use at your own risk.

Towards the end of April 2012, something rather unprecedented happened over on the Joggler Forums. It appeared that we were being linked to by O2 themselves as the point of contact after they discontinued their support for the device. After some negotiation, the forum was provided with a ‘sunset’ build of the OpenPeak OS for the OpenFrame 1, on which the Joggler is based.

It’s rare that a company bows out from a device so graciously, effectively opening up the platform to enthusiasts to continue developing and supporting. They could have locked the device down, but they chose not to, and they deserve recognition for that.

The final release, version 30291, did come with a few minor hiccups; but most of those were ironed out pretty quickly. However, under the hood a couple of things had changed. Firstly, the standby partition was no longer used. Designed to recover the Joggler in the event of system problem (although it rarely worked in reality), this left a quarter of the flash memory wasted and empty in a separate partition. Secondly, automated updates and installations from USB sticks were disabled. And, for the paranoid, the OpenPeak update system was still live and potentially able to lock the devices down should somebody change their mind.

Updated Release

Because of this, I decided to do a little ‘tidy’ of the OpenPeak firmware image. What I’ve done is to take the final release of the OpenPeak firmware and make a few tweaks, re-versioning it as 30300.

This is what has changed:

  1. Removed the empty backup partition (mmcblk0p3).
  2. Allocated the recovered space to the /media partition (mmcblk0p4).
  3. Disabled firmware updates from OpenPeak.
  4. Enabled SSH and SCP by default.
  5. Added ‘setpasswd’ command for easily changing the default password.
  6. Enabled the ‘update from USB stick’ feature that was removed.

Other than that, everything is the same as the 30291 version.

So, please give it a try if it seems interesting and let me know how it performs for you!

Installation

To install Version 30300 on your Joggler, download the .img.gz and accompanying MD5 checksum file from the links above. Then follow the instructions on the Reflashing Tool pages to make your reflash device.

In Part 2: Add the Script or Firmware Image, follow the instructions for Flashing an Alternative OS.

Once the image has been checked, it will be flashed to your Jogglers’ internal memory. You cannot run the OpenPeak OS from a USB stick. It’s just not written to support that.

It should go without saying that doing this will reset everything on your Joggler to defaults, including the NVRAM and the contents of your /media area.

Make sure you’ve backed up your files!

Technical Notes

You don’t need to read this unless you’re planning on messing with the system yourself!

Layout of the MMC

Reorganisation of the MMC device was achieved by removing /dev/mmcblk0p3 and resizing /dev/mmcblk0p4 to use the freed space. This has the side effect of retaining the original partition numbering, which will hopefully alleviate any troubles with software trying to talk directly to /dev/mmcblk0p4 (which would otherwise have disappeared). Code relating to the ‘standbyfs’ partition has been commented out.

Disk /dev/mmcblk0: 1028 MB, 1028128768 bytes
4 heads, 16 sectors/track, 31376 cylinders, total 2008064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00065065

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1   *          16      125055       62520   ef  EFI (FAT-12/16/32)
/dev/mmcblk0p2          125056      625151      250048   83  Linux
/dev/mmcblk0p4          626688     2007039      690176   83  Linux
Local Updates

The ‘local update’ feature, which allows payloads on USB sticks to be handled on boot, has been re-enabled by the inclusion of an empty /etc/.usb-key file. This file would normally be used as a simple signing system to determine that an update is official; by using a zero-byte file, a matching MD5 for the opupdt.tgz payload is sufficient to commence installation.

However, there were some changes to the mechanism between 26635 and 30291. The 30291 version is more secure, running the opupdt.run script that is extracted from the checksummed payload, rather than one that is simply sat on the USB stick root. If you are targeting both 26635 and 30xxx versions, you need to supply a working script within the payload and a ‘dummy’ script for 26635 in the USB root that executes it.

You will also need to provide two checksum files on the USB stick; one for each OS version. I’m sure you’ll be happy to hear that I’ve made this part a little easier, though. This gensum.sh script and keyfile will do the work for you.

hello, I’m trying to login with putty, what is the pwd for root account?
thanks

johnny left this message 1707 days ago

@johnny Probably should have included that in the description; it’s just ‘joggler’ for both username and password. :)

Andy left this message 1694 days ago

Hi, I am new to Joggler, found your site while i am searching for help on the device.

I have just bought a second hand Joggler, my target would be running Ubuntu on it, but I cannot seems to be able to get the device to boot from the usb, it seems it boots directly to the internal OS..

Am trying the flash tools with the original image, still no good and it still boots to the internal OS.

Wonder would you mind to give me a help?

Thanks.

Theo left this message 1499 days ago

@Theo Your best bet is to go to the O2 Joggler Forums. This is a common problem and most likely results from either not writing the image to your USB stick properly, or that your stick just isn’t suitable for booting a Joggler. Plenty of us folks to point you in the right direction there. :)

Andy left this message 1499 days ago

I have an openframe 2.0 that came with a phone app and a handset. I will like to still be able use that phone feature. How is this possible with this new version? I noticed the phone app is nolonger present and the handset is useless. Any help?

Leonard left this message 863 days ago

@Leonard I’ve not had a OpenFrame 2 with a handset until very recently, so I’m afraid I can’t be of much help to you on this one. The very last revision of OpenPeak’s software didn’t include any ‘specialist’ apps that might have been created for individual companies, which is probably why the phone app isn’t present. Doubtless the companies they were designed for won’t be routing calls from them any more.

However, that doesn’t mean you couldn’t try to use the hardware. I’d give one of BuZz’s Ubuntu systems a go on an external memory stick to see if you can get the phone and OpenFrame chatting again. How exactly you would go about that… not so sure! A quick Google didn’t turn a lot up, but if you could pair the phone and the DECT controller, there’s every possibility you could use it.

Andy left this message 859 days ago

@Andy. Thanks for your quick response. I was able to enable the phone app via ssh. I am now trying to enable the hidden options under settings to pair the handset with the frame. These hidden settings could let you provision with another provider. hopefully a sip provider. Do you have the last 2XXXXX firmware version with ssh? I could check somethings. Thanks

Leonard left this message 858 days ago

Hello,

Would you happen to have any knowledge whatsoever about history, specs etc about the Openpeak Openframebs phone/screen? I have an opportunity to purchase 1 or 3 is unused condition. Wondering if is worth it for playing around with another OS.

Thanks!

Devin left this message 796 days ago