STM32 EEPROM Emulation conversion to Keil

OK, fair cop.... however, in my defence:

in eeprom.c, we have

#include "eeprom.h"

so why do I get the error if the .h is included?

Secondly, I did use the uvision 'find in files' to search for it, and it wasn't found in anything but output files.

Sorry for not having found it on my own, sometimes we all need a little help with something very stupid, which is staring us in the face....

I didn't realise about the ST libraries though (I won't call them 'libs' ever again... knuckles slapped far too many times in this thread for that one!), but as I said at the start, I'm new to ARM, new to Keil, so its very easy to get waylayed.

Thanks for all the pointers though (no pun intended), I've learned quite a bit from this thread (mainly, think long and hard before posting to the Keil forum, pedantry is alive and well).

again, very valid points!

The ST rant really does say it all, much of what I have had to write is identical to any other micro, or PC code to that matter, as soon as you talk to hardware it all falls over.

I am the sole engineer here (and a hardware engineer at that), I taught myself C back in the late 1980's having written in assembler for many years prior to that, so my 'terminology' is not always correct, as I have no reason to explain what I do except in situations like this :-) So thanks for the help, I will try to ask better in future.

So far I am very impressed with the ST32f103, a bit of hair pulling, but I have SPI, USB, USART etc all working well, I only have this and the ADC to get to grips with.

Thanks :-)

ps why does my flag show as American? As ARM are very local to me here, and they own Keil, why do we not have a Union Jack?

ps why does my flag show as American? ,/i>

The good old captain will not like to hear this, but if things go on the way they do, soon you will have a standard Chinese flag instead...

so, if you haven't defined the correct symbol(s) to satisfy those #if conditions
ST has tried to make code that can handle any compiler, any ST chip, any clock and any .... thus it is extremely messy. One example: I have had to modify the ST code since the possible combination of #ifs could not be set to the processor and clock that was used.

In this particular case, it would have been better to have had a "none of the above" clause - to catch this situation where the correct symbol(s) are missing

that should be SOP anywhere.

Erik

OK, so thanks to a few pointers, I am down to 2 linker errors... :-)

linking...
LD3070-100.axf: Error: L6218E: Undefined symbol FLASH_ErasePage (referred from eeprom.o).
LD3070-100.axf: Error: L6218E: Undefined symbol FLASH_ProgramHalfWord (referred from eeprom.o).
Target not created

in stm32f10x_flash.h which I have included in the ST eeprom.c file, I have on line 310

FLASH_Status FLASH_ErasePage(uint32_t Page_Address);

on line 313

FLASH_Status FLASH_ProgramWord(uint32_t Address, uint32_t Data);

Any idea why the linker doesn't find these? it finds the rest!

hopefully I have given enough info this time :-)

the linker does not look for func():, it looks fr func(){

Erik

But do you have an _implementation_ of these functions in your project? The error suggests that you do not. Maybe you forgot to add a source file...?

That should be a semicolon - not a colon!

ie,

"the linker does not look for func(); - it looks for func(){...}"

And, to be pendantic, the linker doesn't look for source files at all; it looks only at the resulting object files - the compiler's output from those sources.

OK, calm down, so I didnt explain very well.......again

On line 208 in stm32f10x_flash.c is the function:

FLASH_Status FLASH_ErasePage(uint32_t Page_Address)
{
  FLASH_Status status = FLASH_COMPLETE;
  /* Check the parameters */
  assert_param(IS_FLASH_ADDRESS(Page_Address));
  /* Wait for last operation to be completed */
  status = FLASH_WaitForLastOperation(EraseTimeout);

  if(status == FLASH_COMPLETE)
  {
    /* if the previous operation is completed, proceed to erase the page */
    FLASH->CR|= CR_PER_Set;
    FLASH->AR = Page_Address;
    FLASH->CR|= CR_STRT_Set;

    /* Wait for last operation to be completed */
    status = FLASH_WaitForLastOperation(EraseTimeout);
    if(status != FLASH_TIMEOUT)
    {
      /* if the erase operation is completed, disable the PER Bit */
      FLASH->CR &= CR_PER_Reset;
    }
  }
  /* Return the Erase Status */
  return status;
}

so they are in the header files, and in the .c file. Yes its basic c stuff, but whats there is correct, its me not explaining properly (again), but I am trying!!

but they are not found, any ideas?

... that FLASH_Status FLASH_ErasePage(uint32_t Page_Address) is not included because of the blasted "universality ifs"

a simple test would be
FLASH_Status FLASH_ErasePage(uint32_t Page_Address)
{ $#!^ it's not included

this would give you a compile error if the function is not 'iffed out' (assuming that the module is included, other means will tell you that).

Erik

stm32f10x_flash.c is part of the ST Standard Peripheral Library.

IF you've downloaded the EEPROM Emulation example from the ST site, it will be using the latest version of the ST Standard Peripheral Library. As previously noted, that is likely to be not the same as the version of the ST Standard Peripheral Library included with your Keil installation - therefore, it will not work with that!

If you want to use examples from the ST site, then you really should also use the the ST Standard Peripheral Library from the ST site - this is exactly the kind of grief that you will get if you try to mix "new" ST examples with "old(er)" ST libraries.

Been there, done that!

"the blasted 'universality ifs'"

ST fundamentally changed the library organisation; so the 'universality ifs' (among other things) are entirely different - therefore anything written for one version is doomed to failure with the other.

There is a superficial look of similarity - which leads to the false expectation that it could be made to work.

I wasted a couple of days on this last summer; my conclusion: just don't do it!

Either stick completely to the latest stuff (Library & examples) downloaded from the ST site;

Or stick completely to the (older) stuff included with the Keil installation.

Don't try to mix-and-match.