Plutiedev's blog

F you, Movistar

Published on 2022-apr-18

Lots of swearing ahead.

OK so on February 10th some asshole thief cut off some cables from a pole in order to knock down a camera and in the process left us with no landline or internet.

Now, the telco in question used to be Telefónica (now Movistar) and they already had a reputation of taking their sweet time and leaving their customers two weeks without service upon any minor hiccup but wow, the new owners are much worse.

So we fill a complaint. No news, later we noticed that they marked the issue "fixed" without doing anything at all. We fill another complaint and they mark it fixed again within two days without doing anything. What the fuck? Whenever we'd get them to talk (nearly always at night, once they replied at midnight) they'd insist that there's an active report (yeah because we just reopened it you dumbass) and to keep waiting (one of them said to wait "12 work days" what the heck?) and would put different excuses each time (they even claimed the address was wrong) all this while consistently closing reports as "fixed" after 48hs (automated?). They did this shit six times in a row.

We found the address of their offices in Argentina and decided to directly pay a visit to force their hand… there was nobody in the lobby. The building was freaking empty. What the fuck, does anybody even work there?

Then finally after over a fucking month these assholes finally admit that the reason is that we're on broadband (because they refuse to do fiber in this zone) and that they don't have the required equipment anymore and that as such they wouldn't offer us internet service anymore ("but we're always improving" shut the fuck up) and that at most they'd offer us some device to make landline work. Oh, and they knew this since the first time they closed the report while marking it "fixed" instead of "won't fix" because they wouldn't tell us that they weren't going to bother at all. All this while demanding us to pay the monthly bill for the month where they kept actively refusing to provide service, by the way.


An angry iwis powerbooping a giant button non-stop extremely fast.

So there goes one month.

We finally convinced the landlady to switch to another company, and this still took about another month worth of waiting because apparently this crap went on through the whole area and the competing ISPs are short on staff to deal with the sudden surge in demand for them, because I guess that Movistar is happy to drop an entire neighbourhood.


Hope your fucking executives go to prison but I know that they are too busy swimming in money and living in a mansion away from the rest of the world because you don't believe in the existence of "peasants" who don't go to a bar to spend lots of money to get yoghurt with cereal, but you're crossing a fucking line here, even Edesur with their infamous long blackouts eventually fix their shit, and you had several fucking years to sort out your crap with fiber so don't come saying you didn't have time to prevent this.

Oh, and stop sending demands to pay the overdue bills when you already admitted you won't restore service and we already fucking cut you off, but I guess that you're a chronic bully who needs to punch every single idiot around for their lunch money, amirite? Because Movistar sent us a warning a few days ago. Yeah sure, GET THE FUCK OFF. NOW.

Now to catch up on a lot of stuff…

