Hello,
yes, I have enabled DMA as you said
This is what comes in linker script to locate sections for data:
/* Initialized data sections goes into RAM, load LMA copy after code */
.data :
{
. = ALIGN(4);
_sdata = .; /* create a global symbol at data start */
*(.data) /* .data sections */
*(.data*) /* .data* sections */
. = ALIGN(4);
_edata = .; /* define a global symbol at data end */
} >RAM AT> FLASH
/* Uninitialized data section */
. = ALIGN(4);
.bss :
{
/* This is used by the startup in order to initialize the .bss secion */
_sbss = .; /* define a global symbol at bss start */
__bss_start__ = _sbss;
*(.bss)
*(.bss*)
*(COMMON)
. = ALIGN(4);
_ebss = .; /* define a global symbol at bss end */
__bss_end__ = _ebss;
} >RAM
/* User_heap_stack section, used to check that there is enough RAM left */
._user_heap_stack :
{
. = ALIGN(8);
PROVIDE ( end = . );
PROVIDE ( _end = . );
. = . + _Min_Heap_Size;
. = . + _Min_Stack_Size;
. = ALIGN(8);
} >RAM
I guess it's not about the location of data.. As I said in USB HS:
1- All endpoints except EP0 work well when DMA enabled, so it shows that memory location may not be the problem as I made "uint32_t Setup[12] __attribute__ ((aligned (4)));" to make sure that space allocated for setup packets be also 4byte align
2- All endpoints including EP0 work well when DMA disabled, so it shows that the problem might be something with DMA
The strange thing is that EP0 works well when I send packets with some delay in between (so the memory location may not be the source of problem) and it only stuck when packets are sent continuously one after the other without delay in between
I found something in Reference Manual but I did not understand it... That might also be related to my problem... I don't know, I just guess...
(stm32f72xxx reference manual, Rev 3, page 1278):
"STPKTRX: Setup packet received.
Applicable for control OUT endpoints in only in the Buffer DMA Mode. Set by the OTG_HS, this bit indicates that this buffer holds 8 bytes of setup data. There is only one setup packet per buffer. On receiving a setup packet, the OTG_HS closes the buffer and disables the corresponding endpoint after SETUP_COMPLETE status is seen in the Rx FIFO. OTG_HS puts a SETUP_COMPLETE status into the Rx FIFO when it sees the first IN or OUT token after the SETUP packet for that particular endpoint. The application must then re-enable the endpoint to receive any OUT data for the control transfer and reprogram the buffer start address. Because of the above behavior, OTG_HS can receive any number of back to back setup packets and one buffer for every setup packet is used."
"B2BSTUP: Back-to-back SETUP packets received for USB OTG HS Applies to control OUT endpoint only. This bit indicates that the core has received more than three back-to-back SETUP packets for this particular endpoint"
Thanks in advance,
Best Regards
