#1  
Old 21st April 2013, 11:52 AM
Nekokabu Nekokabu is offline
Alpha Tester
Project Supporter
Junior Member
 
Join Date: Nov 2005
Posts: 13
Default Initializing EEPROM

For the initial value of the EEPROM is 0, Heiwa Pachinko World 64 (J) does not correctly recognize the save data. (*It will recognize that there is a save data of 0 the value of all.)



When it is save data that has been initialized by 0xFF, resulting in will be recognized correctly.
Attached Images
File Type: jpg heiwa1.jpg (60.9 KB, 57 views)
File Type: jpg heiwa3.jpg (63.1 KB, 55 views)

Last edited by Nekokabu; 21st April 2013 at 11:55 AM.
Reply With Quote
  #2  
Old 21st April 2013, 06:20 PM
zilmar zilmar is offline
Core Team
Alpha Tester
Project Supporter
Administrator
 
Join Date: Jun 2005
Posts: 989
Default

good suggestion, I will try to add it in soon
Reply With Quote
  #3  
Old 8th May 2013, 03:56 PM
Nekokabu Nekokabu is offline
Alpha Tester
Project Supporter
Junior Member
 
Join Date: Nov 2005
Posts: 13
Default

THank you, zilmar I looks like it was fixed.
but there is a place that initializes m_EEPROM in LoadEeprom().
I think it is better to fix here too is good.
Reply With Quote
  #4  
Old 15th June 2013, 12:20 PM
Nekokabu Nekokabu is offline
Alpha Tester
Project Supporter
Junior Member
 
Join Date: Nov 2005
Posts: 13
Default

If the save file not exists, problems occur.

I found a bug in the Custom Robo V2.

PJ64 v2.1: not exist save file.


my eeprom fixed build
Attached Images
File Type: jpg robov2.jpg (59.5 KB, 23 views)
File Type: jpg robov2_pj64v21.jpg (55.9 KB, 23 views)
Reply With Quote
  #5  
Old 16th June 2013, 09:51 AM
zilmar zilmar is offline
Core Team
Alpha Tester
Project Supporter
Administrator
 
Join Date: Jun 2005
Posts: 989
Default

ok, what are your changes.
Reply With Quote
  #6  
Old 16th June 2013, 02:01 PM
Nekokabu Nekokabu is offline
Alpha Tester
Project Supporter
Junior Member
 
Join Date: Nov 2005
Posts: 13
Default

It is where initializing the m_EEPROM in Load Eeprom() function.

- memset(m_EEPROM,0,sizeof(m_EEPROM));
+ memset(m_EEPROM,0xFF,sizeof(m_EEPROM));
Reply With Quote
  #7  
Old 16th June 2013, 02:41 PM
HatCat's Avatar
HatCat HatCat is offline
Alpha Tester
Project Supporter
Senior Member
 
Join Date: Feb 2007
Location: In my hat.
Posts: 16,236
Default

Is this the way real N64 writes null bytes for EEPROM backups?

Do empty bytes saved as 0xFF

If so, it seems to be identical to FLASHRAM save format, which I am pretty sure also writes 0xFF for blank/null data.

Would this fix the unpopular Virtual Chess 64 issue where no emulators ever generate an EEPROM for it like the actual N64 I am pretty sure does?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT. The time now is 06:27 AM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.