I am using a CYW20706 based module (CYBT-343026).  I am using the modus toolbox example Audio_Sink for the CYW920706WCDEVAL platform.  The only changes I've made are to the wiced_platform.h to update the pinout for my PCB.

The problem is I get a periodic click when streaming from ios.  I do not see the issue with android.  The period of the click changes on each bluetooth connection, but stays the same while connected.  Somewhere between 1 and 2 sec.  Some connections do not click at all.

I highlighted in white the click while playing a 20Hz tone using a freq generator app.  The second pic is a zoomed in shot.

 

I then captured the i2s data using a logic analyzer and decoded it to see if it was in my audio circuit or in the data.  After decoding I do see the same shapes in the i2s output from the module.

 

I have verified both android and ios are negotiating the same 44.1kHz, max bitrate=53, joint stereo connections.  I'm not sure what to do from here. 

What settings can I make to fix this?

Thanks,

Mark

 

Show Less

Hello Infineon support team. 

My operating environment:
Win10
ModusToolBox Version: 2.4.0
Eclipse Build ID: 2460
Evk: CY8CKIT-062-WIFI-BT
mtb-hal-cat1 release-v2.0.1

When I define normal pin to ADC pin is fine, but use the CSD pin(CYBSP_CSD_SLD2) then function abnormally.
It seems that the pin is occupied, how can I release it?
I switched to using PDL type to use CYBSP_CSD_SLD2 and it worked fine!

Below is my sample code:

#include "cyhal.h"
#include "cybsp.h"
#include "cy_retarget_io.h"

int main(void)
{
  cy_rslt_t result;
  cyhal_adc_t adc_obj;
  cyhal_adc_channel_t adc_chan_0_obj;

  /* Initialize the device and board peripherals */
  result = cybsp_init() ;
  if (result != CY_RSLT_SUCCESS)
  {
    CY_ASSERT(0);
  }

  __enable_irq();

  cy_retarget_io_init(CYBSP_DEBUG_UART_TX, CYBSP_DEBUG_UART_RX, CY_RETARGET_IO_BAUDRATE);

  // ADC conversion result.
  int32_t adc_out;
  cyhal_gpio_free(P8_5);		// CYBSP_CSD_SLD2
  // Initialize ADC. The ADC block which can connect to pin CYBSP_CSD_SLD2 is selected
  result = cyhal_adc_init(&adc_obj, P8_5, NULL);

  // ADC configuration structure
  const cyhal_adc_config_t ADCconfig ={
   .continuous_scanning = true,
   .resolution = 12,
   .average_count = 1,
   .average_mode_flags = 0,
   .ext_vref_mv = 0,
   .vneg = CYHAL_ADC_VNEG_VREF,
   .vref = CYHAL_ADC_REF_VDDA,
   .ext_vref = NC,
   .is_bypassed = false,
   .bypass_pin = NC
  };

  // Call the ADC configure function to begin continuous scanning
  cyhal_adc_configure(&adc_obj, &ADCconfig);

  // Initialize ADC channel, allocate channel number 0 to pin CYBSP_CSD_SLD2 as this is the first
  // channel initialized
  const cyhal_adc_channel_config_t channel_config = { .enable_averaging = false, .min_acquisition_ns = 220, .enabled = true };
  result = cyhal_adc_channel_init_diff(&adc_chan_0_obj, &adc_obj, P8_5, CYHAL_ADC_VNEG, &channel_config);

  for (;;)
  {
    adc_out = cyhal_adc_read_uv(&adc_chan_0_obj);
    printf("%d\r\n", adc_out);
    cyhal_system_delay_ms(100);
  }
}

 

Show Less

Hey all,

I'm looking into interfacing a PSoC5LP to a bit of a strange I2C Master.  Rather than being designed to run on a bus, I have to interface using SDA/SCL and an INT pin in a "point to point" configuration.  The idea is easy enough, it gives a edge on the INT line, I catch it with the PSoC, and read the 9 data bytes that it sends, but there's a twist. 

The catch is this device does not send an address, just the raw data bytes.  How can I adjust the SI2C to account for this?  I see I can use either Software/Hardware address decoding.  Hardware is probably out of the question since there's just no address at all.

