EverDrive Forum

General => SD2SNES => Topic started by: mancyrix on December 28, 2018, 05:36 AM

Title: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on December 28, 2018, 05:36 AM
 :'(i have my Sd2snes for years,and i update firmware time by time til 1.8.0 .

however ,since i updated to 1.8.0, each time it boot and saying is “flash check error (clone?)” such message.
but still boot sucess and load games normal, can play fx games.

I suspect my card is somehow like a clone/chinese clone.

I have tried upgrade to 1.9.0, but it have no any result and still boot with same message “flash check error (clone?)” , and info show is still 1.8.0 firmware.

I have another sd2snes with is able to upgrade with same sd card to 1.9.0.

I want to ask, if there is any way to force upgrade/ downgrade the firmware to either 1.9.0 or 1.7 something?
now my sd2snes is stucked at 1.8.0 with that “checksum error (clone?)” message each time and I cannot change firmware to any older and newer one……

can anyone help, thanks
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: dreimer on December 28, 2018, 05:42 PM
Nope, no help for clones. Especially not in the forum of a official reseller/partner of the sd2snes maker. As you just witnessed your card was detected as cheap clone with low quality components. Nothing to change that fact, it is what it is. You're lucky your card still lives and now just does not up-/downgrade anymore after the usage period it already passed.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on December 29, 2018, 02:28 AM
There's something i don't get...

The PCB design and BOM of the SD2SNES Rev. F is open source and freely available on the GitHub of ikari_01:

https://github.com/mrehkopf/sd2snes/tree/develop/pcb/kicad/RevF

I recently saw a community project on a retro forum, where a user started to assemble a couple of SD2SNES for other forum members using those GitHub files. The project will be done in the near future. So... will all those forum members get the "flash check error (clone?)" message with their DIY SD2SNES carts too!?
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on December 29, 2018, 07:19 PM
yes, you know, honestly, i have bought my first sd2snes in some chinese site, but at that time i dun even know how "official" or not these things are, and I am sure not knowing it is a clone or not.

And one important thing that trigger my first purchase at that time is, it stated as open source and github files opened.
So those seller or even you say doing " clone" sellers, they saying all are the same.

And you know, actually, many of these are still seller newer versions that is able to upgrade.
My first card was a e1 board, and it sold from 0.1.6 firmware, I have always able to upgrade from 0.1.7a- e ... all able to run and never having these sudden messages saying "clone".  Also, I can always switch back to older firmware free to go.

But since i updated to 1.8.0.  I was meeting this situation and no able to switch older firmware or higher.
 
I not to argue what is official or not, as I am just a victim honestly , if i am being convinced by those "unofficial" "clone" seller. 
So what I am asking is, shall I be allowed to switch back to lower firmware, or upgrade further.

You know, I also later bought a "official" one from UK and it is work flawlessly.  I am a real supporter of sd2snes as well.
I just , wish to seek for help or, as previous post reply for, when anyone using open source to build the board, it means a clone??

and base on what judgement shall it be locked to this situation (not able to upgrade/downgrade). 

I wish to have a humble answer and more fair.

Anyway, thanks for all~
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: dreimer on December 30, 2018, 01:51 PM
If the carts would be the same, there would be no way to detect em. Chinese carts are cheap because of a reason. Crap components and these can be detected. Too slow replies to RAM access for example can be useful for detecting AND for trouble on some special chips. You are free to build your own, yes all is open, BUT stay on the specs when doing so!

I have no clue if this is a lock or a hardware fault on your side, but even if it is a lock, I support the idea. Dozens of ppl come in here and lament about their dead sd2snes and what is revealed way too often? Crap clone! That way you have a nice filter to help ppl who bought the support with their price and concentrate on these instead of helping to fix a neverending plague of lowest quality hardware claiming to be a sd2snes.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on December 30, 2018, 04:15 PM
Chinese carts are cheap because of a reason. Crap components and these can be detected. Too slow replies to RAM access for example can be useful for detecting AND for trouble on some special chips. You are free to build your own, yes all is open, BUT stay on the specs when doing so!
It still makes no sense. Regarding the cheaper Chinese SD2SNES: if i remember correctly, ikari_01 himself said something about some parts with slightly different values than recommended in the BOM (for example some resistors and resistor arrays) - but he described them as 'uncritical'.
Afaik most of the problems with those Chinese 'cheapo-SD2SNES' stem from bad solder jobs, where they used far too less (or even close to none) solder paste in the manufacturing process - just to keep the costs as low as possible. This could result in something like the secondary RAM not working (which would go unnoticed in the past... until the GSU1 core came out) or even the SD2SNES not booting up at all. But bad solder joints can happen to somebody building his own SD2SNES manually too.

And even if there are crappy components: some parts reached their eol and are only available via Chinese sellers over eBay or on Alibaba. So you have no choice but to buy those remainders if you want to stick to the specs...


I have no clue if this is a lock or a hardware fault on your side, but even if it is a lock, I support the idea.
I do support the idea in general... but in this case i can't. Because in this one it's not as simple as with the Chinese Everdrive clones. With those i was all for the lock/brick of the clones, since it violated the intellectual property of krikzz by plagiarizing a product he created and kept close source.

Ikari_01 on the other hand gave his idea to the public, by making his product open source. That's why it's strange talking about 'Chinese SD2SNES clones'. There was no reverse engineering involved and no other attempt in creating a 'close-as-possible-to-the-original' hardware design. It IS the original hardware design... just with far less build quality ;) .

So while i'm strongly in favor of NOT giving any technical support to buyers of a Chinese SD2SNES in here (because buyers of the 'krikzz-produced' SD2SNES are paying more money... simply for better build quality and technical support), i'm not in favor of punishing them baseless either.

