MEGA65R3 Batch 2 Release 0.95 Release Candidate

This is the first Release Candidate for MEGA65R3 Batch 2 Release 0.95.

DevKit Owners and MEGA65 Owners: We need your help! Please test this core!

The package uses the new structure for release packages and has all the regression test logs inside. It was completely autobuild and has WARNING files stating if something went wrong.

Get the packages:

• mega65r3/r2: Filehost - MEGA65 Batch 2 Release Test Build
  
• nexys4ddr-widget: Filehost - MEGA65 Batch 2 Release Test Build (Nexys)

Please check the contents of the archive and read through the files.

MEGA65 Release Disk (mega65-release-prep) was updated with the new ROM 920377.

Changes since the first test build:

- merge secure-flash branch into development branch

- freezer sprited fixes

- freezer less border flashing

- freezer display fixes

- vic-iv raster irq & fnrstcmp fixes #609 #609

Updated See the wiki for instructions and what to test: Release verification 0.95 (batch #2) instructions and tips

- make sure that you use the right options with m65 tool!

- watch the MEGA65 Release Test Live Video, if unsure

Note that we also have new mega65-tools builds in CI-refactor-latest

- Mac OS X autodiscover (thanks to kibo)

- mega65_ftp will check for loaded PRG (could nuke MEGAFLASH!)

As this is now a Release Candidate, please test everything!

Please report problems by posting a reply to this. If it is something obviously critical feel free to file an issue instead. flasher, onboard, fdisk, config, and core to the mega65-core repo, release disk stuff to the mega65-release-prep repo.

Please also report successful tests!

Note: mega65r2 and nexys4ddr builds are not in focus here, but you can also test on those platforms. There might be some stuff you can't do, like flashing a core using the build in flasher, but other stuff should also work on those boards.

Important Warning!

Make very sure to use a proper 8.3 DOS filename for your core!

That means:

• only UPPERCASE LETTERS and DIGITS
• only one point after 1-8 characters
• point followed by the three characters "COR"

The flasher does not know vFAT long filenames and so the garbled short 8.3 name that is autogenerated might be bad.

Even "somecore.cor" (lowercase) is not a 8.3 DOS filename!

Quote from clarkkent

I see this kind of constraint as a step backwards.

A security notice is a step backwards? Ok. I can't understand this.

You understand this is a RC, which means testing. Right?

Testing means finding problems. Right?

And fixing them. Ok?

So. Here we already have the first problem and I instructed you how to not run into while testing.

So how is this a step backwards? Please explain!

Please keep the discussion in this thread focused on testing the release candidate. Feel free to discuss other topics elsewhere.

Thanks!

I will be going live with some RC1 flashing Demo Stream in about 6 hours from now.

MEGA65 Release Test Live - RC1 with Windows