Many thanks @jotego for your comments. I have tried to get this subject discussed in a previous dedicated Topic but I have not been successful in getting comments/backing from programmers.
It can be difficult. Programmers need to remember these are not personnel comments/attacks. As a community we all want fully working Cores and to have a 'design guide' to ensure that Cores work on all MiST PCB revisions/RAM chips only benefits the community.
I am very methodical and solve engineering problems for my job, but I don't have any programming knowledge or FPGA knowledge, so although I can create forms/collate information/analysis results, I can't say for sure "Core x has SDRAM timing issues with Y chips on v1.2 PCB vs Z chips on v1.3 MiST PCB". I can only look at what the community provide me with and put forward the results.
Another big variable across MiST operation is the SDcard. FAT, FAT32, capacity size (2GB, 8GB, 32GB?), speed rating (Class 2,4,10 etc) and single Core or multiple Cores with MiST Menu (and what Menu version is being used). - I say to make things easier just have the Core being 'tested' on the SDcard, nothing else.
The ZX-Uno forums have a great spirit for helping each other, we can improve
Like the Core programmers getting satisfaction in writing a Core, I get satisfaction in problem solving. We have all the knowledge and the people to help, it is just getting people to work together and the Core programmers to spend some time 'rubber stamping' what they might think is a fully working Core for them.
To me there are 3 Cores which need looking at to start with; Sam Coupe, MSX & Archimedes. Identifying who is the 'Core Lead' would be a good start, or someone who is able to modify the existing work.
My proposal would be to start with the Sam Coupe. What is the issue you ask. Well this is a classic example, the latest Core (Release 20170206) does not work properly, but the one before does (Release 20170112). Other people need to check to see if they experience the same.
Core - https://github.com/sorgelig/SAMCoupe_MIST/tree/master/releases
And again, if it works you don't just say "it works". We need the variables. PCB version. SDcard info. Link to where did you download the BIOS (if Core requires it etc). Link to the file you test with.
And again, there are differences between a working Core and one where some special DEMO or coding does not quite work.I am trying to focus on the 'it works on one MiST but not at all on another MiST' (which they 'should' be all the same).
For example the BBC Mirco Core, a lot works and works well. A few games/demos don't work, but they do work on the ZX-Uno. So we might be able to take info from another Core or unfortunately it might be down to the hardware used. - and fixes have been made working together. So the BBC Micro Core is a great example what what can happen.
Sorry for the long post, but we got to talk and it is better if we all work together to solve issues