Help with update to MIST build v1.2

[WeiXing3D]

Could you please point me to where I can find information on how to perform a system build update on the MIST?

I still don't know what do I do with these 8 files inside the zip folder with the update:

AROS ROM
firmware.bin
firmware.upg
HRTMON.ROM
minimig.art
minimig.bal
minimig.cop
minimig_mist-1.2.rbf

Do I copy and replace first all these files to the root directory of my SD card?

Thank you.

[AmiDude]

https://code.google.com/archive/p/mist-board/wikis/CoreDocAmiga.wiki

[kolla]

Could you please point me to where I can find information on how to perform a system build update on the MIST?

I still don't know what do I do with these 8 files inside the zip folder with the update:

AROS ROM
firmware.bin
firmware.upg
HRTMON.ROM
minimig.art
minimig.bal
minimig.cop
minimig_mist-1.2.rbf

Do I copy and replace first all these files to the root directory of my SD card?

Thank you.

You do not need firmware.bin

With firmware.upg on the root of the SD card, you can go to the firmware menu entry, where you will see that your current firmware is different revision that the one of the disk - here you can upgrade the firmware.

minimig_mist-1.2.rbf you can load the from the "load core" menu, or if you are only using the MIST as an Amiga, you can rename it "core.rbf" on the root of the SD card.

HRTMON.ROM is needed to enable HTRMON, if you don't know what it is, it doesn't matter.

AROS.ROM is of course the AROS kickstart, if you want to play with it.

minimig.art, minimig.bal and minimig.cop you only need if you want to see the boing and info stuff on screen as the core is loaded.

[WeiXing3D]

You do not need firmware.bin

With firmware.upg on the root of the SD card, you can go to the firmware menu entry, where you will see that your current firmware is different revision that the one of the disk - here you can upgrade the firmware.

minimig_mist-1.2.rbf you can load the from the "load core" menu, or if you are only using the MIST as an Amiga, you can rename it "core.rbf" on the root of the SD card.

HRTMON.ROM is needed to enable HTRMON, if you don't know what it is, it doesn't matter.

AROS.ROM is of course the AROS kickstart, if you want to play with it.

minimig.art, minimig.bal and minimig.cop you only need if you want to see the boing and info stuff on screen as the core is loaded.

Thank you very much for the detailed answer.

Unfortunately, and after following your steps to the letter and when everything seemed to be fine after a first boot, a reboot later prompted random Workbench error messages and Guru meditations.
So, I thought that I had done a bad update, but it turned out that what I have done to update to v1.2 was fine.

When i restored the old core (v1.1) the errors went away and the MIST works fine again.

Is anyone experiencing this? Is this a bug? Otherwise, why core v1.1 works fine, but not 1.2?

[AmiDude]

All the info was already in the link I posted...

[kolla]

So, I thought that I had done a bad update, but it turned out that what I have done to update to v1.2 was fine.

When i restored the old core (v1.1) the errors went away and the MIST works fine again.

Is anyone experiencing this? Is this a bug? Otherwise, why core v1.1 works fine, but not 1.2?

Can be so many things, depending on what software you run. I have not really noticed anything not working with 1.2 that used to work with 1.1 yet, but a lot of things that did not work with 1.1 does work with 1.2.

You should be more detailed about what those errors are, and narrow down what software that causes them.

[WeiXing3D]

Can be so many things, depending on what software you run. I have not really noticed anything not working with 1.2 that used to work with 1.1 yet, but a lot of things that did not work with 1.1 does work with 1.2.

You should be more detailed about what those errors are, and narrow down what software that causes them.

EDITED: I hope I can get somebody's attention. As reported before, I'm having problems using the new core (v1.2) and firmware update. The system boots fine only at times, but most of the time it gives all kind of random Workbench errors, Guru messages and red flashing screens.

When it boots and things seem OK, trying to play any games would give all kind of messages and freeze the system.

I have another SD card in which I still use core v1.1 and everything works perfectly, well I still have to reboot to be able to get any memory recognized, but everything works fine. I have tried core v1.2 with different brands of cards and memory size, yet with the same results....error messages galore.

