parallaxinc / Simple-Libraries

Contents of the SimpleIDE workspace folder and its Parallax Learn Simple Libraries subfolder.
http://learn.parallax.com/propeller-c-set-simpleide/update-your-learn-folder
21 stars 21 forks source link

ee_put_float appears to only work when executed before other put actions #9

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. See attached project .zip file
2. Setup project to write various data types to EEPROM
3. Put a float to a known EEPROM location, Get it back to check that it was 
written correctly
4. Put a byte data type to the same location as above (ee_put_byte)
5. Put a float to the next open location on the EEPROM (above address + 1), Get 
it back and check to see if was written correctly
6. Try steps 4-5 again, but Put the float at a known 4-byte boundary (above 
address + 4)

What is the expected output? Should be able to put the float and get it back

What do you see instead? No longer able to put the float value into a known 
open location

What version of the product are you using? On what operating system? 0-9-25 + 
latest Learn folder (4/30/2013) on Mac OS X & Win 7

Please provide any additional information below. See attached .zip of the 
project. This test was developed after Andy mentioned that a new version of the 
EEPROM code was available (04/30/2013). 

Basically, my original project's purpose is to check for a byte value in EEPROM 
that indicates that a float value and string descriptor had been saved during a 
previous execution. If the byte value is not 1, the program writes the 
following to EEPROM location 64,000, for the next execution, else uses the 
values from EEPROM:

  A byte value: 1                  <- stored values indicator
  A float value: 274.10         <- radians value
  A location description string: "Livermore, CA"  <- just descriptor text

This should put the following in EEPROM:

  64000: 1
  64001: 32-bit float value that represents 274.10
  64005: "Livermore, CA"

Original issue reported on code.google.com by dgat...@gmail.com on 1 May 2013 at 4:35

Attachments:

AndyLindsay commented 8 years ago

This was fixed a long time ago. Sorry for not removing it sooner.