In the end simply ask yourself this (to give another kind of 'close at home' example out of the retro community):
If someone would have the possibility to cheaply build one thousand OSSC and he would sell these for 25% less then what they are sold on VGP - would it make sense to call them 'clone OSSCs'? If they were less good, people would call them 'less good', 'crappy' oder 'cheap'... but i'm pretty sure, they would call them 'clones' ;) .
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 02, 2019, 07:52 PM
thanks all for the replies,

honestly, i do think we all know there are different level of boards in these open source references.
And we all know some low quality components are used in these boards.

I again, give a best support to "official sellers" after realised.too.

I think Tom is well understand the argue points, and remorse our situation for this situation being locked firmware all at a sudden.

You know, I tell you, in this 1st board i Got, it is really all good running, and all success upgrade firmware til 1.8.
And then it say it is a clone(with a question mark as well in the shown message).   
Before, I have even used the diagnose tools and all test are 100% correct at that time.
(I have no mood to retest it as it is not easy, also I doubt there will be a sudden change test results, just to show some late tackle on the so called clones detection).

I appreciate to have an official answer for , who and what reason and what criteria to have a test and even it says in doubt for if mine is a "Clone"?...then without any consent, to locked the firmware at 1.8 and never able to downgrade and upgrade.

I can guess, possibly some components are being identified as "Not fully matching the ideal" , maybe from some latest reviews from ikari?
and actually, if it allow me upgrade from 0.16 to 0.17 to 1.8....then why now not allow upgrade ,even downgrading not allow?

I can accept a concrete answer , and if possible an alternative way to relax the limitation. It can be something like a warning but not to totally stop upgrade/downgrade.

Honestly, we are victims, we not fully clever to distinguish at first for a famous sd2snes card seller supposed to be located.  But we do not believe we are deserved to be punished for being locked at all.

thanks and I still hoping some people can help or providing some humble advise on the actual detection mechanism since 1.8.

Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 02, 2019, 11:44 PM
Well, I have a "CLONE" running 1.9.0 without any problem. Testing S-DD1 from magno and 100% working too.


So, I doubt that there is a "clone detector" in 1.8.0 and upwards.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 03, 2019, 01:24 AM
If you consider the lots and lots of those Chinese "clones" in use, there were surprisingly few posts about this 'flash check error' message. And since it only seems to affect people which had their SD2SNES for quite a while, it may only have an effect on some specific(?) or older revisions of the board (maybe E2)!? I dunno... but it's strange for sure.

It may be possible to get rid of the message (and downgrade to an older firmware) by reflashing the bootloader. But to do so you need to connect an appropriate programmer for the Xilinx Spartan FPGA to the JTAG connector of the board (as far as i know). All in all: not a simple thing to do...
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Terminator2k2 on January 03, 2019, 12:37 PM
Well, I have a "CLONE" running 1.9.0 without any problem. Testing S-DD1 from magno and 100% working too.


So, I doubt that there is a "clone detector" in 1.8.0 and upwards.

you dont have official firmware either, ikari doesnt upload his clone detection firmware to github.

if i was ikari i would of just given sd2snes the chop and build some detection into sd3snes
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 03, 2019, 12:44 PM
if i was ikari i would of just given sd2snes the chop and build some detection into sd3snes

Why?

And yes, I've tested all official firmwares too...

[EARTHBOUND MODE] No problem here! [/EARTHBOUND MODE]
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Terminator2k2 on January 03, 2019, 12:58 PM
why?

because ikari gets nothing from people buying clones, and only gets something through people buying via official channels....

