As a result of checking by enabling ADC DMA (GIOB0 trigger), SCI Tx, Rx DMA, SCI Tx, Rx Packet, packets are destroyed by ADC DMA.
Please tell me how to use it properly so there are no conflicts.
SCI Tx and Rx packets are fine as long as you don't use only GIOB triggers.
Upload and send project files.
1. SCI tx Debugging mode result is abnormal (Using GIOB0 Trigger for ADC DMA)
2. SCI tx Debugging mode result is normal (I didn't use GIOB0 trigger for ADC DMA)
Hi Eun Kyu Son,
I didn't see the issue you are talking about at my end.
I just debug your code as it is and i didn't see the issue you are talking about.
Here is the test result for UART1 sciREG:
Am i need to do any further changes to trigger the issue?
--
Thanks & regards,
Jagadish.
Thanks for your help.
The problem occurs immediately without any additional changes to the source code.
As a result of the test, when UART1 sciREG TX, RX, and GND are connected to the J2 and J3 pins of the LAUNCHPAD TMS57012 with a terminal program (TOKEN 2), strange values other than 0x31,0x32,0x33,0x34,0x35,0x36,0x37,0x38,0x39,0x0d,0x0a are output as in the question.
In the source code, the following 2 lines must be commented out so that they are output normally. I wonder if there is anything wrong with the DMA settings of SCI and ADC.
gioSetBit(gioPORTB, 0u, 0u);
gioSetBit(gioPORTB, 0u, 1u);
[ ABNORMAL printf ] [ NORMAL printf - deleted 2 lines ]
--------> 
Hi Eun,
The code looks good to me.
gioSetBit(gioPORTB, 0u, 0u);
gioSetBit(gioPORTB, 0u, 1u);
Are those the function calls in if(_1msTmr != 0u) section?
Can you suspend the code execution to check DMA CH0 settings and the value in SCITX register?
The base address for the DMA control packets is 0xFFF80000.
Hello QJ Wang.
As you said, I checked the debugging result of the part and the surrounding RAM address with the memory browser.
In conclusion, it was confirmed that adc2DmaBuf and sciDma (sciDmaRxData, sciDmaTxData, sciDmaTxBuf) collide.
The address (0x08001708) pointing to DMA_CH0 of 0xFFF80000 you mentioned and the value of adc2DmaData (0x080016F8) moved together.
It seems to be a memory invasion error, so I looked for problems with adcdmaInit(void) settings.
As a result, we determined that the number of channels to use for ELCNT was incorrectly.
Correctly corrected the number of dma channels, and confirmed that it operates normally.
It was a problem caused by my inability to use it. Thank you for caring me.