This leaves me with software decoding, in which case it seems like modifying the ISR in SI2C_INT.c to just drop bytes immediately into the buffer rather than doing a check on the address might work.  Maybe some custom code placed in the SI2C_SW_ADDR_COMPARE_interruptStart code block in the ISR?  I could maybe set the "expected address" to something that should never occur as the first byte received (would need to see if this is possible, it only has 1 bit of data, the rest are "Reserved", so maybe they'll read all 0?  That would make it easy.) so it will drop into the address compare where I can drop my custom code to place the data in the receive buffer rather than use it as an address?

An easier option after looking further may be just to use the SI2C_ISR_EntryCallback(); and have it perform essentially a modified version of the stock Slave I2C code.

I'd be interested if anyone out there had any better options, maybe even something that just works in hardware?

Thanks!

Show Less

Hello,

I was attempting to do initial programming of a CYPD3135 device over the CC lines using the CY4531 eval kit and now are running into issues with detecting the device.

The first time we attempted to program we were able to detect the target device with the factory default firmware using the EZ-PD configuration utility. We attempted to program the device with a modified version of the CYPD3125-40LQXI_notebook example modified to target CYPD3135 and CC bootloader and got a GET_SILICON_ID U_VDM error (modifications were following instructions here: https://community.infineon.com/t5/USB-EZ-PD-Type-C/Replacing-CYPD3125-with-CYPD3135/m-p/287357#M5913). We then tried programming from an unmodified version of the CYPD3135-40LQXI_power_adapter project. After programming, the device is no longer detected by the EZ-PD utility.

To attempt to revert back to factory conditions, we purchased a MiniProg 3 to program the chip directly over the SWD lines. We were able to flash the device with PSoC Programmer successfully with the image below: 

C:\Program Files (x86)\Cypress\EZ-PD CCGx SDK\CCG3-CCG4\Firmware\binaries\CYPD3135-40LQXI_power_adapter

However, the EZ-PD configuration utility still does not detect the device after SWD flashing. Is the hex file in the location above the same as the factory image? Furthermore, how best do we go about debugging this issue?

Thank you,

David

Show Less

because github cannot be accessed in my office, I have to use offline content.

Show Less

We are having connection stability issues while using CYBLE-012011-00 EZ-BLE Creator Module in our device when communicating with our iOS app.

The problem we were seeing was our device and the phone app would irregularly disconnect, even while idle and in close proximity. The error message the Bluetooth module throws is “0x08: Instant Passed.” We have done our best to optimize our setup including repositioning the module on the pcb and adjusting the connection parameters.

While we have gotten improved performance, we still occasionally get random dropouts/disconnects when the app and our device are communicating with a high frequency of messages i.e. connection is more stable with a lower message interval but degrades the more frequently we send messages.

We would appreciate suggestions to resolve this such that these random disconnects no longer occur unexpectedly.

 

Thanks,

Tim

Show Less

I'm attempting to load the Setup Package for CY8CKIT062WiFiBT

DOWNLOAD - CY8CKIT062WiFiBTSetupOnlyPackage_RevSS.exe

The process stops with a note that the PDL 3.0 is missing

I have PDL 3.1 loaded.

The "Download" button for PDL 3.0 sends me to a 401 error - page not found

Reference: https://www.infineon.com/cms/en/design-support/software/device-driver-libraries/psoc-6-peripheral-driver-library-pdl-for-psoc-creator/

Greg

 

Show Less

Hi,
I am using flash memory part S25FL064L in my design.
I wanted to know the "Write cycle time" to Write 1 Byte data into this memory.
In the datasheet, they have mentioned Typical 220mSec "Nonvolatile Register Write Time" (tw)
But, I want to Write 14000 Bytes of data after power fail (as a retentive data)
So, how should I estimate "Write cycle" time in this case ?

Regards,
Prasad Show Less

Hi all,

I have trying QSPI with iLLD library 1.0.0.0.7. I want using QSPI0 with manually driven CS pin. Here is SPI the initialization code part:

//********************************************************************************
//   Function Name   : init_SPI
//   Author          : 
//   Date            : 
//   Parameters      : NONE
//   Returns         : NONE
//   Notes           : Initializes the SPI Interface
//********************************************************************************
void init_SPI(void)
{
	uint32                          i;

    /* disable interrupts */
    boolean interruptState = IfxCpu_disableInterrupts();


	    IfxQspi_SpiMaster_Config        spiMasterConfig;
	    IfxQspi_SpiMaster_ChannelConfig spiMasterChannelConfig;

	    {
	        /* create module config */
	        IfxQspi_SpiMaster_initModuleConfig(&spiMasterConfig, &MODULE_QSPI0);



	        /* set the maximum baudrate */
	        spiMasterConfig.base.maximumBaudrate = 10000000;


	        /* ISR priorities and interrupt target */
	        spiMasterConfig.base.txPriority  = ISR_PRIORITY_QSPI0_TX;
	        spiMasterConfig.base.rxPriority  = ISR_PRIORITY_QSPI0_RX;
	        spiMasterConfig.base.erPriority  = ISR_PRIORITY_QSPI0_ER;
	        spiMasterConfig.base.isrProvider = (IfxSrc_Tos)IfxCpu_getCoreIndex();



	        /* pin configuration */
	        const IfxQspi_SpiMaster_Pins pins = {&IfxQspi0_SCLK_P20_11_OUT,                               /* SCLK */
	                                             IfxPort_OutputMode_pushPull,
	                                             &IfxQspi0_MTSR_P20_14_OUT,                               /* MOSI */
												 IfxPort_OutputMode_pushPull,
	                                             &IfxQspi0_MRSTA_P20_12_IN,  IfxPort_InputMode_pullDown,  /* MISO */
	                                             IfxPort_PadDriver_cmosAutomotiveSpeed3                   /* pad driver mode */
	        };
	        spiMasterConfig.pins = &pins;

	        /* initialize module */
	        IfxQspi_SpiMaster_initModule(&g_QspiCpu.drivers.spiMaster, &spiMasterConfig);
	    }

	    {
	        /* create channel config */
	        IfxQspi_SpiMaster_initChannelConfig(&spiMasterChannelConfig,
	            &g_QspiCpu.drivers.spiMaster);

	        /* set the baudrate for this channel */
	        spiMasterChannelConfig.base.baudrate = 3000000;

	        const IfxQspi_SpiMaster_Output slsOutput = {
	        		                            &IfxQspi0_SLSO9_P20_3_OUT,
                                                            //NULL_PTR,   // if this option is used then got jump to intrisic code part !!!!!
	                                                    IfxPort_OutputMode_pushPull,
	                                                    IfxPort_PadDriver_cmosAutomotiveSpeed1};

	        spiMasterChannelConfig.sls.output.pin    = slsOutput.pin;
	        spiMasterChannelConfig.sls.output.mode   = slsOutput.mode;
	        spiMasterChannelConfig.sls.output.driver = slsOutput.driver;
	        spiMasterChannelConfig.base.mode.autoCS = 0;   // HERE I SET AUTO CS DISABLED, BUT CS STAYS ENABLED!!!!!

	        /* initialize channel */
	        IfxQspi_SpiMaster_initChannel(&g_QspiCpu.drivers.spiMasterChannel, &spiMasterChannelConfig);
	    }

	    /* init tx buffer area */
	    for (i = 0; i < SPI_BUFFER_SIZE; i++)
	      g_QspiCpu.qspiBuffer.spi0RxBuffer = (uint8)(0);

	    IfxCpu_restoreInterrupts(interruptState);

} //end init_SPI

As you see I set up the autoCS disabled but it was not took effect, CS stays automatically driven. Also if I set NULL_PTR for spiMasterChannelConfig.sls.output.pin, then I get intrisic entry, debugger jumps to here :

( file IfxCpu_Inrtinsics_Gnuc.h )

/** Insert DEBUG instruction
 */
IFX_INLINE void __debug(void)
{
    __asm__ volatile ("debug" : : : "memory");
}

What the problem could be please ?

Thank you in advance !

Best regards,
Born Show Less