PSoC™ 6 Forum Discussions

Hello, I have a question while looking at the PDL library.

Please look at the picture below.

The top comment says ECO is used, and the comment below while says IMO is used.

As far as I know, "ECO is External Crystal Osilator" and "IMO is Internal Main Osilator," but aren't the two different things?

I am inquiring because the description and the code used are different.

And if I write IMO in the part where ECO is entered, is it possible to write PILO Trim based on the IMO?

Thankyou for your Reply

Hi,

  We made an evaluation board using PSoC 6 MCU.

  According to the datasheet, the XRES pin should be pulled up to V_DDD, as shown in the following figure.

Unfortunately, we thought PSoC 6 should have an internal pull-up resistor and did not add the pull-up resistor. So the XRES pin is kept floating. But luckily, some of the fabricated boards are working normally (we are not sure whether the abnormal boards are caused by the floating of XRES pin).

Hence I am here to ask about the consequence of floating XRES pin.

1. Some of our boards are working normally, does it mean XRES is not necessary to be pulled up?

2. Is there leakage current caused by floating of XRES pin? If yes, how much can it be?

3. What is the other abnormal phenomenon that will happen if the XRES pin is floating? 

4. In the datasheet, there is a check table about schematic design, we found the requirement of pull-up XRES pin. Excepting the pull-up of XRES pin, are there any other dedicated pins that should be pull-up or pull-down? Such as SWDIO, SWDCLK, and so on.

Sorry for the long question lists.

Sincerely appreciate your kind help!

hello I get the CY8CPROTO-062-4343w PSOC 6 WI-FI BT 

When I try to run some program I get the error Can't open CMSIS-DAP port-dap port

hi sir,

I am using PSoC+43438 module and I would like to add "ethernet" interface.

how to implement it ? via spi ?

please advice.

thanks.

best Regards,

howardyu

Dears

When I upgrade project using Libraries mtb-hal-cat1 from 1.6.0 to newer 2.X. I have several problems. Maybe I am doing something in wrong way... when updating libs.

For example on this project https://github.com/Infineon/mtb-example-psoc6-usb-audio-device-freertos

void audio_app_clock_init(void)
{
/* Initialize the PLL */
cyhal_clock_get(&pll_clock, &CYHAL_CLOCK_PLL[0]);
cyhal_clock_init(&pll_clock);

/* Get the reset USB clock */
cyhal_clock_get(&usb_rst_clock, &CYBSP_USB_CLK_DIV_obj);
}

passing argument 2 of 'cyhal_clock_get' from incompatible pointer type [-Wincompatible-pointer-types]

I tried investigate what is wrong in "mtb-hal-cat1" library

cyhal_clock.h

1.6.0

extern const cyhal_resource_inst_t CYHAL_CLOCK_PLL[SRSS_NUM_PLL];

> = 2.0.1

extern const cyhal_clock_t CYHAL_CLOCK_PLL[_CYHAL_SRSS_NUM_PLL];

And Structure cyha_clock_t has deprecated two elements:

cy_en_divider_types_t div_type; /*!< Deprecated */
uint8_t div_num; /*!< Deprecated */

But in corespondent C source code cyhal_clock.c the function cyhal_clock_get, is still defined with 2nd parameter as type "cyhal_resource_inst_t" used in 1.6.0 version

cy_rslt_t cyhal_clock_get(cyhal_clock_t *clock, const cyhal_resource_inst_t *resource)

How to correct this situation ? I can create own structures as workaround.  But I don't wont to modify shared libraries... (to still have possible update in feature)

And for last are there any releases notes for each revision of specific library ? It is a bit of detective study to see what changed.

Radim

Hello I'm using psoc6 WIFI-BT Pioneer Kit

I'm implementing "UART_DMA", but I don't know where to place the callback.

What I want is, for example, when all five pieces of data are received, a callback is called and the result value is returned.

Should I use "Cy_SCB_UART_RegisterCallback()" as the existing UART method?

