PSoC™ 6 Forum Discussions

I'm running SPI with DMA like this:

I'm transferring blocks of 512 bytes (reading and writing to SD card), and sometimes I don't care about the transmitted data and sometimes I don't care about the received data. (Similar to how the High-Level SCB SPI function Cy_SCB_SPI_Transfer() is used.)

This solution works:

bool sd_spi_transfer(sd_card_t *this, const uint8_t *tx, uint8_t *rx, size_t length) {
    uint8_t dummy[512];
      
    if (!tx) {
        memset(dummy, 0xFF, length);
        tx = &dummy[0];
    }
    if (!rx) {
        rx = &dummy[0];
    }
//...
/*Set up SRC addr for TX DMA*/
Cy_DMA_Descriptor_SetSrcAddress(this->txDma_Descriptor_1, tx);
/*Set up DEST addr for RX DMA*/
Cy_DMA_Descriptor_SetDstAddress(this->rxDma_Descriptor_1, rx);
/*Enable DMA_channels*/
Cy_DMA_Channel_Enable(this->rxDma_base, this->rxDma_channel);
Cy_DMA_Channel_Enable(this->txDma_base, this->txDma_channel);

I thought I'd try to optimize away the useless 512 byte buffer, like so:

spi_dma_transfer(spi_t *this, uint16 len, const uint8_t *txBuffer, uint8_t *rxBuffer) {
uint8_t dummy = 0xFF;
if (!txBuffer) {
txBuffer = &dummy;
}
if (!rxBuffer) {
rxBuffer = &dummy;
}
    
/*Set up SRC addr for TX DMA*/
Cy_DMA_Descriptor_SetSrcAddress(this->txDma_Descriptor_1, txBuffer);
/*Set up DEST addr for RX DMA*/
Cy_DMA_Descriptor_SetDstAddress(this->rxDma_Descriptor_1, rxBuffer);
/*  Use 256 X loops and 2 Y loops */
/*Set up RX Descriptor 1*/
Cy_DMA_Descriptor_SetXloopSrcIncrement(this->rxDma_Descriptor_1, 0);
if (&dummy == rxBuffer)
  Cy_DMA_Descriptor_SetXloopDstIncrement(this->rxDma_Descriptor_1, 0);
else
  Cy_DMA_Descriptor_SetXloopDstIncrement(this->rxDma_Descriptor_1, 1);
Cy_DMA_Descriptor_SetXloopDataCount(this->rxDma_Descriptor_1, 256);
Cy_DMA_Descriptor_SetYloopSrcIncrement(this->rxDma_Descriptor_1, 0);
if (&dummy == rxBuffer)
  Cy_DMA_Descriptor_SetYloopDstIncrement(this->rxDma_Descriptor_1, 0);
else
  Cy_DMA_Descriptor_SetYloopDstIncrement(this->rxDma_Descriptor_1, 256);
Cy_DMA_Descriptor_SetYloopDataCount(this->rxDma_Descriptor_1, 2);
/*Set up TX Descriptor 1*/
if (&dummy == txBuffer)
  Cy_DMA_Descriptor_SetXloopSrcIncrement(this->txDma_Descriptor_1, 0);
else
  Cy_DMA_Descriptor_SetXloopSrcIncrement(this->txDma_Descriptor_1, 1);
Cy_DMA_Descriptor_SetXloopDstIncrement(this->txDma_Descriptor_1, 0);
Cy_DMA_Descriptor_SetXloopDataCount(this->txDma_Descriptor_1, 256);
if (&dummy == txBuffer)
  Cy_DMA_Descriptor_SetYloopSrcIncrement(this->txDma_Descriptor_1, 0);
else
  Cy_DMA_Descriptor_SetYloopSrcIncrement(this->txDma_Descriptor_1, 256);
Cy_DMA_Descriptor_SetYloopDstIncrement(this->txDma_Descriptor_1, 0);
Cy_DMA_Descriptor_SetYloopDataCount(this->txDma_Descriptor_1, 2);
    
/*Enable DMA_channels*/
Cy_DMA_Channel_Enable(this->rxDma_base, this->rxDma_channel);
Cy_DMA_Channel_Enable(this->txDma_base, this->txDma_channel);
}

The idea is to send from, or receive to, the same byte over and over instead of filling an array that no one will ever look at, and I do that by setting the increment to 0. Of course, the transmit dest. is

  Cy_DMA_Descriptor_SetDstAddress(this->txDma_Descriptor_1, (void *) &this->base->TX_FIFO_WR);

and the receive src. is

  Cy_DMA_Descriptor_SetSrcAddress(this->rxDma_Descriptor_1, (void *) &this->base->RX_FIFO_RD);

so those don't increment.

It almost, kinda, sorta, works, but not quite. If I'm reading, say, 4 blocks, I'll get 3 OK, and then time out waiting (as much as 4 seconds) for the completion interrupt for the 4th. Logically, it seems like it should be the same. Maybe there is a timing issue? Or, have I messed up some mundane detail, as usual?

operating system: WINDOWS 10

IDE: PSoC creator 4.2

MCU: CYBLE-416045-02

I am trying to program the CYBLE-416045-02 proramming will fail during erasing of flash. this is the details of the error code....

"There was an error running the Programmer to configure the device. Try lowering the clock speed used for communication in the Options dialog, under Tools > Options > Program/Debug > Port Configuration. If the problem persists, make sure that the Programmer for this debug target is properly installed and ready to use."

output window

Programming device 'PSoC 63 CYBLE-416045-02 (CM4)' with file 'C:\Users\w-wow\BioCheck\BioCheck_OTA\Application.cydsn\CortexM4\ARM_GCC_541\Debug\Application.hex'.

Device ID Check

Erasing of Main Flash...

Erasing of Main Flash Failed

EraseAll API returned: Error code 0x7491A400: Unknown SROM status code

Error: dbg.M0023: There was an error while programming the device: PSoC Programmer reported error (100 - EraseAll API returned: Error code 0x7491A400: Unknown SROM status code)

I have tried to slow the clock speed as suggested in the details above but programming still fails at flash erase.

I have programmed these MCU's before using the same setttings.

I recently installed the PSoC creator 4.3 IDE but could not get the ide to program the MCU so I switched back to using PSoC creator 4.2. PSoC creator 4.3 is still installed but is not being used.

I'm looking at this:

__STATIC_INLINE void Cy_RTC_SyncFromRtc(void)

{

    uint32_t interruptState;

    interruptState = Cy_SysLib_EnterCriticalSection();

    /* RTC Write is possible only in the condition that CY_RTC_BUSY bit = 0

    *  or RTC Write bit is not set.

    */

    if ((CY_RTC_BUSY != Cy_RTC_GetSyncStatus()) && (!_FLD2BOOL(BACKUP_RTC_RW_WRITE, BACKUP_RTC_RW)))

    {

        /* Setting RTC Read bit */

        BACKUP_RTC_RW = BACKUP_RTC_RW_READ_Msk;

        /* Delay to guarantee RTC data reading */

        Cy_SysLib_DelayUs(CY_RTC_DELAY_WHILE_READING_US);

        /* Clearing RTC Read bit */

        BACKUP_RTC_RW = 0U;

    }

    Cy_SysLib_ExitCriticalSection(interruptState);

}

in Generated_Source\PSoC6\pdl\drivers\peripheral\rtc\cy_rtc.h. I'm guessing that Cy_SysLib_EnterCriticalSection() disables interrupts and returns the previous value.  If so, is it really necessary for this function to disable interrupts the whole time? It really messes with my application. Could I make my own version of this routine that wouldn't block interrupts for so long? (I don't really understand exactly how this routine works.)

I want to store some configuration in the sflash and lock the debug port using the efuse. I have read that if the debug port is locked, writing to the sflash is no longer possible.

In my use case, some of that config stored in the sflash might need to change. Is there a way to lock the debug port (SWD) and still be able to write to the sflash ? Is there a way to lock only parts of the sflash?

Thanks

I have a question on this discussion: Re: Do DMA triggers work on trigger level change or just on trigger level itself?

3. Re: Do DMA triggers work on trigger level change or just on trigger level itself?

BragadeeshV_41 Nov 15, 2019 10:14 AM (in response to user_1669321) Hi user_1669321, It is recommended to set Trigger deactivation and re triggering to Retrigger after 4 Clk_Slow cycles when using SCB peripheral.

I see this "Note that the DMA has a trigger deactivation setting. For the SCB this should be set to 16." in PSoC 6 MCU with BLE: CY8C63x6, CY8C63x7 Architecture TRM, Document No. 002-18176 Rev. *H, page 248, section 25.3.4 SPI Buffer Modes; 25.3.4.1 FIFO Mode. Are those statements saying the same thing (and the difference is slow clocks vs clocks)? Because I do see "Retrigger after 16 Clk_Slow cycles" as one of the options:

Hi,

I'm using CYBLE-416045-02 and want to change Uart baud rate during run time.Please help.

Thank you

Hi there,

I would like to know if is there anything different in the usage of the BootloaderUtils.dll for the use with PSoC 6 devices. We are trying to provide the users of our product (which has a PSoC6) to do the DFU (Device Firmware Update) through our software (Visual Studio C# based), which already works pretty good with PSoC 4 and 5 devices, updating through UART and USB HID.

Now I am trying to use this same code with PSoC6 devices through UART interface.

But then when our software calls the BootloaderUtils.dll in the function Bootloader_Utils.CyBtldr_Program, the Visual Studio, it throws the following exception:

System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt

It works perfectly to update when I use the Bootloader Host Tool from PSoC Creator 4.2 or 4.3.

I tried to use the cybootloaderutils.dll files provided in the installation of these PSoC Creator bin files, but it throws the  same error.

Am I missing something?

I have a customer working with the CYBLE-416045-EVAL stick and has upgraded the programmer to KitProg3 in order to work within his Keil uVision environment.  There is an error he is seeing, is it something we know about and can address?  Here is his statement:

We almost succeeded to use Keil with the kitprog, hooray! The problem remains is this error: RDDI-DAP Error. Any ideas?

Thank you!

Please let us know.