Thanks for your response clive1, I didn't think anyone was paying attention.
Anyway, I've made progress with this and I'm still working on it.
Here are the changes I've made:
1) Change target device to STM32F401VC
2) Changed clock to 84 MHz.
3) Remove stm324xg_eval.c from project and add in STM32F401_discovery.c, .h files too of course. I think they are the same as the files you've enclosed.
4) Change BUTTON_KEY to BUTTON_USER
5) Removed EVAL_COM1 declarations from stm32f401_discovery.c and instead populated USART_InitStructure and then called USART_Init.
6) Removed STM_EVAL_COMInit from stm32f401_discovery.c as I am using USART_init directly
7) Added COM_Typedef to stm32f401_discovery.h
8) Copied definition of COM port1 from stm324xg_eval.h to stm32f401_discovery.h. Had to change USART3 to USART6 and change pin numbers and stuff.
Why is it that bits in ports are called pins in STM nomenclature? Very confusing.
Look okay so far? I'm still getting used to MDK IDE, have not used it before. I've been using IAR for 10 years. At least it compiles and downloads and I can start to step through it. I added some of the LED blinking stuff from the discovery board demo and that is working. I still need to add menu.c and all that.
Hi clivel,Thanks for your prompt reply and it helps us a lot.We have tried to load different binary files(images) given by the example to different memory locations. And it is found that only when the image in the default starting application address(0x08008000) is able to run. For images in other locations, if it is the same as the one in the default starting address, it can also run properly. And it shows what exactly you mentioned.However, we are still confused by two problems:1. How can we configure the binary file so that it can be loaded to different memory address and run properly. 2. If the specific address can only be included when the binary file is generated. How do we generate a binary file for a specific memory address?
Retrieving data ...