You will not be able to post if you are still using Microsoft email addresses such as Hotmail etc
See here for more information viewtopic.php?f=20&t=7296
DO NOT USE MOBILE / CGNAT DEVICES WHERE THE IP CHANGES CONSTANTLY!
At this time, it is unfortunately not possible to whitelist users when your IP changes constantly.
You may inadvertently get banned because a previous attack may have used the IP you are now on.
So I suggest people only use fixed IP address devices until I can think of a solution for this problem!
terriblefire wrote: 22 Sep 2024 16:17
I've had feedback that this has fixed the issue. I suppose i should do a 2b version of the board.
As far as understand it from the Discord discussen the status is that the fmpak now works. The memory mapper does however not seem to work so always 64kb.
You can test the ram with ram check tools. It will show 512Kb. But MSX2 will only ever show 128K on the boot screen.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
As far as understand it from the Discord discussen the status is that the fmpak now works. The memory mapper does however not seem to work so always 64kb.
You can test the ram with ram check tools. It will show 512Kb. But MSX2 will only ever show 128K on the boot screen.
Yes could be in practice there is 64kb. So it seems there is still something not fully ok with the memory mapper although the fm now works. So for arcade cabinet use a big plus for other computing usage still some optimization seems to be needed on the memory side of things.
You do not have the required permissions to view the files attached to this post.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
terriblefire wrote: 22 Sep 2024 16:57
this is how the ram is mapped....
IMG_6531.jpeg
although i believe it's moved to slot3 now
It seems to have 64kb and the memory mapper does not seem to work.
At least this is the status @ Jeroen now and was also part of the issue I had. It was the fmpac and this.
Additional memory needs to come from external cartridge and so on…,
terriblefire wrote: 22 Sep 2024 16:57
this is how the ram is mapped....
IMG_6531.jpeg
although i believe it's moved to slot3 now
It seems to have 64kb and the memory mapper does not seem to work.
At least this is the status @ Jeroen now and was also part of the issue I had. It was the fmpac and this.
Additional memory needs to come from external cartridge and so on…,
Yes i can confirm this. I have a regression. It seems to be related to things i did while developing the MSX2 Mapper Cart. Shouldnt take long to sort.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Sent a new FW to Jerone let's see what the result is.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
One more fix was sent over. When this is verified i'll post 2 firmwares here. One for those with the WAIT fix done, one for those without it.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Hey, it seems that things are moving forward while I look away. That is great!
First of all, I'm very happy to hear that the memory mapper issue is finally fixed as Chuck suggested I need to change the faulty CPLD chip to get around the 64kB issue (I did not ever get to it) and now this sounds 100x more easy to fix!
... also cool that you managed to tweak the FM-PAC to work. I was under the impression that it was due to lack of +12v and -12v as the FM-PAC worked great when connecting to slot expander that had it's own PSU, but now it sounds like such monster setup might not be needed anymore... Very, very nice!