when sd3snes launches, im sure it wont be so open as it is now.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: dreimer on January 03, 2019, 03:21 PM
Do you really think he gets a worth to mention amount of money right now? I think he does not care about money here, more about ppl going on his nerves with features not working on their cheap "sd2snes"-ripoff (See? Didn't say clone that time^^) and DEMAND it to be fixed for them via all social media available. True story that is! If he really added some clone lock to specific behavior known to cause problems, he is 100% right in doing that IMO. If ppl complain about this message he can be 100% sure to not have to give a f*ck ^^ Luckily, if that's the case, ikari is far more friendly that I am, I would zero out the whole bootloader and thus brick the wannabe sd2snes.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 03, 2019, 07:00 PM
when sd3snes launches, im sure it wont be so open as it is now.
Which is fine with me. But if you make something open source, then stay true to your decision and make the simple argument: if you want the best version of my product with all the technical support -> buy the version manufactured by my business partner. Otherwise: no support from me since you get what you pay for.


I think he does not care about money here, more about ppl going on his nerves with features not working on their cheap "sd2snes"-ripoff (See? Didn't say clone that time^^) and DEMAND it to be fixed for them via all social media available.
First of all: thanks for calling it 'ripoff' now - sounds WAY less bad than 'clone' ;-p .

Let me be totally honest for one second: i think ikari_01 did an amazing job in developing the SD2SNES and he deserves every penny he made out if it via the official built. That's why i supported him too, by buying my SD2SNES from an official seller.
And i don't believe he was thinking about the money he could make either, since he made his project open source. Maybe partly because he was hoping for others to jump in and help in developing and perfecting the enhancement chip cores.

That being said: nobody but Maximilian knows for sure if he regrets not making it closed source in the first place. And: only he does know, if the constant demanding was bugging him. But since some people can be a real pain in the a**, maybe that was the case. But it never was and still isn't his job to fulfill those demands since those people bought a finished product for which the seller(!) has to provide technical support. And if the seller can't or won't do that (which may be the case for most - if not all - of the Chinese sellers) you are screwed as a buyer. Simple as that. But implementing a 'clone check' sends the wrong message... but i'm getting ahead of myself.


If he really added some clone lock to specific behavior known to cause problems, he is 100% right in doing that IMO. If ppl complain about this message he can be 100% sure to not have to give a f*ck ^^ Luckily, if that's the case, ikari is far more friendly that I am, I would zero out the whole bootloader and thus brick the wannabe sd2snes.
He may have the right to do it (if he did it at all) - but (as i said): it sends a very wrong message to the open source community IMHO.
Think about it in a grander scale: there may be hundreds of open source FPGA hardware projects out there. What if EVERY SINGLE inital developer of those projects starts to implement a lock into his precompiled firmware, which looks for a built not manufactured by his preferred or recommended partner/seller??? Don't you think it wouldn't be fair? It's like saying:

"Here... i developed this. For you. For the public. For everyone to enjoy... and to develop it any further. For... whoooops - changed my mind. It's just for the 'elite' buyers now (or for people smart enough to build their own firmware without any lock). Nevermind. No hard feelings."

Or simply think about it that way:
For such projects like the SD2SNES most of the users seem to demand more and better features again and again. So: what about the smart folks out there, who are skilled enough to be very helpful in the further development of the software of such an open source project... but simply can't afford to buy the open source hardware from an official partner of the developer? To lock them out seems kind of wrong to me as well as counterproductive. It's open source! So what's the point in making the plans of your brainchild publicly available and everything recreatable, if you exclude parts of the public and highly restrict the ability to recreate it???

And that's why i don't get people saying things like "I would punish those 'clone' buyers even more". Cause it always sounds to me like "I paid a LOT of money for this thing - so i'm part of a small and elite group of people owning this. People who bought it cheap are NOT part of this group. I'm better than those people" - which is justified to think about closed source hardware and buyers of clones of such hardware. But for open source hardware it seems kind of against the open source thinking and spirit.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 03, 2019, 07:04 PM
Well, ikari fixed many of the issues that were in my "ripoff" sd2snes... and I'm sure that many of them have been used for the s-dd1 support accuracy for ALL cards...

So that ripoff carts helped to have a better s-dd1 support.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Sarge on January 03, 2019, 08:41 PM
If anything, the SD2SNES and its recent improvements make the argument that the EverDrive firmware should also go open source.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: dreimer on January 03, 2019, 09:22 PM
Well regarding that... I would like to see it open sourced. You were able to see last year what could happen when a few skilled ppl start to add stuff. Hello, SDD-1, hello SA-1 and HELLO Mario Chip aka FX and all the other great fixed stuff for 1Chip etc!! Not gonna happen for the Super Everdrive because it has not the FPGA power for that, but some stuff is there to be modified or optimized and that is true for any of the Everdrive carts.
Anyways... I think this goes a bit off topic.
Regarding the cart with some defect or lock: I never tinkered with my sd2snes 's JTAG port but this could be the way to go. No clue if anyone here ever used it and can help there. I can't and thus won't. Even if it would be a real one in that case.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Jdurg on January 03, 2019, 10:36 PM
To be honest, if the Everdrive OS for all Everdrives was made open source, that may be a good thing.  Krikzz is far more brilliant than I am, but when you constantly hear about random errors/crashes/freezes/SD Card issues, it makes me wonder if he has some shortcomings in coding the OS with regards to reads/writes from the SD card.  (As it seems that is where the bulk of the issues are coming from).  May be a better option for all if the code was open source so others could fix the issues that are being found, but for which Krikzz just doesn't have the hardware needed to troubleshoot it.

With regards to the open source debate and clone SD2SNES carts, my feeling is that for open source projects the end-user should go to where they got the product for support.  These forums here are really for those who paid the extra money to get one from the official sellers.  So while it might suck if someone can't afford to get an "official" cart, my apologies.  Not being able to afford stuff sucks.

Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 05, 2019, 06:32 AM
Honestly, i know there is always a debate.  While i just not wish to trigger anybody to feel bad in these.

I am just a general public and when i first buying a lower priced sd2snes from some "not official" sellers, i know very little and i think that is not surprised in many people's thought.  Sure now I learnt a lesson and this is no correct/incorrect in my judgement yet, I just knew the atmosphere now.

by the way, I also real support the official ones and so i bought one as well.

So, I think i am sure just to seek for some Help/ the help is, I just wish to make clarify for :

1. MY 1st sd2snes card (not so call official one) is having perfect sd2 diagnose test result (refer bottom)
2. If it is checked as passing all test results, so i think it shall be a quality-proved and it shall not have failure in hardware,
3. It is started from 0.16 firmware , all firmware running perfect til 1.8.  and no more upgrade or downgrade allow suddenly.
4. It say "flash check error(clone)" message and querying it be clone.  I just want to know if that is a solid problem found, e.g. memory speed error? ic problems? etc, if then, the test shall not saying okay, right?
5. Otherwise, if that is really a NEED to check "non-offical" hardware , i just hope to have a know. (while I understand this is probably to get)
6. See, I saw many other so called Clone or unoffical hardware in this open source item is still selling, it is sure right for any supporting or failure shall back to the seller directly.  However, the problem is, they all can use 1.9 firmware, but why some card just being checked and saying clone and some others still survive ? My card is checked test okay, but it locked me since 1.8.   I just wish I can take my own risk to bear any quality issues in case happened, I will not challenge any issues here, but I really not wishing the card being proactively locked without strong reason. 
7.if that is just developer's wish to isolated these hardware, definitely can.  But i still not wishing to seeing just by decision instead of real quality check problems.  My card is from China seller, yes, but they may not have intention to letting buying suffer as well. ( Honestly, those sellers also allow for repairing in case of card hardware issues.) 

I know total thing is debatable, I not wish to make all of  us fans of sd2snes being down, I just sincerely wishing to seek for some help for if there is some possible to let the rom being fresh cleared and be new, at least no locking at a specific firmware .  My card pass all test, so i dun think it is " quality problem"  ,  except there is hidden agenda from developer's view, then i am humble to learn it.

If no one can help, i still enjoying my another official card which is using 1.9 so far happily. thanks.

Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 05, 2019, 05:47 PM
@mancyrix
There is probably NO EASY solution. You may have to (re)program the bootloader - which is described here:

https://github.com/mrehkopf/sd2snes/tree/develop/src

Quote
2) Building & programming the bootloader
The Makefile is prepared for JTAG programming using OpenOCD 0.4 and an FT2232
based USB-JTAG adapter.
Connect a JTAG cable to J401 (14-pin header). The pinout is printed on the
board. cd to src/bootldr and make && make program.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 05, 2019, 11:54 PM
I think that that word "clone" is refering to the main processor, not the card.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 06, 2019, 07:19 AM
Thanks Tomkeller,
it sure cannot be easily handled by me..........poor.

Anyway thanks for giving me insights.
also, just curious, why can it be easily firmware upgaded to the 1.8 firmware (with locked status now. i think), but cannot just flash to other ones............-_- :'(


@mancyrix
There is probably NO EASY solution. You may have to (re)program the bootloader - which is described here:

https://github.com/mrehkopf/sd2snes/tree/develop/src

Quote
2) Building & programming the bootloader
The Makefile is prepared for JTAG programming using OpenOCD 0.4 and an FT2232
based USB-JTAG adapter.
Connect a JTAG cable to J401 (14-pin header). The pinout is printed on the
board. cd to src/bootldr and make && make program.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 06, 2019, 10:28 AM
Normally the bootloader tells the SD2SNES to load the firmware from the sd card. It's not permanently flashed intro the card itself - that's why in the past you could change the firmware by replacing the firmware files on the sd card.