When implementing "UART_DMA", I would appreciate it if you could register "Callback" or let me know the location.

Thankyou for your reply.

Hi.

I'm trying to use the HAL System Power Management library to put the CM4 to sleep. So far, I've had no luck, and as I have found too many times, there is very little documentation available, and no examples. What documentation exists (e.g. Architecture TRM) is unclear, even suggesting that only masked interrupts can wake up a sleeping CPU.

Here's the environment:

• PSoC 63 with BLE in a custom board.
  • MTB 2.3.0 
  • BSP 2.3.0
  • PDL 2.3.0
  • HAL 2.1.0
• CM4 and CM0+ running FreeRTOS
• Several peripherals in use (BLE, I2C, UART, SPI, RTC, TWPCM, etc.)

1. I registered four callbacks using cyhal_syspm_register_callback(). 
2. I call cyhal_syspm_sleep().
3. The four callbacks are called with state set to CYHAL_SYSPM_CB_CPU_SLEEP and mode set to CYHAL_SYSPM_CHECK_READY. All callbacks return true.
4. The four callbacks are called again with state set to CYHAL_SYSPM_CB_CPU_SLEEP, but this time mode set to CYHAL_SYSPM_BEFORE_TRANSITION.
5. The four callbacks are immediately called a third time with state set to CYHAL_SYSPM_CB_CPU_SLEEP, but this time mode set to CYHAL_SYSPM_AFTER_TRANSITION.

The first problem is that the CPU either doesn't sleep, or wakes up immediately. I disable the RTOS SysTick interrupt in one of the callbacks. I also disable several other peripheral interrupts, and turn off the BLE stack, none of which has made a difference. It's likely that some interrupt is firing, but I can't think of a good way to determine which is the culprit.

The second problem is that the stated behavior, namely that the callbacks are called on wakeup (CYHAL_SYSPM_AFTER_TRANSITION) in the reverse of the order in which they are called on sleep (CYHAL_SYSPM_CB_CPU_SLEEP) does not match the observed behavior.
Callbacks are always called in the same order, even when one of the callbacks returns false in response to CYHAL_SYSPM_CHECK_READY.

Has anyone successfully used cyhal_syspm_sleep() to put one of the CPUs to sleep?

Thanks,

-Nick

I'm struggling to see how I can have a WCO accurate timer using an external 32768 crystal to provide timestamps that can be used with the RTC seconds to get subsecond RTC timestamps of around 1mS.  Is there an example clock configuration for a WCO synchronized 1 KHz timer that can be read in software? 

Good morning:

I am trying to make some  very initial getting started on wifi subjects and I have selected Wi-FI Scan as my "hello world wifi". I installed Modus toolbox, and I am playing with a -062-4343w board. If you think there is a more initial exercise, please just let me know to begin with.

I created a new application with the Wi-fi scan, and I am reading the WI-FI Scan README.md. 

Instructions on the document uses Tera Term but I use Putty. Reference on the text shown  8N1 and 115200 bauds. Is 8N1 something just related to Tera?. I can not see any relation on this parameter to Putty. Could you help me on this?. On other points for Putty are understood (serial line connected to the PC port as COMXX, ...).

1/ I connect the board the the PC, OK.

2/ I do not realy understand if I have to change scan_task.h or just leave it as it is. Please let me know. I a assuming that the file keeps unmodified. This is a first trial, so I just want to see "Something" scanned on the console window.

3/ I open the Putty terminal as defoned above.

Using Eclipse IDE

1/ I select the application, OK

2/ Quick panel,...and download the code to the board.

The PC console  shows:

****************

CE230270 - Wi-Fi Scan

****************

and the Debub windows in MTB shows: Thread #11 1 (Name:Current Execution)(Suspended : Breakpoint)

so it seems that the sw is not scaning and apparently  sttopped because discovered an error.

Last line on Preview vindow in MTB shows ===== Cortex-M DWT registers

Could you please provide me some help on this?

Thanks in advance