Started by OffseT, 16:51, 24 January 21
0 Members and 1 Guest are viewing this topic.
Quote from: Maniac on 01:02, 22 September 21Finally got around to trying this out now that M4 support is available. This is a brilliant development but I think I've found a bug even if it might be unique to my setup.My setup is a 6128 Plus with a C4CPC cartridge, an X-Mem (with ROMboard element disabled) and an M4 Board. I'm using the M4 board for the ROMs as shown in the screenshot where UniDOS is in slot 7.The C4CPC is running the original Plus cartridge image with no other ROMs present.When I have all of this connected the system runs fine for the most part until I run the command ¦drive on its own. When I do this the command lists the Available DOS devices and Logical drives and then the system crashes with vertical lines down the screen. Reset try again and it happens every time.If I switch my cartridge to the original physical system cart (i.e. not the C4CPC) then it all works without issue. So I thought it was (and most likely is) a conflict between the various devices providing ROMs. However I then switched back to the C4CPC and used the Firmware 3.16 cartridge image and it works but I have no access to the disc drive just the M4. So I created a custom cartridge image using the new tool you made to do this with the ROMs in the same slots as the screenshot above and removed the ROMs from the M4 slots and I still get the same issue with a system crash.To test further I then switched the ROMs about on the M4 as shown in the screenshot with UniDOS in slot 6.Thought I'd cracked it as the ¦drive command worked initially but now crashes consistently again.Everything else works that I've tried but this I'm afraid.
Quote from: Cwiiis on 03:09, 22 September 21I see similar things with just the X-Mem on a Plus and I think it's actually power related - I see it more easily if I use a separate power adapter rather than the monitor which leads me to think it's a voltage drop caused by the extra power draw of the X-Mem and C4CPC combined. I have an MX4 on the way which I'll configure with external power to see if it affects things.
Quote from: Maniac on 10:13, 22 September 21Good to hear that I'm not the only one. I might disconnect the internal drive and just use my externally powered HxC to see if it still happens.
Quote from: Maniac on 20:22, 22 September 21[...] will long file name support be coming to the M4 node please? Or is this something that could be added to the main UniDOS ROM in the future please?
Quote from: OffseT on 13:49, 22 September 21That's interesting.So, I just did some tests and I it actually appears to be some power drain issue.Here is my base config (which is quite stable as I am using it everyday):6128plus + Mulfiface Two + Albireo + MegaFlashGordon + Nova + dual floppies (both powered by the monitor)What I experimented:Base config + C4CPC -> still perfectly stable.Base config + M4 Board -> still perfectly stable, but I can notice that the blue led of the board is slighlty blinking when floppies are being used.Base config + X-Mem -> still perfectly stable.Base config + C4CPC + M4 Board -> don't even boot, at best it crashes during firmware start, most of the time even before.Base config + C4CPC + X-Mem -> don't even boot, at best it crashes during firmware start, most of the time even before.I also tried with an USB stick plugged on the Albireo: no changes; when it is stable, plugging a USB stick won't make the system unstable.Please also note that I am not using the Mother-X4 which is known to have issues regarding 5V power drain when no external power is used.Then I also tested with an Amiga external power supply able to deliver 5A:Base config + C4CPC -> perfectly stable.Base config + M4 Board -> perfectly stable, blue led not blinking anymore.Base config + X-Mem -> perfectly stable.Base config + C4CPC + M4 Board -> booted once, but crashed after a while when doing nothing.Base config + C4CPC + X-Mem -> don't even boot.All of this make me think that the issue is not only related to the power supply itself but also to the way the motherboard is designed to deliver the 5V to all the components. I guess we are reaching some limits of what can be plugged together on a Plus.I'm afraid you will have to choose between M4 Board and C4CPC.About |DRIVE, since it is accessing all the devices together, it makes sense that it could triggers easily the power issue in your case.
Quote from: gerald on 20:39, 23 September 21What is your configuration regarding the M4 or XMEM ? If you enable a lower ROM on these, you will have some trouble for sure as the C4CPC will not be able to control CPC boot. It will load the cartridge while the lower ROM (one the M4 or XMEM) will run and possibly try to access it during its init process.
Quote from: gerald on 21:32, 23 September 21The C4CPC consume about 70mA more than the original eprom and is using a 3.3V local voltage regulator. It would require quite a big voltage drop to prevent the regulator to properly work (it need at less 3.7V). Also, on one of my plus, I measured the path from the power switch to the cartridge : 0.17ohm + 0.03ohm on the ground at the power plug, so a voltage drop of less than 20mV from plug to cartridge.Other option are possible : - power switch is not that clean, and then we can have voltage drop that can affect the whole system. But then accessing a drive (real one) would cash the system too.- load on bus such that some signal do not behave properly anymore. - ...I do not have any issue with the C4CPC + XMEM combo. Need to find time to test the M4.
Quote from: OffseT on 21:53, 23 September 21The initial related issue from Maniac is a crash which occurs during the UniDOS |DRIVE RSX, which is actually accessing all devices (including disc drives) in a row.Drive motor should be considered as an issue trigger.Regarding X-Mem, as I said, I have no issue either with it unless I add numerous other interfaces.Maniac instabilities might be easier to trigger because of an aging power supply.
Quote from: Maniac on 17:04, 24 September 21Think I spoke too soon! Upgraded to v1.36 of UniDOS and got back to a similar position although the crashes don't happen quite so frequently.
Quote from: OffseT on 19:55, 24 September 21Case 1:Base config + M4 Board + X-Mem + System cartrige|DRIVE never crashes.Case 2:Base config + M4 Board + X-Mem + C4CPC (set to start with system cartridge)|DRIVE leads to a crash from time to time (filling the screen and all memory with &00,&3c,&00,&3a).Weird.
Quote from: m_dr_m on 20:41, 08 October 211/ Are you sure you can replace your ROM 7? (It doesn't work with unmodified CPC 6128)
Quote from: m_dr_m on 20:41, 08 October 212/ I though M4 was meant to be as ROM 6, but I might be wrong.
Quote from: zhulien on 21:01, 08 October 21The documentation does say that the assignments are persistent but so far for me they reset every reboot. Also I am unsure if the NOVA is actually doing anything, is there a way to tell?
Quote from: zhulien on 18:57, 08 October 21Symbiface 2 is listed as compatible, is that using the same driver as X-Mass? Is Symbiface 3 supported yet or would that need a different driver?
Page created in 0.084 seconds with 50 queries.