I assume: the 1.8 firmware somehow changed the bootloader and flashed the firmware somewhere onto the cart itself (probably just the main core, while the cores of the enhancement chips are still loaded from the sd card!?). So the new bootloader doesn't load the firmware from the sd card anymore, but instead loads it from the cart itself. That's why you stuck with 1.8.

But those are just assumptions since i don't know any of it for sure...
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: FeverDrive on January 06, 2019, 09:34 PM
but still boot sucess and load games normal, can play fx games.

Please correct me if I'm wrong but this is not a "lock", this is only a warning about the manufacturing of this particular SD2SNES.

This is GOOD, it's good to identify the poorly manufactured SD2SNESes out there so you can ask for support/help to the corresponding parties. And also to know that sometimes the problems don't come from firmware but from crap chinese manufacturing. Also it means you have to sell this chinese made SD2SNES at a fair price.

This warning is a problem in the case you want to sell this SD2SNES passing it as a Krikzz manufactured one, and I assume you don't want to do this, right?  ;) ;)
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 06, 2019, 11:52 PM
It's not just the message - he can't upgrade (or even downgrade) his firmware:

I have tried upgrade to 1.9.0, but it have no any result and still boot with same message “flash check error (clone?)” , and info show is still 1.8.0 firmware.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Richardragon87 on January 10, 2019, 06:42 AM
but still boot sucess and load games normal, can play fx games.

Please correct me if I'm wrong but this is not a "lock", this is only a warning about the manufacturing of this particular SD2SNES.

This is GOOD, it's good to identify the poorly manufactured SD2SNESes out there so you can ask for support/help to the corresponding parties. And also to know that sometimes the problems don't come from firmware but from crap chinese manufacturing. Also it means you have to sell this chinese made SD2SNES at a fair price.

This warning is a problem in the case you want to sell this SD2SNES passing it as a Krikzz manufactured one, and I assume you don't want to do this, right?  ;) ;)

That is a good point but what if the actual manufacturers are worse than the Chinese ones? Take Retrotowers for example I have had nothing but frustration with their methods for years now and nothing has ever good has come from it. They were one of the most rushed quanity over quality makers I have ever come across and have not ruined just 1 but 2 of my physical orders I got from them.

The first is their attempt at the SD2 SNES I can first hand say they cannot even take time to put it together right as you see in the imgur link below...

https://imgur.com/a/NnivhjG

But however it gets much... much worse when they made my X5 GBA Everdrive. They firstly sent it to me with a really dodgy spring it was so dodgy that it eventually wouldn't stop springing the SD card out so I sent it back and they fixed it but did the back of my shell in I really cannot explain this result in words so make it out for yourself on what you think...

https://imgur.com/a/5iUPXh7

I can say they tightened the screws so tight that it was cracking the inner shell of the back so I had to loosen it as there was no space for it to breath for the bottom having a bit of breathing space where both parts of the plastic before the chip at the bottom is slotted into the GBA itself.

It kind of makes me glad I got the Chinese SD2 SNES and have used it for over 3 years to what I was given from them. It's a scary warning about it bricking the fake SD2 SNES so I likely won't attempt to go past 1.7.0 I think it has the required SA1, SDD1 implementation added via the recent updates and I am happy with it.

Though it's a shame this was added as I intended to use my Retro Towers one for the MSU1 CD quality feature and the Chinese one for all the other updates as you know it has no MSU1 inserted inside it.

I can also say as an official PAL gamer there is no such thing as SNES games running at 60HZ unless you have a dip switch or something that changes the CIC settings of the Super Nintendo.  I know for sure my games always ran at 50HZ and have never gone full screen.

(Okay I probably got that last one mixed up xDD)

