nretro

nretro

Member Since 2 years ago

Experience Points
0
follower
Lessons Completed
0
follow
Lessons Completed
27
stars
Best Reply Awards
3
repos

0 contributions in the last year

Pinned
⚡ Main MiSTer binary and Wiki
Activity
Jan
8
2 weeks ago
Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

Those files work for me.

Jan
5
3 weeks ago
Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

OK... with that change in gary.v it works as expected. Entering the System -> ROM selector will trigger a reload of the ROM and sets ExecBase at 0x04 to an odd address which will trigger a cold reset and discard all resident structures.

Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

After a reset, the minimig core does not allow to write to the lower 512KB, because of the line sel_chip[0] = cpu_address_in[23:19]==5'b0000_0 && !ovl; in gary.v. So currently, we can not write to 0x04 in minimig_config.cpp. Changing above line to sel_chip[0] = cpu_address_in[23:19]==5'b0000_0 && (!ovl || cpu_hlt) should solve this issue.

The minimig core probably does not support to write a single byte via spi, at least the corresponding code in userio.v suggest that:

        toggle <= ~btoggle;
	if(btoggle) begin
	host_wdat[7:0] <= IO_DIN[7:0];
	mrx <= 1;
	IO_WAIT <= 1;
	end
	else host_wdat[15:8] <= IO_DIN[7:0];

I haven't looked any further, since writing an odd number of bytes is not necessary.

Jan
2
3 weeks ago
Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

It does swap all bytes. So writing 0x01 to 0x7 (or 0x01010101) to 0x6 is the right operation. Writing to 0x4 might not work for 68000, because this is just the top 8 bit of the Address, which this CPU ignores.

Just to make sure, that it is in fact 0x7, I wrote a small program: `s: moveq #0,d0 moveq #0,d1 moveq #0,d2 moveq #0,d3 move.l #12345678,data move.b data,d0 move.b data+1,d1 move.b data+2,d2 move.b data+3,d3 rts

ALIGN 0,4

data: dc.l 0 ` (Seka resp ASM-One syntax). Running this program results in D0=0x12 ... and D4= 0x78. If we want to ensure to have get an odd address, we therefore have to write to data+3.

Dec
31
3 weeks ago
Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

Thanks! While you are at it.. is there a reason, why Kickstart ROMs can only be selected from the Amiga directory? Used to be different and that's quite annoying, when you have more than 10 different versions. I reverted that change to

SelectFile(Selected_F[4], "ROM", SCANO_DIR, MENU_MINIMIG_ROMFILE_SELECTED, MENU_MINIMIG_CHIPSET1);

at case MENU_MINIMIG_CHIPSET2: in menu.cpp, adding the SCANO_DIR (instead of 0) option.

Just a suggestion, I

Dec
29
4 weeks ago
Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

One more correction: to make the 32 bit address at 0x04 odd, we have to write the byte 0x01 at address 0x07, since m68k is big-endian. Sorry, I'm a little out of shape.

Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

Minor correction: writing 0x01 to address 0x04 will do the trick. An odd ExecBase pointer (which is always at 0x04) will be rejected immediately. The corresponding code (in Kickstart 1.2) is:

FC014C move.l 4,D0 Get pointer at location 4. FC0150 btst #0,D0 Check if it is an odd address. FC0154 bne.s FC01CE Go reconfigure memory if it is. FC0156 move.l D0,A6 Assume we are pointing to ExecBase. FC0158 add.l $26(A6),D0 Get complement of ExecBase.

(see http://wandel.ca/homepage/execdis/exec_disassembly.txt)

Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

More Fast RAM Memory Options

More of a suggestion than issue - would it be possible to add 16MB, 32MB, 64MB and 128MB options for fast RAM? Currently there is jump from 8MB to 256MB. If I have to chose from those 4 options to add only one - then 16MB would be great. (there are different setup and most of turbo boards were between 8 and 32MB.)

nretro
nretro

if Debug ROM is actually implemented using HRTMON as debugger.

HRTMON sits at 0xa10000 not in the Debug ROM range at 0xf00000. The Debug ROM area can be used to add additional ROM libraries and every Kickstart jumps to that area in the very beginning, if the right magic number is present at 0xf00000. That's quite useful in a real Amiga, but I haven't yet missed it in Minimig.

Activity icon
issue

nretro issue comment MiSTer-devel/Minimig-AGA_MiSTer

nretro
nretro

Kickstart version not being completely flushed when switching configs.

Hi! I found this interesting oddity:

I have three Minimig configs: OS3.9 (KS 45.57), OS 3.2.1 (KS 47.102) and KS 1.3

By default I load OS3.9 - if I then load OS3.2.1, it incorrectly reports the Kickstart version as 47.57 (seemingly taking the xx.57 from the prior Kickstart) - in order to correctly show KS 47.102 in OS3.2.1 I have to load the KS 1.3 config before loading OS 3.2.1

This bug doesn't appear to cause any issues with 3.2/3.2.1 (I don't think it cares so long as the KS version is v47+) but I'm guessing it could if something checks the full version string?

nretro
nretro

You just have to write 0 to address 0 before the reset. Actually, this could be done automatically on loading kickstarts in minimig_config.cpp (Main_MiSTer). I'll have a look at it after the holidays.