What is format of EEPROM data file?

I am very much new in this field.
I am doing some project on Atmega 328p. I have to load EEPROM data for simulation, but I do not know the format of the files.
i.e.
.bin File Data Format
.data File Data Format

Would you please clarify the issue about the different formats?

Thanks and regards.

A few months ago when trying  Ram/Rom Memory component I came across this same confusion when I had to upload some microcode for a TTL-Cpu.

Data files can be created when you right click on the R/R component and click Save Data. It will be stored as a .data file.
If you want a file from somewhere else they are sometimes called .bin or .rom but I used a couple of them and the file extension name does not seem to make much difference wether it is .bin or .data or .rom.
Notepad++ is handy to see (and change) what is inside a file or use Memory Table in Simulide 0.4.15

On a microcontroller I have not tried Load/Save Eeprom Data yet.
Arcachofo will know a lot more about it than me.

By the way, if you want to program your uC you need to click Load Firmware and navigate to the hex-file that was generated after building/compiling/verifying your program code. Probably that is not the problem but I mention it anyway.

expertpk wrote:I am very much new in this field.
I am doing some project on Atmega 328p. I have to load EEPROM data for simulation, but I do not know the format of the files.
i.e.
.bin File Data Format
.data File Data Format

Would you please clarify the issue about the different formats?

Thanks and regards.

.data is a text format readable in any text editor, just a list of values separated by commas.

.bin is binary format.

When you load a file it will be considered comma-separated text format if the extension is .data, for any other extension it will be considered binary.

I have to load EEPROM data for simulation

Do you already have a file?

Yes.
I have a file with .eep extension, produced through Atmel Studio.
How I can convert to .bin or .data format to simulate in SimuliIDE.
Please suggest.
Thanks

And if possible, please tell me how to convert .eep file into .bin file?

Thanks once again

Have you tried to just load it?

Yes I loaded it, but cant get data from EEPROM.
It is in Intel Hex format.
Can Intel Hex format runs on simulation in SimuliIDE?
OR I have to convert it into .data format or .bin format?

It is in Intel Hex format.

Ah ok.
By now there is no way to load ihex files into memories in simulide.
I think I will add this feature in the future.

But you can convert that .eep file to .bin and load that .bin file to AVR EEEPROM.
There are many ways to do this.
If you have the avr-objcopy executable it can be used like this:

avr-objcopy -I ihex file.eep -O binary file.bin

You can find avr-objcopy in Arduino:
arduino-x.x.x/hardware/tools/avr/bin

If you use Windows execute like this:
"C:\...\...\arduino-x.x.x\hardware\tools\avr\bin\avr-objcopy.exe" -I ihex file.eep -O binary file.bin

I forgot to mention:

You can load EEPROM data from an .elf file.
If you have the .elf file corresponding to that .eep file, then it should contain eeprom data.
You can load an .elf file with "Load Firmware" the same way you load an .hex file to flash.

I tried that, but unable to lead the .bin file too.
I am attaching both the files here. That is .eep and .bin created by objcopy method.
Please have a look and suggest.

:10000000496473733D00206574613D00554A540096
:1000100050555400310803083320342D33306E46D8
:10002000284C29005245465F523D005245465F43E9
:100030003D00203E3130306E460066706E056D002A
:100040006B4D00111111131D101000000E11110A3B
:100050001B00041F111111111F04001E0203021EB8
:100060000000000F0818080F00001113171F1713C6
:10007000110011191D1F1D1911001B1B1B1B1B1B20
:100080001B005244533D005B435D003108030833BD
:1000900020003108070608090A08332000432B45D1
:1000A0005352405450313A3300664054503200208D
:1000B0003530487A00433073616D70200043302042
:1000C0000052695F4C6F3D0052695F48693D0052C4
:1000D000303D0052482F524C002B52482D203132D7
:1000E000203133203233002B524C2D20313220313D
:1000F000332032330052482B0052482D00524866BC
:100100003D005265663D00494345733D0049434506
:10011000303D00436F6D706F6E656E742054657373
:100120007465720008090A080008070608002A0119
:100130002020007A20513D002069662000204030B8
:100140002D355600080208000801080049723D00DC
:100150004C3D0020566C6F73733D00204553523D5B
:10016000005643433D0043656C6C210008030800C2
:100170004056673D002056743D0055663D0055626F
:10018000653D00203132333D0050696E2000424A07
:10019000542D504E5000424A542D4E504E00433D77
:1001A0000043673D006846453D002D4947425400E5
:1001B0004A464554002D4D4F53004443205077721A
:1001C000204D6F6465004F4B004261742E20004348
:1001D0006F6E7472617374004672657175656E63DB
:1001E000790073686F72742050726F6265732100BA
:1001F00053656C6674657374007475726E21004388
:10020000280546292D636F7272656374696F6E00ED
:1002100031302D6269742050574D00662D47656E50
:10022000657261746F7200537769746368206F66DA
:10023000660053686F77206461746100566F6C7458
:10024000616765005472616E736973746F720053F5
:10025000656C656374696F6E3A005465737420450C
:100260006E640069736F6C6174652050726F6265B3
:1002700073210053656C6674657374206D6F6465DB
:100280002E2E0054696D656F7574210020646574AD
:100290006563746564004E6F2C20756E6B6E6F77AE
:1002A0006E2C206F720020756E6B6E6F776E00542F
:1002B0006879726973742E005472696163007061A9
:1002C00072740064616D616765642000656D7074AF
:1002D0007921007765616B0054657374696E672ED0
:1002E00000705780508D4A6645E340E83C5E3933E4
:1002F000365A33C6306D2E492C532A8428DA264EBE
:1003000025DF2389224A212020081F011E091D20E4
:100310001C431B731AAD19F1183F189517F4165AA0
:1003200016C6153A15B3143214B7134013CE126122
:1003300012F81193113111D3107810FF1414141402
:10034000002F072F072F072F072F072F072F072F04
:10035000072F072F072F072F072F072F0739393BA5
:100360003B3B39390C00032020202020205B524CDD
:040370005D0078466E
:00000001FF