Could anybody help me to trouble shoot this issue? Is this a known issue? Thank you.

[kolla]

Again - you need to be more specific about those error messages you are seeing, and also describe your system in more detail. In you signature it says "Workbench 3.9 configuration", but what does that imply? BB2? BB3+4? Using what hacks&patches?

[WeiXing3D]

Again - you need to be more specific about those error messages you are seeing, and also describe your system in more detail. In you signature it says "Workbench 3.9 configuration", but what does that imply? BB2? BB3+4? Using what hacks&patches?

Regarding the OS3.9 update patches, I don't know which ones are installed since I bought the MiST with card already configured for me using my OS3.9 license. Is there a way to check that?

As for the MiST, I'm using firmware VER ATH160221, core_1.2 and firmware.upg file of February 21.

But then again, how come v1.1 works very stable and 1.2 doesn't work, in the same system, using the same sd cards?

EDITED with screenshot:









After this what I get a Guru meditation screen. Rebooting just makes the system to go in the same cycle. Once in a blue a moon, I do get the system to boot up, but then it'd would freeze when trying to run a game or app.

[WeiXing3D]

Since I haven't received any replies, I am adding some extra information, hoping that someone comes to my rescue.

CHIPSET : cpu 68020, turbo none, video pal, chipset AGA, cd32 off
MEMORY : CHIP 2.0, slow NONE, FAST 24 MB (try also with 4 MB), ROM
kick3.1, HRTMON disabled
VIDEO : lores / hires none, scanlines dim, dither SPT
Hardfile Workbench 3.9

And yes, firmware says ATH160221. I am using the file firmaware.bin and firmware.upg posted on February 21 in the Atari Forum. I have copied those two files, plus the new core.rbf to the root of my SD card. Then from the OSD menu I navigated to the Firmware & Core option and Update.

After booting it shows that I'm running v1.2.

Honestly, I am not so sure that I am doing the upgrade process correctly. This is the first time since I bought the MiST that I am doing an update.

[Epsilon_]

Since I haven't received any replies, I am adding some extra information, hoping that someone comes to my rescue.

CHIPSET : cpu 68020, turbo none, video pal, chipset AGA, cd32 off
MEMORY : CHIP 2.0, slow NONE, FAST 24 MB (try also with 4 MB), ROM
kick3.1, HRTMON disabled
VIDEO : lores / hires none, scanlines dim, dither SPT
Hardfile Workbench 3.9

I recently upgraded my MIST to the latest firmware 1.2 and the latest stable Minimig AGA core and it is quite stable. I am not sure I can help but will offer some ideas in case they do...

1. OS3.9 needs 6MB fast memory so running with 4MB on the MIST I believe is a nonstarter. Use 24MB.

2. c:version error on boot usually indicates problems with boing bag ROM updates. You can test this by renaming Rename "DEVS:AmigaOS ROM Update" file to something else and see if it boots properly.

You can also modify s:startup-sequence on the setpatch line to achieve the same thing:

C:SetPatch NOROMUPDATE QUIET

In my experience boing bag 2 update in particular often cause weird problems anyway because of the ROM update.

3. There is no FPU on the MIST so make sure you aren't running any FPU required utilities, datatypes or software in s:user-startup, wbstartup, etc.

I hope some of this helps.

MIST is a lot of fun for sure. I am having a ball with it! :-)

http://amigax1000.blogspot.com.au/2016/02/mist-minimig-aga-system-has-arrived.html

Catcha,
Epsilon

[WeiXing3D]

I recently upgraded my MIST to the latest firmware 1.2 and the latest stable Minimig AGA core and it is quite stable. I am not sure I can help but will offer some ideas in case they do...

1. OS3.9 needs 6MB fast memory so running with 4MB on the MIST I believe is a nonstarter. Use 24MB.

2. c:version error on boot usually indicates problems with boing bag ROM updates. You can test this by renaming Rename "DEVS:AmigaOS ROM Update" file to something else and see if it boots properly.

