Hacking New Theme for EZ-Flash Omega!

Sterophonick

Stupid Retro Tech Cat
OP
Member
Joined
Jul 17, 2018
Messages
536
Trophies
0
Location
Spamton's Keygen Dungeon
Website
sterophonick.github.io
XP
1,791
Country
United States
O yea?
3b8a1c3801a37d218b6200e98c7b3f04.jpg
499587599c77ab9873c198dcd7e099f1.jpg

This is exactly what I see, too. Freshly reformatted SD card, latest version, it freezes whenever trying to do anything that requires a pogoshell plugin.

Here's an idea. Create a 64kb dummy .esv for each file you can launch with the plugins. Put these into SAVER.
Create copies of the provided file and rename them EXACTLY the same as your files.
It might also be a good idea to create a .sav file for each of your Game Boy Advance ROMs.

I do this and it's probably why I've never seen this.
The SD driver for this flashcart has some real issues that I do not have the capacity to fix.
 

Attachments

  • dummy.zip
    244 bytes · Views: 164
Last edited by Sterophonick,
  • Like
Reactions: treflip

Rocky5

Well-Known Member
Member
Joined
Aug 12, 2007
Messages
125
Trophies
0
Website
github.com
XP
896
Country
United Kingdom
Here's an idea. Create a 64kb dummy .esv for each file you can launch with the plugins. Put these into SAVER.
Create copies of the provided file and rename them EXACTLY the same as your files.
It might also be a good idea to create a .sav file for each of your Game Boy Advance ROMs.

I do this and it's probably why I've never seen this.
The SD driver for this flashcart has some real issues that I do not have the capacity to fix.
Can’t you just write a dummy file if it doesn’t exist when one of the other extensions are launched?
(Or supply one and copy it when required)

It’s a static paths and I assume you can grab the file name from the launched perimeters. (Haven’t looked yet)
 

Sterophonick

Stupid Retro Tech Cat
OP
Member
Joined
Jul 17, 2018
Messages
536
Trophies
0
Location
Spamton's Keygen Dungeon
Website
sterophonick.github.io
XP
1,791
Country
United States
Can’t you just write a dummy file if it doesn’t exist when one of the other extensions are launched?
(Or supply one and copy it when required)

It’s a static paths and I assume you can grab the file name from the launched perimeters. (Haven’t looked yet)
The SD driver for this flashcart has some real issues that I do not have the capacity to fix.

If the flashcart already has issues creating files, then I cannot work around this. Sorry dude. :/
 

nuvandibe

Active Member
Newcomer
Joined
Mar 19, 2007
Messages
38
Trophies
0
XP
457
Country
United States
I don't understand why the previous version works fine and is able to create files, while the most recent version cannot.

Edit: Even MORE confusing, the 3.32 uploaded on page 16 of this thread works, but one built from source does not.

Edit 2: 3.3, 3.31, 3.32, 3.33, 3.4 built from the code repo on Github all have the same symptom that we're complaining about recently, while 3.32 as uploaded to GBATemp has no such issue.
 
Last edited by nuvandibe,

nuvandibe

Active Member
Newcomer
Joined
Mar 19, 2007
Messages
38
Trophies
0
XP
457
Country
United States
Update v3.3:
- Made a few tweaks to the UI
- New plugin: Sharp X68000 Music (.mda)
- New plugin for JPEG images.
  • This new plugin has support for zooming in and out and can support JPEGs of up to 2000x2000.
  • The catch being that it requires a certain format(s), that being YUV411, YUV111 or YUV100.
  • A tool is included to convert these images to a proper format, use the bottom option that just says JPEG.

JPEG Instructions:
https://sterophonick.github.io/omegamanual.html#toc_43

^ The "Generating Emulator..." issue is not present on this file.

Edit: I'm beginning to suspect that this may be an issue with an updated devkitpro.
 
Last edited by nuvandibe,

nuvandibe

Active Member
Newcomer
Joined
Mar 19, 2007
Messages
38
Trophies
0
XP
457
Country
United States
Confirmed! Reverted devkitARM to devkitARM_r47 and built 3.3 from source, issue is resolved. Built 3.4 from source, issue stays resolved.

No idea how to fix it so that it runs okay with the devkitARM updates yet, though.
 

Shadow#1

Wii, 3DS Softmod & Dumpster Diving Expert
Member
Joined
Nov 21, 2005
Messages
10,786
Trophies
1
XP
6,333
Country
United States
Confirmed! Reverted devkitARM to devkitARM_r47 and built 3.3 from source, issue is resolved. Built 3.4 from source, issue stays resolved.

No idea how to fix it so that it runs okay with the devkitARM updates yet, though.

can u share that with everyone?
 

nuvandibe

Active Member
Newcomer
Joined
Mar 19, 2007
Messages
38
Trophies
0
XP
457
Country
United States

Using Windows, at least.
  1. Delete the devkitARM directory and replace it with the r47 build from 2017 (google is your friend).
  2. Run the build process again.
The .bin file generated by the r47 build (attached) does not cause any lockup when loading pogoshell plugins. My guess is that some command somewhere in the last 3 years has been depreciated and the code needs to be updated to work with the updated toolchain.

I began to suspect this was the case once I discovered that building v3.32 from source does not result in the same file as the v3.32 firmware .bin that was uploaded in this thread. The code was the same, therefore the toolchain updates must have been the problem.

Since this is essentially a fork of the official firmware, and they state outright on the official github here that they use devkitARM v47, there are only two ways around this:
  1. Continue using devkitARM versions that don't cause this bug, or
  2. Update the code yourself so that it works with the latest devkitARM