Idss= eta= UJT PUT 13 4-30nF(L) REF_R= REF_C= >100nF fpnm kM
RDS= [C] 13 1
3 C+ESR@TP1:3 f@TP2 50Hz C0samp C0 Ri_Lo= Ri_Hi= R0= RH/RL +RH- 12 13 23 +RL- 12 13 23 RH+ RH- RHf= Ref= ICEs= ICE0= Component Tester
* z Q= if @0-5V Ir= L= Vloss= ESR= VCC= Cell! @Vg= Vt= Uf= Ube= 123= Pin BJT-PNP BJT-NPN C= Cg= hFE= -IGBT JFET -MOS DC Pwr Mode OK Bat. Contrast Frequency short Probes! Selftest turn! C(F)-correction 10-bit PWM f-Generator Switch off Show data Voltage Transistor Selection: Test End isolate Probes! Selftest mode.. Timeout! detected No, unknown, or unknown Thyrist. Triac part damaged empty! weak Testing. pW€PJfEã@è<^936Z3Æ0m.I,S*„(Ú&N%ß#‰"J! Cs­ñ?•ôZÆ:³2·@Îaø“1Óxÿ //////////////99;;;99 [RL] xF

That bin file looks good.

But there is a bug when loading eeprom data to MCU: data don't get actually written to eeprom.
This problem is solved in 0.4.15 branch Rev 187.

So, I will have to wait for the New Version to be uploaded.

expertpk wrote:So, I will have to wait for the New Version to be uploaded.

Not per sé
https://www.patreon.com/bePatron?u=13972179

@expertpk:
It probably works in 0.4.14
There is no memory viewer, but load eeprom should work.

The format of an EEPROM data file can vary depending on the specific device or application. However, there are some common elements that are often found in EEPROM data files.

Binary format: EEPROM data files are typically stored in binary format. This means that the data is stored as a sequence of bytes, rather than as text or other encoded format.
Addressable: EEPROM data files are often addressable, meaning that each byte in the file is associated with a specific address in the EEPROM device. This allows the data to be read and written from the EEPROM device in a specific order.
Header: Some EEPROM data files may include a header. The header may contain information about the format of the file, such as the size of the file, the address of the first byte of data, and the data type of each byte.
Payload: The payload of an EEPROM data file is the actual data that is stored in the EEPROM device. The payload can contain any type of data, such as configuration settings, calibration data, or user preferences.
Some common file extensions for EEPROM data files include:

.bin
.eep
.hex
.rom
EEPROM data files can be created and edited using a variety of tools, such as EEPROM programmers, hex editors, and software development environments.

Example of an EEPROM data file

The following is an example of an EEPROM data file for a simple microcontroller:

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
This file contains 16 bytes of data, starting at address 00. The data could represent anything, such as the configuration settings for the microcontroller, or the calibration data for a sensor.

How to use an EEPROM data file

To use an EEPROM data file, you will need to be familiar with the specific EEPROM device that you are using. You will also need to know the address format of the EEPROM device.

Once you have this information, you can use an EEPROM programmer to write the data from the file to the EEPROM device. You can also use an EEPROM programmer to read the data from the EEPROM device and save it to a file.

EEPROM data files can be used to back up the configuration settings of a device, or to restore the configuration settings to a previous state. EEPROM data files can also be used to update the firmware of a device.

https://whatext.com/eep