open-field unofficial · for OP-1 Field
Put open-field on your own OP-1 Field. This page builds the new firmware file from the one already on your unit, in this browser: nothing of Teenage Engineering's is downloaded, and no firmware is uploaded anywhere.
Before you start
- This is unofficial, and you do it at your own risk. It is not made, endorsed or supported by Teenage Engineering, and it is not affiliated with them. Changing a device's firmware is risky: a unit can end up unable to start for good ("bricked"), and installing this will void the warranty of your device. Whether to do it is your choice alone.
- You need a Windows computer with Chrome or Edge, a USB cable that carries data, a charged unit on the original OS 1.7.3 with bootloader 1000.1.1 (step 1 checks both, and step 5 checks your firmware file), and half an hour. Mac and Linux are not supported yet.
- Keep your own firmware file. Step 3 copies it off your unit into a folder on this computer. Put a copy somewhere else as well (a USB stick, another computer): it is your way back.
- In the bootloader's menus, press only the keys this page names. In its main menu,
3opens the developer menu. In the developer menu, press only2and4: its key1is a factory reset, which erases your recordings and sounds at once and asks nothing, and its key3resets a calibration.
Still on OS 1.7.0? The page for it is kept here, as it was. Only for a unit that was never updated to 1.7.3.
Loading the builder's files…
1Check your unit
- Switch the unit off. Hold COM and switch it on: the bootloader's menu shows.
- Plug in the USB cable.
- Press Find my OP-1 Field and allow MIDI when the browser asks.
If the bootloader's menu does not show 3. dev menu yet, switch it on (once for a unit). Then leave
the menu and come back, or switch off and on holding COM: 3. dev menu shows.
2Open the unit's drive
On the unit, in the bootloader's menu: press 3 (the developer menu opens), then
2 (its drive mode). The unit now shows on the computer as a drive named OP-1. Never press
1 in the developer menu.
3Choose the folder
This page and the helper share one folder on this computer: open-field in your user folder
(C:\Users\ and your name). Press Choose the folder. In the dialog, open your user folder; if
there is no open-field in it yet, make one (the dialog's New folder, named
open-field). Choose it, and let the browser view and edit its files. The page keeps it for the rest
of the install, and offers it again next time.
4Run the helper
A web page cannot reach the unit's files on Windows, so a small helper does that part. Open PowerShell (press
the Windows key, type PowerShell, press Enter), paste this line and press Enter:
It checks that the folder you chose in step 3 is its own, finds the unit, copies your own firmware
file off into that folder, takes the unit's log files off into the same folder, lists the unit's disk, and waits for this page.
Leave its window open. What it changes on the unit, and nothing else: it takes the files in logs
off, and the pad files earlier installs left (open-field-pad.bin and the like), and later writes
os.ldr at the top of the drive, a pad file if one is needed, and your pack files. Read the helper
before you run it, if you like.
Pack files. base.pack, the shared pack every feature needs, comes with this
page: step 5 puts it into the folder packs inside open-field, and the helper copies it
onto the unit with the new firmware file. If packs holds a base.pack already, this
page's takes its place; one with other bytes is first kept in the folder replaced. Other packs can
be ticked from the listing in step 5, and the page puts them into packs the same way. Pack files you
have from elsewhere can go into packs too before step 5's button, or onto the unit later in its disk
mode.
A pack is a program that can read and write the files on your unit: take packs only from people you trust. Holding the help key while you switch the unit on starts it with no packs.
5Build, and plan the write
This starts by itself once the helper has listed the unit's disk: the page checks your file, builds the new one and works out the write.
The firmware file on your unit is not the original OS 1.7.3 file, so nothing can be built from
it. If you kept your own original file from before, put it into the folder as os-1.7.3-yours.ldr
(the page finds it there by itself), or choose it:
What to write:
Packs Tick the packs to put on the unit with the rest. The page downloads each one from its author's repository, at the version the listing names, and refuses a file that is not that one.
This writes the new file, base.pack, the packs you ticked and the plan into the folder.
The helper then puts them on the unit and checks every copy.
6The helper puts the files on the unit
Waiting for step 5.
7Write
- On the unit, press
2to close the drive, and switch the unit off. Leave it off until the write: a start in between writes to its disk, and the placement no longer holds (then go back to step 2 and run the helper's line again, step 4). - Hold COM and switch on. Press
3: the developer menu opens. Wait five seconds. Press4, the entrywrite os to boot partition. - The screen reads
looking for /os.ldrand then stands still for up to half a minute. Do not touch the unit and do not switch it off while it is still. - When
firmware written ok!shows, switch the unit off. That line by itself proves nothing: the bootloader prints it whatever happened. - Wait five seconds, and switch the unit on with no key held.
If small text shows instead, naming a source file and a line (rsi.c and a number), the
write stopped before it touched the firmware your unit runs: switch off, then on with no key, and the unit starts
as before. The unit's spare copy of its firmware is gone after such a stop, which is one more reason to keep your
own file. Run the install again from step 1.
8Read the start screen
The proof is the start screen. With the new firmware file and this page's base.pack it reads
1.7.3 - open-field 0.3: the number is the release of base.pack. If a pack
file cannot run, the words end in (1 left out) and the others run. Holding the help key while
you switch on starts the unit as the original firmware for one start, with no packs, and the start screen reads
1.7.3 stock (help key).
After the way back (step 5's second choice), the start screen shows the original firmware's version line with nothing added.
The owner's guide, docs/guide.md in the repository, has the rest: adding and taking
away a pack, the way back, and what to do when something is not as described.
log
The developer menu step reuses code of Ferret and open-xy (MIT).