I kind of like the idea of SNES games being widescreen as it looks good on TV's of that type these days but that's just me everyone is different on preferences and likes and the such.

And there's my 10 cents on this post.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 10, 2019, 06:59 PM
but still boot sucess and load games normal, can play fx games.


It kind of makes me glad I got the Chinese SD2 SNES and have used it for over 3 years to what I was given from them. It's a scary warning about it bricking the fake SD2 SNES so I likely won't attempt to go past 1.7.0 I think it has the required SA1, SDD1 implementation added via the recent updates and I am happy with it.



yup, take my case as an example, it is now being hard locked (or bricked) as v1.8 and no allow to up/downgrade,
....... if no solution , you shall consider before flashing v1.8 or up. ( i dunno if you direct upgrade to v1.9 will it have such lock..)
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 10, 2019, 07:04 PM
but still boot sucess and load games normal, can play fx games.

Please correct me if I'm wrong but this is not a "lock", this is only a warning about the manufacturing of this particular SD2SNES.

This is GOOD, it's good to identify the poorly manufactured SD2SNESes out there so you can ask for support/help to the corresponding parties. And also to know that sometimes the problems don't come from firmware but from crap chinese manufacturing. Also it means you have to sell this chinese made SD2SNES at a fair price.

This warning is a problem in the case you want to sell this SD2SNES passing it as a Krikzz manufactured one, and I assume you don't want to do this, right?  ;) ;)



unfortunately,  it not just a warning but is actually not allow the card being firmware upgrade/downgrade anymore since it up to v1.8 and having some "detection" of so-called clone card.
I still feel unwell for a card with diagnose test 100% perfect but being locked in this way with no absolute quality issues, and is a open source project based too.

  but , if that is developer's intention, who can say more,........?

again, anyway i still paid more to another official one as mentioned....I think i have a say on my feeling, hopefully have some luck on any help....
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Richardragon87 on January 10, 2019, 08:17 PM
but still boot sucess and load games normal, can play fx games.

Please correct me if I'm wrong but this is not a "lock", this is only a warning about the manufacturing of this particular SD2SNES.

This is GOOD, it's good to identify the poorly manufactured SD2SNESes out there so you can ask for support/help to the corresponding parties. And also to know that sometimes the problems don't come from firmware but from crap chinese manufacturing. Also it means you have to sell this chinese made SD2SNES at a fair price.

This warning is a problem in the case you want to sell this SD2SNES passing it as a Krikzz manufactured one, and I assume you don't want to do this, right?  ;) ;)



unfortunately,  it not just a warning but is actually not allow the card being firmware upgrade/downgrade anymore since it up to v1.8 and having some "detection" of so-called clone card.
I still feel unwell for a card with diagnose test 100% perfect but being locked in this way with no absolute quality issues, and is a open source project based too.

  but , if that is developer's intention, who can say more,........?

again, anyway i still paid more to another official one as mentioned....I think i have a say on my feeling, hopefully have some luck on any help....


A problem is this issue happened a few threads back on another page of this forum and it was clearly 1.8.0 that did it. I thankfully do not copy the entire directory from every update and just the important parts to keep the SD2SNES running.

I do recall when I updated a while ago without copying the entire updated folder the menu became garbled but after adding the entire directory copying it across everything went back to normal on it.

It was first noticed on October 8th 2018 - http://krikzz.com/forum/index.php?topic=8227.0

Edit: I just noticed mine is indeed 1.8.0 but its got around the issue maybe because I mix stuff up and things?
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 10, 2019, 08:29 PM
I don't know for sure, but it seems like this "flash check error" message only happens with the older Chinese builds of the Rev. E1 pcb (there was a problem with a bootloader bug with those too, i think). Newer Chinese ones are most of the time - but not always - Rev. F (since it is the last available Revision on the GitHub of ikari_01). So newer ones probably(!) aren't affected by this...