(PS: the yoghurt with cereal part isn't a joke, I saw a bar actually do it…)

What to watch out for when making cartridges

Published on 2020-oct-15

With all these new Mega Drive releases lately we've had a lot of people complain about cartridges being of low quality and potentially putting consoles at risk. Shouting at a dying forum or something is not going to help any vendors realize what they're doing wrong, so I'm quickly putting together here what to look out for. This probably deserves a proper page with strict specs to follow some day.

5V vs 3.3V components

Yes, this thing again.

Mega Drive is a 5V machine and everything on the cartridge slot is 5V. Modern components are usually 3.3V instead (or even 1.8V). Now, using modern components is great, you can get cheap Flash memory that way! But you absolutely must not mix 5V and 3.3V signals as-is.

If you're using 3.3V (or 1.8V) components, you must use a voltage regulator and level shifters (the former generates 3.3V VCC out of 5V VCC, the latter converts signals between both voltages). Connecting 5V directly to 3.3V components risks damage long term, in particular to the latter.

Board beveling

The hot topic of the day!

Something that may be easy to overlook is that the bottom of the board should be beveled (i.e. thinned down). This is important to reduce risk of damaging the cartridge slot: if the board isn't beveled then there's little room for margin to maneauver and you risk pushing down the pins when inserting the cartridge, potentially damaging it permanently. With beveling the board is easier to insert and pins will be at most pushed a bit outward instead, which is much safer.

Here's how the bottom of the board should look like (based on that PDF called GEN-CART-BASIC-fabnotes.pdf that keeps circulating around), note that 0.063 inches is a common thickness for boards:

The thickness of the board at the top is 0.063 inches, while it becomes 0.017 inches at the bottom. The beveling is done at an angle of 30 degrees, giving the beveled surface a height of 0.040 inches.

Chamfered corners

Related to the above, the bottom corners of the board should also be chamfered in a similar way, making them more rounded instead of hard corners. This one isn't as critical at least (failing to do this simply makes it a bit harder to seat or unseat the board) but you should still try to do it.

Ground shield

This one is easy to miss if one isn't putting much thought into it, but ideally you should cover up any empty space in the board with a trace to GND. This acts as a RF shield and helps reduce risk of interference with other nearby electronics.

Bringing this up since I've seen a few boards without it.

One last note

Check the actual boards please. I'm seeing a lot of people going "they make shitty cartridges!" over stuff that was done wrong long ago but nobody bothering to confirm if their newest releases still do it, or what they are doing wrong (because without details we have to assume the absolute worst). It starts getting hard to trust those comments if we can't tell for sure if they're still true nowadays (they may be, but we can't tell).

This gets even more important as new issues are found. Board beveling is something that people only started paying attention like last year or so. I'm sure that we'll find yet more issues in the future that we're currently ignoring, and we're probably going to be slamming manufacturers for getting that wrong back when nobody was paying attention.

I suppose there's also some mea culpa for not having put together yet a page giving full specs for cartridges to follow. It's very easy to get everything wrong when there isn't any checklist to follow, after all!

Game Gear on Mega Drive idea

Published on 2020-jul-13

One of the Mega Drive features is being able to run Master System games with an adapter. The Game Gear is mostly a handled Master System, but it has enough differences that playing those games on a Mega Drive isn't feasible (colors are all wrong, and also the Start button doesn't work so most games can't go past the title screen).

Some time ago krikzz revealed the Mega Everdrive Pro's features and one of the things is does is running NES games. It works by having part of the NES running on its FPGA and letting the Mega Drive handle video output. Now, this is just a "bonus" feature and it doesn't work great (CHR-ROM bank switching is a big problem), but for many games it should be good enough.

On the other hand this also got me wondering if it'd be feasible to take the same approach with the Game Gear. Its VDP is significantly less flexible than the NES PPU, so maybe the results could be better?

So here's an idea of how I think it could work (feel free to copy them). Note that the goal here is to try making most games work, but it's not gonna be 100% perfect unless take over the video output with a passthrough cable like the 32X.



The graphics would work as follows:

On VRAM/CRAM accesses:

On the tilemap layer:

On sprites:

On the palette:


68000 would be reading the controller every frame and passing its buttons to the Game Gear core. D-pad would be mapped as-is, B and C to buttons 1 and 2, and Start to… Start.

Probably nobody will bother with the Gear-to-Gear cable, but if you *really* insist, the port used by it is practically the same you can find on the Mega Drive itself (serial mode included!), so you could attempt to pass it onto the player 2 port… but you'd need a custom cable, another Game Gear or Mega Drive, and timing may make it unfeasible anyway.


