Made it compile on Windows : Would you test it ?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. there are no problems ;)


Hello I made your code compile using em::blocks a free IDE for embedded arm 
devices under Windows.
As I don't have the motion player shield right now i'm not able to test the 
software.

Would you mind to test the attached hex file, please and give me a comment ?

Many thanks in advance

Tom

Original issue reported on code.google.com by [email protected] on 27 Feb 2014 at 11:50

[GoogleCodeExporter]

Hi Tom
thank you for interesting my project.
i tested your firmware on my board but it doesn't work.
i think your specified flash allocation is wrong.

My Motion Player's Linker script has abnormal part(FLASHORG and FLASH) like 
below.
Please refer to the stm32_flash.ld linker script.
best regard

Tonsuke

/* Memory Spaces Definitions */

MEMORY
{
  RAM2 (xrw) : ORIGIN = 0x10000000, LENGTH = 64K
  RAM (xrw) : ORIGIN = 0x20000000, LENGTH = 128K
  FLASHORG (rx) : ORIGIN = 0x08000000, LENGTH = 64K
  FLASH (rx) : ORIGIN = 0x08010000, LENGTH = 1024K-64K-256K
/*  FLASH (rx) : ORIGIN = 0x08000000, LENGTH = 1024K */
  FLASHB1 (rx) : ORIGIN = 0x00000000, LENGTH = 0
  EXTMEMB0 (rx) : ORIGIN = 0x00000000, LENGTH = 0
  EXTMEMB1 (rx) : ORIGIN = 0x00000000, LENGTH = 0
  EXTMEMB2 (rx) : ORIGIN = 0x00000000, LENGTH = 0
  EXTMEMB3 (rx) : ORIGIN = 0x00000000, LENGTH = 0
}

also check Motion Player Flash Structure
http://motionplayer.wiki.fc2.com/wiki/%E5%86%85%E9%83%A8%E6%A7%8B%E9%80%A0

Original comment by [email protected] on 2 Mar 2014 at 4:52

[GoogleCodeExporter]

Changed the script as referred by you.
thanks for you answer.

Could you explain this mapping to me ?  As i see FLASH start 64k later than 
usual 
the length is max length minus 256k .

My question where do you use the last 256k ?
Do you put any code to FLASHORG? and if yes where ? i don't see any references 
to this section.

Original comment by [email protected] on 3 Mar 2014 at 7:45

Attachments:

• motion-player.map
• motion-player.hex
• motion-player.elf

[GoogleCodeExporter]

if i see right the isr is set to 0x08000000 then , right ?

Original comment by [email protected] on 3 Mar 2014 at 7:46

[GoogleCodeExporter]

btw could you send me your mapping file for inspection?

Original comment by [email protected] on 3 Mar 2014 at 7:56

[GoogleCodeExporter]

map file

Original comment by [email protected] on 3 Mar 2014 at 10:51

Attachments:

• stm32f4_motion_player.map

[GoogleCodeExporter]

ISR       0x08000000 16KB
PIC0#0 0x08004000 6KB
PIC1#0 0x08005800 6KB
CONF   0x08007000 4KB
PIC0#1 0x08008000 16KB
PIC1#1 0x0800C000 16KB
TEXT    0x08010000 704KB
PIC0#2 0x080C0000 128KB
PIC1#2 0x080E0000 128KB

last 256KB is used as a part of background image data which displays in filer 
and music play background.
each background image size is 150KB, so it is divided in 3 pieces.

your second attached ELF is worked. 
but HardFault occurred during LCD Initialize process.

Original comment by [email protected] on 3 Mar 2014 at 4:17

[GoogleCodeExporter]

thank you very much for testing and your annotations.
I have to  check that hardfault  thing in next time time . But first i have to 
build the hardware somehow which will need some time ;)

again thank you very much

Original comment by [email protected] on 4 Mar 2014 at 7:36

[GoogleCodeExporter]

you're welcome:)
i'm happy to hear that.

Original comment by [email protected] on 4 Mar 2014 at 12:46