• State Accepted Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 23 subscribers
  • Views 4186 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

STM32F4 memcpy arry to structure other name addr hard-fault?

artazhang

I have some question about memcpy?

when i use memcpy with STM32F4,i wanna copy some data to structure in other data(copy data size 16byte), but however i used microlib or not this memcpy translation by keil,i see this thumb code become STRD r1,r12,[r2,#0x08] ,but R2 reg is 0x20017977 is a not word align. R2 reg number is memcpy Dst addr.
When i use memcpy like "memcpy(0x20017977,(u8*)Src_addr,16)" i see translation thumb code use "__aeabi__memcpy(0x080001E4)",that`s all right.

so, I want know whey Armcc translation code do this?And How can i safe use when i use memcpy funcation?

Parents
  • 0

    I would agree there is a stellar amount of stupidity making memcpy() fault on unaligned data, it used to be the default method of pulling unaligned data into aligned local variables on old ARM7/ARM9 boards.

    There are occasions when you want memcpy() to be fast, but most need it to be safe.

Reply
  • 0

    I would agree there is a stellar amount of stupidity making memcpy() fault on unaligned data, it used to be the default method of pulling unaligned data into aligned local variables on old ARM7/ARM9 boards.

    There are occasions when you want memcpy() to be fast, but most need it to be safe.

Children