EDIT: Forget what i said - just saw in here (http://krikzz.com/forum/index.php?topic=8227.0), newer revisions are affected as well.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 10, 2019, 11:48 PM
Mine's is E1 and it's fully working.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Richardragon87 on January 11, 2019, 12:27 AM
I don't know for sure, but it seems like this "flash check error" message only happens with the older Chinese builds of the Rev. E1 pcb (there was a problem with a bootloader bug with those too, i think). Newer Chinese ones are most of the time - but not always - Rev. F (since it is the last available Revision on the GitHub of ikari_01). So newer ones probably(!) aren't affected by this...

EDIT: Forget what i said - just saw in here (http://krikzz.com/forum/index.php?topic=8227.0), newer revisions are affected as well.

Guess I was just lucky... I guess?

https://imgur.com/a/qVS7s4v
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 11, 2019, 04:16 AM
Seems like some Chinese versions do work with the 1.8.0 firmware without any problems... and others won't. You'll have to admit: it's really strange.

I just remembered vaguely reading a post from ikari_01 a while ago, talking about a buggy bootloader in some Rev. E1 SD2SNES from China - so i thought it could be a hint on what revisions may be affected. But now there seems to be no pattern...
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Richardragon87 on January 11, 2019, 05:24 AM
Seems like some Chinese versions do work with the 1.8.0 firmware without any problems... and others won't. You'll have to admit: it's really strange.

I just remembered vaguely reading a post from ikari_01 a while ago, talking about a buggy bootloader in some Rev. E1 SD2SNES from China - so i thought it could be a hint on what revisions may be affected. But now there seems to be no pattern...

I am certain my SD2SNES is a really old rev, it was likely that I don't copy the entire directory and just randomly take parts here and there that come out which haven't become part of the real hardware for example the 1.8.0 SDD1 mention isn't related to the official one.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 11, 2019, 10:02 PM
I don't know for sure, but it seems like this "flash check error" message only happens with the older Chinese builds of the Rev. E1 pcb (there was a problem with a bootloader bug with those too, i think). Newer Chinese ones are most of the time - but not always - Rev. F (since it is the last available Revision on the GitHub of ikari_01). So newer ones probably(!) aren't affected by this...

EDIT: Forget what i said - just saw in here (http://krikzz.com/forum/index.php?topic=8227.0), newer revisions are affected as well.

Guess I was just lucky... I guess?

https://imgur.com/a/qVS7s4v

Me too XD

sd2snes https://imgur.com/gallery/wSz6RhI
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Richardragon87 on January 11, 2019, 10:05 PM
I don't know for sure, but it seems like this "flash check error" message only happens with the older Chinese builds of the Rev. E1 pcb (there was a problem with a bootloader bug with those too, i think). Newer Chinese ones are most of the time - but not always - Rev. F (since it is the last available Revision on the GitHub of ikari_01). So newer ones probably(!) aren't affected by this...

EDIT: Forget what i said - just saw in here (http://krikzz.com/forum/index.php?topic=8227.0), newer revisions are affected as well.

Guess I was just lucky... I guess?

https://imgur.com/a/qVS7s4v

Me too XD

https://imgur.com/gallery/Sk9xnPw

Sweet ^^ Also did the unacessable to public 1.10.1 release include the SDD1 implementation?
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 11, 2019, 10:22 PM
Yes.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 12, 2019, 06:30 AM
I don't know for sure, but it seems like this "flash check error" message only happens with the older Chinese builds of the Rev. E1 pcb (there was a problem with a bootloader bug with those too, i think). Newer Chinese ones are most of the time - but not always - Rev. F (since it is the last available Revision on the GitHub of ikari_01). So newer ones probably(!) aren't affected by this...

EDIT: Forget what i said - just saw in here (http://krikzz.com/forum/index.php?topic=8227.0), newer revisions are affected as well.

Guess I was just lucky... I guess?

https://imgur.com/a/qVS7s4v



poor,but my card still no good result.  no matter what firmware/sd card put,  the sd2snes card will boot with that messages and hence no update any firmware.
so i think the card been locked when it say detected as clone.  now 1.8 cannot up/down firmware
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 12, 2019, 06:46 AM
if I was alerted for this, i believe i would not upgrade the card to v.18 , i never expected a result of being unable to downgrade.
At least if a way to revert back , or if the firmware update logs informing this then we are well deserved.
Especially an open project debatable items, i dun know if it is a right for a developer making those other manufacturer's card locked in this way.

anyway.  I just hope to see if any revert-able way, (besides jtag method)
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 12, 2019, 12:10 PM
Just out of curiousity: what happens when you're trying to start your SD2SNES without any firmware on your sd card @mancyrix?
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 12, 2019, 06:46 PM
Just out of curiousity: what happens when you're trying to start your SD2SNES without any firmware on your sd card @mancyrix?


you got the point,

same......message appeared

........that means that check is injected into my board now.......and so, it detects somethings and it not allow any sdcard firmware update.. ......

i wonder if any method can force the card to update firmware .........-_-
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 12, 2019, 07:10 PM
Probably: none. It's like locking the door to a room and casting the keyhole with concrete afterwards... so you can't unlock the door. The only way to access the room would be via the window (which is the JTAG method) or by removing/replacing the whole door (which in this case means: replacing the FPGA - but you'll have to programm the bootloader in this case too).

But it's still a mystery to me, where inside the SD2SNES the whole 1.8.0 firmware was permanently flashed to - into the FPGAs own flash memory? Would it be big enough?
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 12, 2019, 11:56 PM
You can remove the firmware.img file once you flashed the new firmware, so yes, firmware is stored in the flash chip.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 13, 2019, 06:17 AM
actually i have test all kinds of firmware to put into sdcard, but no one will make diff,

becos, the thing now seems is,  even I not putting sdcard into board, the sfc boot up, and then that message must shown at first, saying "flash check error (clone?)"  , and if have sdcard with any firmware,  the result is just boot into main menu, and checked sys info, showing v1.8 only.  no matter i put 1.9, or some unofficial firmware e.g. 1.8/1.9 with sdd, etc..

seems is, firmware 1.8 already flashed into chips and as that firmware monitored hardware in a certain checks before it allow to flash the firmware from Sd card...

so i wonder , if then my card already no way to escape from v1.8....by soft method.  As i think jtag method is not possible at my side.

i really wish i have not flashed this v1.8 which silently adding such check without any pre-caution.  even i believe possible is developer's though is to ruin those"unofficial" sd2snes card, ........in this open source project.......

i just wish, if there is any secret method which can force to skip such check and allow to reflash the firmware .  personally, I can accept a warning shown for claiming the possible for such non offical cards quality issues (even diagnose test is perfect result tho...),  it shall still allow the user to change firmware, at least downgrade..... to escape from forcing a specific firmware version with no warning and choice.

I really not professional about open source meaning, but normal public not expect in this way i believe.

(anyway,  again,
just to remark: i own my another offical sd2snes card.....i appreciate this whole project and products)
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 13, 2019, 11:23 AM
Have you tried to flash the diagnostics firmware?

https://sd2snes.de/blog/cool-stuff/sd2snes-diagnostics
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 13, 2019, 08:39 PM
Have you tried to flash the diagnostics firmware?

https://sd2snes.de/blog/cool-stuff/sd2snes-diagnostics
as mentioned before,

I have even used the diagnose tools and all test are 100% correct



===log opened===
derp
SD test... please insert card
=============================
crc1 = d805a1bf crc2 = d805a1bf   PASSED


RTC Test
========
setting clock to 2011-01-01 00:00:00
waiting 5 seconds
new time: PASSED


CIC Test:
=========
Current CIC state: CIC_OK
CIC reports OK; no pair mode available. Provoking CIC error...
new CIC state: CIC_FAIL
***Please reset SNES***
PASSED


FPGA test
=========
configuring fpga...
fpga_pgm: 212501 bytes programmed
FPGA configured
basic communication test...PASSED


RAM test
========
Testing RAM0 (128Mbit) - clearing RAM - writing RAM - verifying RAM -RAM0 PASSED


Testing RAM1 (4Mbit) - writing RAM - verifying RAM...RAM1 PASSED


SD DMA test
===========
clearing RAM - loading test file - verifying -PASSED


Loading SNES test ROM
=====================



sysclk test
===========
measuring SNES clock...
21480677 Hz
21480677 Hz diff = 0  max = 0
21480677 Hz diff = 0  max = 0
21480677 Hz diff = 0  max = 0
   CPUCLK: 3420828
  READCLK: 3095033
 WRITECLK: 162897
  PARDCLK: 162896
  PAWRCLK: 162897
  REFRCLK: 78740
ROMSELCLK: 488689
PASSED


SNES test status: IRQ: 00   PA: 00   MEM: 00/00
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/00
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/01
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/02
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/03
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/04
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/05
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/06
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/07
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/08
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/09
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/0a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/0b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/0c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/0d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/0e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/0f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/10
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/11
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/12
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/13
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/14
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/15
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/16
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/17
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/18
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/19
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/1a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/1b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/1c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/1d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/1e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/1f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/20
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/21
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/22
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/23
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/24
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/25
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/26
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/27
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/28
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/29
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/2a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/2b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/2c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/2d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/2e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/2f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/30
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/31
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/32
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/33
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/34
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/35
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/36
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/37
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/38
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/39
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/3a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/3b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/3c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/3d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/3e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/3f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/40
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/41
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/42
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/43
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/44
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/45
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/46
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/47
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/48
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/49
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/4a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/4b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/4c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/4d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/4e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/4f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/50
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/51
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/52
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/53
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/54
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/55
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/56
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/57
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/58
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/59
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/5a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/5b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/5c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/5d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/5e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/5f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/60
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/61
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/62
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/63
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/64
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/65
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/66
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/67
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/68
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/69
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/6a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/6b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/6c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/6d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/6e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/6f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/70
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/71
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/72
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/73
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/74
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/75
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/76
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/77
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/78
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/79
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/7a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/7b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/7c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/7d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/7e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/81
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/82
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/83
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/84
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/85
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/86
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/87
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/88
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/89
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/8a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/8b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/8c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/8d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/8e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/8f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/90
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/91
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/92
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/93
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/94
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/95
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/96
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/97
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/98
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/99
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/9a
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/9b
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/9c
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/9d
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/9e
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/9f
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a0
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a1
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a2
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a3
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a4
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a6
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a7
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a8
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/a9
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/aa
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ab
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ac
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ad
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ae
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/af
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b0
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b1
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b2
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b3
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b4
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b6
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b7
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b8
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/b9
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ba
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/bb
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/bc
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/bd
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/be
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/bf
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c0
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c1
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c2
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c3
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c4
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c6
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c7
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c8
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/c9
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ca
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/cb
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/cc
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/cd
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ce
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/cf
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d0
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d1
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d2
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d3
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d4
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d6
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d7
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d8
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/d9
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/da
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/db
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/dc
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/dd
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/de
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/df
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e0
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e1
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e2
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e3
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e4
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e6
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e7
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e8
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/e9
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ea
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/eb
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ec
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ed
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ee
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ef
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f0
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f1
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f2
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f3
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f4
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f5
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f6
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f7
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f8
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/f9
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/fa
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/fb
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/fc
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/fd
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/fe
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/ff
SNES test status: IRQ: 5a   PA: 5a   MEM: 00/00
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/00
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/01
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/02
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/03
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/04
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/05
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/06
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/07
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/08
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/09
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/0a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/0b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/0c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/0d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/0e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/0f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/10
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/11
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/12
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/13
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/14
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/15
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/16
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/17
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/18
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/19
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/1a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/1b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/1c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/1d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/1e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/1f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/20
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/21
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/22
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/23
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/24
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/25
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/26
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/27
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/28
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/29
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/2a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/2b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/2c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/2d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/2e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/2f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/30
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/31
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/32
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/33
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/34
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/35
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/36
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/37
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/38
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/39
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/3a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/3b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/3c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/3d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/3e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/3f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/40
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/41
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/42
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/43
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/44
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/45
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/46
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/47
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/48
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/49
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/4a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/4b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/4c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/4d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/4e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/4f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/50
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/51
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/52
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/53
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/54
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/55
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/56
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/57
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/58
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/59
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/5a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/5b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/5c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/5d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/5e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/5f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/60
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/61
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/62
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/63
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/64
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/65
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/66
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/67
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/68
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/69
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/6a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/6b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/6c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/6d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/6e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/6f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/70
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/71
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/72
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/73
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/74
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/75
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/76
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/77
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/78
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/79
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/7a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/7b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/7c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/7d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/7e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/81
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/82
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/83
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/84
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/85
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/86
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/87
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/88
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/89
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/8a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/8b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/8c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/8d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/8e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/8f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/90
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/91
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/92
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/93
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/94
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/95
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/96
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/97
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/98
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/99
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/9a
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/9b
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/9c
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/9d
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/9e
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/9f
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a0
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a1
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a2
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a3
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a4
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a5
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a6
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a7
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a8
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/a9
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/aa
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ab
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ac
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ad
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ae
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/af
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b0
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b1
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b2
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b3
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b4
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b5
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b6
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b7
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b8
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/b9
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ba
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/bb
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/bc
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/bd
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/be
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/bf
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c0
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c1
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c2
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c3
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c4
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c5
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c6
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c7
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c8
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/c9
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ca
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/cb
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/cc
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/cd
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ce
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/cf
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d0
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d1
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d2
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d3
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d4
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d5
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d6
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d7
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d8
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/d9
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/da
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/db
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/dc
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/dd
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/de
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/df
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e0
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e1
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e2
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e3
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e4
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e5
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e6
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e7
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e8
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/e9
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ea
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/eb
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ec
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ed
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ee
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ef
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f0
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f1
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f2
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f3
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f4
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f5
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f6
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f7
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f8
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/f9
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/fa
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/fb
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/fc
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/fd
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/fe
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/ff
SNES test status: IRQ: 5a   PA: 5a   MEM: 01/00
SNES test status: IRQ: 5a   PA: 5a   MEM: 5a/00



TEST SUMMARY
============

Test      Result
----------------
SD        Passed
USB       no run
RTC       Passed
CIC       Passed
FPGA      Passed
RAM       Passed
SD DMA    Passed
CLK       Passed
DAC       no run
SNES IRQ  Passed
SNES RAM  Passed
SNES PA   Passed
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: josete2k on January 13, 2019, 09:30 PM
Strange... The diagnostics firmware flashes your card too so if this is working for you it seems that your flash cart can e flashed.

Try to flash from 0.1.5 upwards...
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on January 13, 2019, 10:42 PM
Strange... The diagnostics firmware flashes your card too so if this is working for you it seems that your flash cart can e flashed.

Try to flash from 0.1.5 upwards...

oh, sorry, what i means is, the test i have done when I am still not yet changed to v.1.8.

while, today i retest with the diag firmware again, it is not able to start.  That still showing the flash check error (clone?) warning,
and then say no menu.bin (sure, as the test folder sd2snes does not contain it.)

so it means, now no possible to flash any firmware.......including diag firmware........

Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: FeverDrive on January 16, 2019, 06:04 AM
Well... if you could downgrade then the warning would be useless since anyone can bypass it by downgrading.
Showing the warning message and then allowing to upgrade/downgrade would make no sense.
My suggestion is to sell the product as-is since it loads the special chip games anyway.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on January 16, 2019, 05:48 PM
If it's just a warning, downgrading should be possible. But it's obviously a brick/lock... well... i already said what i had to say about that ;) .
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: lordoftime79 on February 06, 2019, 01:06 PM
FPGA by the very nature are programmable hence the 'P' in FPGA - so in theory this should be fixable, I come from the Amiga community and we have something called a Vampire cpu card - it too is FPGA based and as its still in development all people who purchase one are told they should also purchase a USB blaster to reflash FPGA on our Vampire card. mainly due to it being beta it often screws up... could this same device not be used to save this SD2SNES? the files to reflash should be available due to it being open source and a USB blaster is like 5 quid on ebay. I have took my SD2SNES out of its shell and it looks like it has points on the pcb for a JTAG progammer.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on February 08, 2019, 05:28 PM
Yes... it's possible to reflash the bootloader... but:
Thanks Tomkeller,
it sure cannot be easily handled by me..........poor.

Anyway thanks for giving me insights.
also, just curious, why can it be easily firmware upgaded to the 1.8 firmware (with locked status now. i think), but cannot just flash to other ones............-_- :'(


@mancyrix
There is probably NO EASY solution. You may have to (re)program the bootloader - which is described here:

https://github.com/mrehkopf/sd2snes/tree/develop/src

Quote
2) Building & programming the bootloader
The Makefile is prepared for JTAG programming using OpenOCD 0.4 and an FT2232
based USB-JTAG adapter.
Connect a JTAG cable to J401 (14-pin header). The pinout is printed on the
board. cd to src/bootldr and make && make program.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: mancyrix on February 10, 2019, 06:13 PM
without a proper simple solution at my level of technical skills, (just like normal public)
i started to think my card#1 is now certified and forever stucked at firmware 1.8. 

I think my story is a good demo for alerting public for the developer planted a lockup in firmware flash ability without a pre-alert and without a proper consent in a so-called open source project.

Although I respect our sd2snes developer, I still think such an action shall not be applied all in a sudden and it definitely punished some kinds of innocent users who not familiarized with those  sellers limited.  Still, it is not really perfect open source project style in many people's eyes.

anyway, I will certify my this card#1.  and now it is a no more up/down-gradable card forever at 1.8 before the card die.

I hope my demo case can let public awared of this , think before upgrading any unknown source cards to higher than 0.17.


I still have my sd2snes card#2 anyway.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: Richardragon87 on February 10, 2019, 10:55 PM
On a youtube video that I just saw it seems that Smokemonster mentioned there was even a scam of inserting a really old revision Chinese Super Everdrive gut into a SD2SNES shell though I haven't been able to find the article of it.

What would be weird is if they stepped up their game and it played SD2SNES supported games but if its 1.0 then it would be that old revision that had the loading bar in green like a windows computer.
Title: Re: Sd2snes firmware update issue / “flash check error (clone?)”
Post by: TomKeller on February 10, 2019, 11:13 PM
I heard him saying that too in his last SD2SNES Pro video... but never heard or read about it somewhere else. But it could easily have happened - there are lots of scammers on all of the big internet sale platforms.

But the story is definitely unrelated to the problem described in this very thread since there's no way the SD2SNES firmware would work on any Super Everdrive. Different FPGA... different design - no chance to make it work.