We have implemented a DRP with the controller CYPD3125 and the Mux PS8743B because the Mux PS8740B is not recommended for new design. The CYPD3125 interface to the PS8743B through the local I2C bus. In a previous conversation I have been told that I need to modify the file datamux_ctrl.c in the firmware project to make it compatible with the Mux PS8743B.
From what I understand there is three tools that can be use to customize the CYPD3125. The EZ-PD Configuration Utility, the EZ-PD CCGx Host SDK and the PSoC Creator. Can you give me a brief description of each of those tools? What is the purpose of each one?
What tool do I need to modify the file datamux_ctrl.c and compile the firmware? I assume it's the EZ-PD CCGx Host SDK.
Where can I get the default project of the CYPD3125? Is it that same that is use for the CY4531 EZ-PD CCG3 Evaluation Kit?
Thank you for helping us.
The PSoC 6 lists 3 XTAL's Core, RTC and BLE, as these take up more or less same board space as the psoc itself, I wonder if there are any ways to omit the bluetooth xtal, i.e. clocking it using the same MHz XTAL used for the core!?
In the hardware guide (AN218241) it simply says
> An external 32 MHz crystal is mandatory for proper BLE operation.
Basically any ways to reduce the number of crystal oscillators is what I'm after. i.e. skipping the ECO and instead rely on a sub 20ppm xtal for BLE and have it on all the time feeding other parts of the system.
...option 2 would be to go for some 3-in-1 mems oscillator at the cost of mems + added power
any ideas?Show Less
I try to use Charge Pump that can get in the Paper(AN60580)
but there is no spec of current.
so i ask to you, How much current does Charge Pump supply?
SIO sink current is 25mA, therefore maybe 25mA is maximum current.
is it true?
And if you know, how increse maximum current, please reply.
Thank you.Show Less
I am upgrading a design from using the Cy8C4246AZI to the Cy8C4248LQI-BL573 or BL583. In my Cy8C4246 design I have an IR receiver module connected to the wakeup pin P0.7. Internally this pin is configured as an interrupt (IR_Input) and connected to the capture input of a Timer Counter. The interrupt is derived.
During normal operation, when I receive an interrupt on this pin I start the timer to measure the pulses so that I can decode the IR signal received. I also have a storage mode for this device where I use Hibernate and the IR signal is used to wakeup from Hibernate. I maintained the same external hardware but now I am using the Cy8C4248LQI-BL573 and want to also be able to use the -BL583. I connected the IR input to the wakeup pin P2.2 but I am not able to compile. I receive routing errors and if I delete the connection from the pin to the Timer Counter capture input it will compile without errors.
I can't attach my project as it is because it is code for my customer. I am using PSoC Creator 4.3 with PDL 3.1.1. Both devices are from the PSoC 4 family so why does it work on the 4200M devices and not on the BLE devices?
I do not have BLE active yet. I am just getting the existing project running and will incorporate BLE later. We are upgrading the hardware first because we couldn't buy the Cy8C4246.
I have a fresh install of ModusToolbox 2.4 on my Mac running Big Sur OS. I did a git pull of the Amazon FreeRTOS project and based on AWS tutorial info, I imported the aws_demos project into my running IDE.
I get an error in the console almost immediately:
10:37:00 **** Build of configuration Debug for project aws_demos **** /Applications/ModusToolbox/tools_2.4/modus-shell/bin/make CY_MAKE_IDE=eclipse CY_IDE_TOOLS_DIR=/Applications/ModusToolbox/tools_2.4 CY_IDE_BT_TOOLS_DIR= -j15 all Tools Directory: /Applications/ModusToolbox/tools_2.4 INFO: The path '../../../../../vendors/cypress/MTB/psoc6/psoc6make' set for CY_BASELIB_PATH does not exist. Attempting to use BSP provided path instead Makefile:187: ../../../../../projects/cypress/make_support/afr.mk: Operation not permitted /Applications/ModusToolbox/tools_2.4/make/startex.mk:398: *** Build support for the target device not found. Run "make getlibs" to ensure all required build and code dependencies are present.. Stop. "/Applications/ModusToolbox/tools_2.4/modus-shell/bin/make CY_MAKE_IDE=eclipse CY_IDE_TOOLS_DIR=/Applications/ModusToolbox/tools_2.4 CY_IDE_BT_TOOLS_DIR= -j15 all" terminated with exit code 2. Build might be incomplete. 10:37:00 Build Failed. 2 errors, 0 warnings. (took 159ms)
I can't understand the source of this error.
Any help appreciated.Show Less
I am attempting to use the write buffer programming process to write all 256 16-bit words with the same constant value as part of a device sanitization process. I know the command sequence to run the write to buffer process but I have not had success in simulation. The unlock and setting commands are issued correctly, as is the following writes to all 256 buffers, but the ready signal goes low halfway through writing to the buffers and stays low indefinitely. Attached are three waveform screengrabs of what I am doing and seeing in simulation.
Picture1: Two unlock commands, issue "write to buffer" command at sector address 00, issue number of locations (255) at sector address 00, start loading address/data pairs
Picture2: Ready signal going low halfway through buffer address/data writes
Picture3: Finish buffer address/data writes and issue "write buffer program confirm" command at sector address 00Show Less
In order to respect our cybersecurity requirements, I need to disable the support for TLS 1.0 and TLS 1.1, only keeping TLS 1.2.
I've noticed that this configuration is made from wiced_default.h
However it comes with a comment
/* Note: Please don't try to change TLS MINOR VERSION MIN & MAX values, * as few wiced prebuilts are compiled using below values changing the values can cause issues * */ /* TLS major version is assumed to be 1 */ #define WICED_TLS_MINOR_VERSION_MIN (0) /* Refers to TLS version 1.2. Values for TLS Versions: 0 ==> TLS v1.0, 1 ==> TLS v1.1, 2 ==> TLS v1.2 */ #define WICED_TLS_MINOR_VERSION_MAX (2) /* Refers to TLS version 1.2. Values for TLS Versions: 0 ==> TLS v1.0, 1 ==> TLS v1.1, 2 ==> TLS v1.2 */
What would be the correct approach to disable TLS versions that are under 1.2?
I am trying to use the FX3 SlaveFIFO in 32-bit mode for automatic DMA transferring. I am able to fill up the buffers and send data to the host, however I noticed half of each of the 32-bit words are missing. This leads me to believe it is operating in 16-bit mode.
Am I missing a configuration somewhere? Note I have setSysClk400 set to True.
For reference, see main C source file that implements this. The project is a modification of AN75779 firmware, and uses the GPIF design from AN65974.
We are testing WHD with Sterling-LWB5+ (CY4373E) and we have the following issue. In whd_wifi_on() country code setting fails and we get "Could not set Country code" error.
Tracing shows that whd_thread_func() puts the device to sleep (KSO disable) and takes the transceiver semaphore with timeout CY_RTOS_NEVER_TIMEOUT. After this point, the card interrupts are missed and there is no activity on the wifi task.
To test that the issue is with card interrupts when KSO is off, we have tested the following case. We used whd_ensure_wlan_bus_is_up() in the main task loop and set CY_RTOS_NEVER_TIMEOUT to, for example, 10ms so that we are periodically waking up the device. Then, the card interrupts are received and the country code setting succeeds. Also, whd_wifi_on() completes successfully. We have tested with WHD v2.0.0 and v1.94.0.
What could be the root cause for this issue and how could we mitigate it?
I recently looking into the 4700S series, but i found that there are not much code example for this series, only 8 of them.
I tried to follow those examples from PSoC4 such as 4200 series etc. but they are significantly different now.
Is there any resources you can share?
The way Cypress update or extend your component library is quite hard to do the sustaining process. All the functions and components are part specific, which is not quite user friendly, just my opinion.
Anyway, please see if you can share any helpful tips. Thanks!