I don't know where the bug lies, in the original EZ Flash Omega kernal code, or your modified code. But the latest devkitARM does throw up a ton of warnings when compiling SimpleLight from the GitHub source.

Edit: It may be necessary to delete run 'make clean' before switching toolchain versions

Edit 2: It seems to break on line 2830 in ezkernel.c where it tries to actually reboot into the generated emulator ROM.

Edit 3: devkitARM v50-4 works but I have been unable to test V51, 52, 53
 

Attachments

  • ezkernel-dark_v3.4_devkitARM_r47.zip
    542.5 KB · Views: 201
Last edited by nuvandibe,

Shadow#1

Wii, 3DS Softmod & Dumpster Diving Expert
Member
Joined
Nov 21, 2005
Messages
10,786
Trophies
1
XP
6,333
Country
United States
Using Windows, at least.
  1. Delete the devkitARM directory and replace it with the r47 build from 2017 (google is your friend).
  2. Run the build process again.
The .bin file generated by the r47 build (attached) does not cause any lockup when loading pogoshell plugins. My guess is that some command somewhere in the last 3 years has been depreciated and the code needs to be updated to work with the updated toolchain.

I began to suspect this was the case once I discovered that building v3.32 from source does not result in the same file as the v3.32 firmware .bin that was uploaded in this thread. The code was the same, therefore the toolchain updates must have been the problem.

Since this is essentially a fork of the official firmware, and they state outright on the official github here that they use devkitARM v47, there are only two ways around this:
  1. Continue using devkitARM versions that don't cause this bug, or
  2. Update the code yourself so that it works with the latest devkitARM
I don't know where the bug lies, in the original EZ Flash Omega kernal code, or your modified code. But the latest devkitARM does throw up a ton of warnings when compiling SimpleLight from the GitHub source.

Edit: It may be necessary to delete run 'make clean' before switching toolchain versions

Edit 2: It seems to break on line 2830 in ezkernel.c where it tries to actually reboot into the generated emulator ROM.

Edit 3: devkitARM v50-4 works but I have been unable to test V51, 52, 53

Guys this works like he said should update to this build thanks
 
  • Like
Reactions: nuvandibe

Sterophonick

Stupid Retro Tech Cat
OP
Member
Joined
Jul 17, 2018
Messages
536
Trophies
0
Location
Spamton's Keygen Dungeon
Website
sterophonick.github.io
XP
1,791
Country
United States
Using Windows, at least.
  1. Delete the devkitARM directory and replace it with the r47 build from 2017 (google is your friend).
  2. Run the build process again.
The .bin file generated by the r47 build (attached) does not cause any lockup when loading pogoshell plugins. My guess is that some command somewhere in the last 3 years has been depreciated and the code needs to be updated to work with the updated toolchain.

I began to suspect this was the case once I discovered that building v3.32 from source does not result in the same file as the v3.32 firmware .bin that was uploaded in this thread. The code was the same, therefore the toolchain updates must have been the problem.

Since this is essentially a fork of the official firmware, and they state outright on the official github here that they use devkitARM v47, there are only two ways around this:
  1. Continue using devkitARM versions that don't cause this bug, or
  2. Update the code yourself so that it works with the latest devkitARM
I don't know where the bug lies, in the original EZ Flash Omega kernal code, or your modified code. But the latest devkitARM does throw up a ton of warnings when compiling SimpleLight from the GitHub source.

Edit: It may be necessary to delete run 'make clean' before switching toolchain versions

Edit 2: It seems to break on line 2830 in ezkernel.c where it tries to actually reboot into the generated emulator ROM.

Edit 3: devkitARM v50-4 works but I have been unable to test V51, 52, 53

Want to just chime in here, I updated to the latest devkitARM and compiled the source and it does what others are saying, green bar after it loads a few MBits.

Its caused by the optimisation setting in the make file, -0s breaks it, -0 doesn't.

Thankyouthankyouthankyouthankyou so much!!!
I'm going to try an optimization level of -O3 and see if that helps.
 
Last edited by Sterophonick,

IkarugaShock

Member
Newcomer
Joined
Sep 29, 2020
Messages
7
Trophies
0
Age
45
XP
21
Country
Spain
That's pretty dumb...
Anyways here it is with -O
Hello!
I am new in the forum...
You mean that it i will install the version you just uploaded there is no error of "GENERATING EMULATOR"? I installed the version 3.4 but I had this error and I tried to return to 3.2 but it didn´t downgrade muy Ezflash Omega...I had to give up and return to original kernel of the cart...
Anyone can help me please? and one more thing of is the Neogeo Pocket Color emulator? I tried it but it wasw veery slow...am I right?
Thanks so much in advance
 
  • Like
Reactions: Sterophonick

nuvandibe

Active Member
Newcomer
Joined
Mar 19, 2007
Messages
38
Trophies
0
XP
457
Country
United States
That's pretty dumb...
Anyways here it is with -O

Testing.... anddddddd............ IT WORKS! Time to commit a github change, methinks.

--------------------- MERGED ---------------------------

Hello!
I am new in the forum...
You mean that it i will install the version you just uploaded there is no error of "GENERATING EMULATOR"? I installed the version 3.4 but I had this error and I tried to return to 3.2 but it didn´t downgrade muy Ezflash Omega...I had to give up and return to original kernel of the cart...
Anyone can help me please? and one more thing of is the Neogeo Pocket Color emulator? I tried it but it wasw veery slow...am I right?
Thanks so much in advance

Yes, that build seems to have resolved the "Generating Emulator" bug.
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    KennieDaMeanie @ KennieDaMeanie: https://youtube.com/shorts/mGy-gUnBeQc?feature=share