¿ªÔÆÌåÓý

Fw: Re: [BITX20] uBITX EEPROM MAP


Jack Purdum
 

My bad...I didn't even think of those calls. In the main INO file are the following defines:

/**
 * These are the indices where these user changable settinngs are stored  in the EEPROM
 */
#define MASTER_CAL 0
#define LSB_CAL 4
#define USB_CAL 8
#define SIDE_TONE 12
//these are ids of the vfos as well as their offset into the eeprom storage, don't change these 'magic' values
#define VFO_A 16
#define VFO_B 20
#define CW_SIDETONE 24
#define CW_SPEED 28
These are byte offsets into the EEPROM address space. Because LSB_CAL is offset by 4 bytes, we know that MASTER_CAL takes 4 bytes (i.e., 0-3) and is likely a long data type. Because an int can have a value of 32,767, SIDE_TONE's memory requirements could be reduced, as could CW_SIDETONE. CW_SPEED could be a byte value since an unsiged byte can have a value of 255. That's over my current WPM CW speed.

Anyway, you could write a short program that would write values to EEPROM using values that make sense for you, or you could just run the program and use the menu items associated with each constant, since the code writes the new values to EEPROM.

Jack, W8TEE


On Saturday, March 24, 2018, 11:21:38 AM EDT, Ronald Pfeiffer via Groups.Io <w2ctx@...> wrote:


Maybe its EEPROM.get? and EEPROM.put

rOn



From: Jack Purdum via Groups.Io <jjpurdum@...>
To: [email protected]
Sent: Saturday, March 24, 2018 10:44 AM
Subject: Re: [BITX20] uBITX EEPROM MAP

Joe:

Interesting. I just did a GREP on all the source code files and did not find an EEPROM.read() or EEPROM.write(). Where did you read that the original code uses EEPROM?

Jack, W8TEE


On Saturday, March 24, 2018, 10:20:47 AM EDT, W3JDR <joe@...> wrote:


Does anyone have a file with the UBITX? EEPROM map as delivered from the factory? I had to replace the Nano board, but now don't have the proper EEPROM settings to get going again.

Joe