Alternatively, you could implement a stereo PSG in the cartridge itself and push its output through the audio-in lines in the cartridge slot, which solves all the issues (but wouldn't be as fun :P).

Compatibility issues

Now obviously the above shows that compatibility isn't going to be perfect, and I'm not that well versed on the Game Gear catalog, but I can think of a few cases that are obviously problematic:

Super Game Boy approach

On the other hand we could take Nintendo's approach which was to put the entire hardware in the cartridge and treat the console as a glorified passthrough that just passes over controller inputs. Audio can go through the audio-in lines in the cartridge slot, so that isn't a problem.

Video is another issue. Display is 160×144, but Game Gear can output up to 31 colors (which won't fit in a single tile) so we need to send *two* screenfuls. That'd be 720 tiles to transfer. That'd require extending vblank to get all the bandwidth we can, which means the border will have to be a solid color. Assuming 320×224, that'd require 117 lines to transfer (ignoring overhead). With the extra vblank time we get from disabling display in the border we get… 112 lines (in NTSC). Oops.

Many Game Gear games push against the borders of the screen, so trying to remove lines is probably not an option, which means you'd need to get accustomed to tearing. You could try to optimize by avoiding sending tiles that haven't changed or don't need both palettes, though it only reduces the chance of it being an issue and would be harder to implement.

Oh, and don't forget about the palettes. Again, the above was all assuming the palette doesn't change mid-screen, which breaks some raster effects. Trying to transfer 31 colors per line is not easy. You could probably disable display mid-line (the borders to the sides really help here), but even then expect to still see a few CRAM dots on the sides of the screen.

YM2612 programming warning

Published on 2020-jan-03

I've already seen at least a couple of homebrew games trip over this so I think this deserves a warning.

Do not rely on undefined behavior when reading the YM2612 status. The behavior differs between hardware revisions, and your game will break on a lot of consoles if you don't follow this advice.

If you're using one of the popular sound drivers this shouldn't be an issue, but if you're making your own sound code, mind the following:

In particular, always make sure to read only from $4000 (or $A04000 if accessing from 68000), and to not expect a particular byte value to show up. If you're waiting for the YM2612 to stop being busy, only check bit 7 and ignore the rest, if you're waiting for the timers then only check the relevant bit.

Just because it works on your console doesn't mean it will work on all of them. If you can't afford to test multiple revisions then at the very least follow the above advice to get you out of trouble.


The Mega Drive underwent several hardware revisions over time to reduce costs. In particular, there are two major variants of the YM2612 in use (the original discrete YM2612 and a later YM3438-based variant integrated into the main ASIC). On top of that the Teradrive uses a discrete YM3438.

These variants differ in how they handle reading the status port in undocumented ways. Some variants only return a valid status value on the first address ($4000), and on top of that the values of bits 6-2 may be either zeroes or a previously written value depending on which variant it is (which is why you should ignore their value).

Retroflag Controller-M review

Published on 2019-nov-15, last updated 2019-nov-15

Earlier this month I purchased a Retroflag Controller-M and I thought I may as well make write a review of it. Testing involved playing Xeno Crisis, a full playthrough of Arkagis Revolution and iwis slapping the buttons because she likes clicky sounds.

Here's the link for the official Amazon listing for the controller. As a disclaimer, I bought it from a local store in Argentina instead (to avoid having to deal with import headaches).

Retroflag's controller looks pretty similar to a Mega Drive 6-button controller, down to the size. There are some practical concessions however: there's a Select button on top of the Start button, and instead of a Mode button there are L and R buttons. The latter two are built to look like the original Mode button, which is nice.

(iwis claims that it's not L and R buttons but "weft mode" and "wight mode" buttons)

The D-pad seems to happily take all the abuse going on so far (turns out Arkagis Revolution is surprisingly hard on the D-pad), albeit of course the question is how many months it will last. At least pressing the directions feels nice. The L and R buttons may be a bit too easy to press, so be careful where you place your fingers, but everything else seems OK.

The Controller-M shows up as either a generic XBOX controller (if in XInput mode) or a generic retro controller (if in DirectInput mode), so get ready to rebind buttons (at least the button mappings seem decent). This may or may not be an issue depending what you're using, the controller lets you swap Z/C with L/R if really needed. The controller also works with a Switch, according to their site.

If you're OK with the original 6-button controller's size and are ready to rebind buttons, you should be fine.

Known issues

Input details

The controller maps its buttons like this:

Retroflag's site includes how the controller buttons map to a modern controller's buttons, but the box also mentions some features that I'm going to include here in case somebody loses the box and needs help: