OneROM

[Muncie]

I’ll hold the BIN for the minute as it’s so heavily modified it would be next to useless for anyone else. Once my turbo VY is running successfully on the OneROM I’ll load a stock v1.0 Enhanced calibration test on my other stock VY and release a clean base file.

[jxx]

Very good to hear it worked.
In theory 27C020 and 27C040 should work by changing the rom type byte, but really not needed for vs/vt and now vx/vy.
You've headed down a path i didn't contemplate with the flash based PCM, maybe something to look at is an interposer for the flash chip to a socket for the onerom.
Stealing ideas from the old console mod days soldering a 0.8mm pcb to certain board pinouts instead of running 32 wires.
Memory is rusty here, the AT29C010 used is a TSOP32? not a PLCC32

Slowly working on making this work on the new onerom firmware,
REV K successfull with the build scripts with 0.7.1 repository, false positive, it built but did not function as intended

usb_emu_system_plugin.jpg

A lot of stale incorrect comments in the old source code as well (correct for the fire 28, completely wrong for the fire 32), probably should have cleaned all that up before I released it.... i did say it was possibly a mess.
I'll upload this new source when i've confirmed the new built plugins work.
I have also had it working with upto 250Mhz overclock on the RP2350 (stock is 150Mhz) but the UART baud needs to recalculated if this is done. More hassle than it's worth, but can be done.

Now that piers made flashing easier and allowing you to add a custom plugin with the stock tools, makes my flashtool obsolete, i only built that initially instead of the back and forth using picotool flashing changes and onerom cmdline to stop/start the onerom.
I haven't actually tried the new stock flashing tools: web, cmdline, studio

As I said there's a bit of work to go on the 128K variant, it really was a proof of concept build.

I guess I should clean up my source zips and upload what wil be 3 (currently 2) variants to github.

Rev I - Fire 28 all working and stable
Rev J.02 - the source code I've released here, with fire 32 and data tracing, work in progress.

Rev K - will be for 0.7.0 once i play around and make sure it works when i get some time. There is no plan for this to happen anytime soon, it's a major re-write of the code


Side note, you don't need to pad the the system plugin with FF, it should automatically build the full image on boot, like how the .uf2 files are so small and not the full 2/4MB, it writes what it needs and formats the rest on first boot.
The smallest .uf2 only have the Base firmware, metadata and system plugin, if i recall correctly.
Also you can release it with the rom area clear with FF, just a matter of hooking tunerpro up and writing an image.

[Muncie]

Current plan for install is to use the J4 header as much as possible use flat ribbon cable to connect, and run short leads to U11 as required many pins are on j4 with excellent connections 0.1-0.3 ohms theres a few that have more resistance so will go back to u11 for those as im unsure what else is in the circuit.

This is my first time doing anything this invasive so any tips for a good result im all in.

My board looks a bit hammered its just from probing through the silicone potting that is over entire board have since scrubbed it off with isopropyl alcohol and looks ready to go.

[jxx]

PLCC32, my memory was wrong.
I'd get creative in kicad with something like this (a bit more refined and use a smd dip32 socket, those bypass caps could be moved), maybe even use J4 as well for some extra support but it won't be going anywhere with the 32 solder points.

plcc32_dip32.jpg

No need for WE, PGM
Only need A0-A16, D0-D7, -CE, -OE, GND and VCC

Or socket J4 if everything is there and an interposer like the VS/VT memcal to plug into that.

I'm assuming there is no documented pinout for the J4 connector? I did a quick search but couldn't find anything.


Progress:
REV K to suit current 0.7.1 one rom firmware.

Tunerpro:
Detects
Writes
Verify fails, Read is only seeing all FF

Physical verify in eprom programmer 100% and persists thru power cycle.

It's close. 3 out of 4 ain't bad.
Only working on the Fire 32 128KB version at the moment.
Haven't even looked at the Fire 28 27C256 & 27C512 and i'm considering dropping that in the new code.

[Muncie]

Just to update i got a semi clean read back on my T48 I had a few pins that weren't making good contact initially looking through most the bin got in. Now its looking good after writing through tunerpro so ive moved to fitting.

PCM'S got its ribbon cable in ready to start soldering up to J4 and u11 (PLCC32) back to the ONEROM

[Muncie]

Good News!

Muddled my way through the wiring took 2 goes as i've not soldered much for 20 years up till 1am very excited to get it going got the shakes so finished this morning, and it woke up on bench! passed all tests so i fitted it into a VT Case with the window on back plugged it in and car started like normal.

Persistence is there it starts repetitively coms through OBD work Coms through usb C to Onerom work changes happen live.

Heres a log and all files i'm using.

Apologies for my Dishevelled mug on video I was bloody excited and had a late night working through some niggly stuff
[youtube]https://youtube.com/shorts/QAgYlvJjoWc? ... hYFnIX6Tnf[/youtube]

[delcowizzid]

Good effort

[jxx]

Nicely done

[Muncie]

The ribbon didn't work out in end as so many wires crossed sides so i tore them up the colours helped keep track at least.

Used J4 header as much as possible as its less fiddly then 4 wires to make up what was missing to U11.

I will redo this once i know its solid fit an interposer board to mount too...... I'll have to learn how to design a board

[Muncie]

Cars running fine live tuning works fine only issue i have is coms to onerom is sometimes hard to establish car off seems to work 90% of time key cycling or restarting tunerpro gets online.