Kinsey Moore commented on a discussion on stm32h7/include/lwipbspopts.h: https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/37#note_150786 > +#define ETH_PAD_SIZE 2 > + > +/* Strongly byte-by-byte MEMCPY for STM32H7 to avoid all hardware traps. > + * Optimized library versions of memcpy() may use word-aligned instructions > (LDR/STR) > + * even on byte-access paths, which can trigger usage faults in certain > memory regions. > + */ > +static inline void stm32h7_byte_memcpy(void *dst, const void *src, size_t > len) { > + uint8_t *d = (uint8_t *)dst; > + const uint8_t *s = (const uint8_t *)src; > + while (len--) { > + *d++ = *s++; > + } > +} > +#define MEMCPY(dst, src, len) stm32h7_byte_memcpy(dst, src, len) > +#define SMEMCPY(dst, src, len) stm32h7_byte_memcpy(dst, src, len) > +#define MEMMOVE(dst, src, len) stm32h7_byte_memcpy(dst, src, len) Is this a result of locating the lwip heap space in D2 SRAM? -- View it on GitLab: https://gitlab.rtems.org/rtems/pkg/rtems-lwip/-/merge_requests/37#note_150786 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