You can also modify s:startup-sequence on the setpatch line to achieve the same thing:

C:SetPatch NOROMUPDATE QUIET

In my experience boing bag 2 update in particular often cause weird problems anyway because of the ROM update.

3. There is no FPU on the MIST so make sure you aren't running any FPU required utilities, datatypes or software in s:user-startup, wbstartup, etc.

I hope some of this helps.

MIST is a lot of fun for sure. I am having a ball with it! :-)

http://amigax1000.blogspot.com.au/2016/02/mist-minimig-aga-system-has-arrived.html

Catcha,
Epsilon

@epsilon
Thank you. It's nice to see that someone is reading this thread and trying to help. I've been reporting these issue for a while now.

I checked my Memory Settings and Chip goes only from 0.5 M to 2.0 MB, so I am using the max available. Or can this be changed? For fast memory, I'm using 24 MB.

For Firmware & Core (ARM & File) I'm showing ATH160221; it remains unchanged even after I perform the update using the new files uploaded on Feb. 21

I followed your suggestions for:

2. c:version error on boot usually indicates problems with boing bag ROM updates. You can test this by renaming Rename "DEVS:AmigaOS ROM Update" file to something else and see if it boots properly.

You can also modify s:startup-sequence on the setpatch line to achieve the same thing:

C:SetPatch NOROMUPDATE QUIET

And I can boot now, but the system still crashes after attempting to play some games that used to play well before the update.

I'm still inclined to believe that I didn't do a proper frimware update. This is the first time I try; I don't even which files to copy, where or what to do with them. I'm referring to the files in the zip folder that was posted with the firmware and core upgrade on Feb. 21/ I found it in the Atari forum.

[Epsilon_]

@epsilon
Thank you. It's nice to see that someone is reading this thread and trying to help. I've been reporting these issue for a while now.

I checked my Memory Settings and Chip goes only from 0.5 M to 2.0 MB, so I am using the max available. Or can this be changed? For fast memory, I'm using 24 MB.

For Firmware & Core (ARM & File) I'm showing ATH160221; it remains unchanged even after I perform the update using the new files uploaded on Feb. 21

I don't quite understand what to do with:

2. c:version error on boot usually indicates problems with boing bag ROM updates. You can test this by renaming Rename "DEVS:AmigaOS ROM Update" file to something else and see if it boots properly.

You can also modify s:startup-sequence on the setpatch line to achieve the same thing:

C:SetPatch NOROMUPDATE QUIET

Could you please explain in terms a little bit lighter ?

UPDATE: I have a whole bunch of Amiga OS Update files under DEVS:



In any case I can't Rename the DEVS: Amiga OS Update file, or modify the startup-sequence because it gives DOS error messages.

Your firmware is the latest version already.  ATH160221 is 20160221 (ie. February 21, 2016).

To troubleshoot the other problems you are having, reset the Minimig and when booting, hold both mouse buttons down for the early startup menu. choose Boot with no startup-sequence.

At the Shell prompt type (press enter after each line):

prompt

assign env: envarc:

ed s:startup-sequence

modify the line in the startup-sequence that says c:SetPatch to say:

C:SetPatch NOROMUPDATE QUIET

Save and close Ed. Then reboot and see what happens.

This change should stop OS3.9 from patching the kickstart with boing bag updates.

Let me know if it helps or you continue to get the same errors as before.

If you are still getting the errors please post your startup-sequence and user-startup contents here.

Catcha,
Epsilon

[WeiXing3D]

@Epsilon

Thank you again for your guidance/help.

This is a screenshot of my startup-sequence after making the change in the C:SetPatch

It boots OK, but I still notice that some games that worked before are not working now.

[kolla]

Yes, the process with loading rom modules may very well be the problem. This will not work with 1.1 since the reset induced by "SetPatch" will cause the FastRAM to vanish. With 1.2 the FastRAM stays put, and it should in principle work. However, I do something else, I built my own 3.9 kickstart file and use "NOROMUPDATE" option of SetPatch.