PSoC™ 5, 3 & 1 Forum Discussions
Hi.
I'm trying to use Cypress SWV component but it doesn't seem to work.
There is nothing to define in it, but nothing comes out of the SWV output (I've checked with oscilloscope) while using printf() function.
Did anyone manage to make it work?
Thanks.
Show LessDear all,
I have a new board based on CY8C5468AXI-LP106 device. After 10-20 minutes the chip gets hot and the power consumption in the external power supply goes from a few mA to hundred of mA and chip gets hot. During this time I can program and debug the board using miniprog3.
I have revised the schematic and checked symbols and footprints of all components and do not see any thing wrong.
I attache schematic and some screenshots of the PSOC Creator if you want to have a look. On the Schematic, FILA_X are digital outputs, and COL_X are analogue inputs going to an internal AMUX/ADC. The Power supply is 9V and with two regulators goes down to 5V and 3V3.
Could you please have a look and check if there is anything wrong? have anyone an idea what can be the problem?
Thanks in advance,
Joaquin
Show LessCSD2X Interrupt のつづきで記載しております。
「CY3280_22X45_SLM」のサンプルプロジェクトを動かしております。
しかし、「_CSD2X_1_L_ISR と _CSD2X_1_R_ISR」の割り込みが発生しません。
※ブレークポイントを置いているのですが、割り込み関数内で止まりません。
これらの割り込みを使用する際に何か、レジスタの設定を変更する必要があるのでしょうか?
Show LessHello!
I'd like to transfer bulk data to SPI slave of EEPROM via PSoC 5LP (CY8C5888LTI) using USB (PC -- PSoC) and SPI (PSoC -- EEPROM) with PC firmware of LabVIEW 2017. I couldn't find proper application note and past discussion especially about USB interface with LabVIEW and USB to SPI data conversion. If you know about hints of these tasks, please teach me. Thank you very much.
Best Regards.
D. Kusakari
Show Lesswhere can I find driver for miniprog3 windows10 ?
Thanks a lot for your help
Hello,
I got a error.
"
collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.
"
It looks like the error is pointing no where and i do not understand why this happens.
I have readup on the error and found out that i need to change the toolchain to ARM GCC Generic in the build menu.
After that i located the build in the main folder and now i get this error.
ERROR: Could not locate the binaries for the generic tool chain "ARM GCC Generic" in the selected path "C:\Users\Daan Brinkers\Dropbox\! Stage CLS 04-09-2017 05-02-2018\PSoC programma's\Final Project\Final Project\FINAL PROJECT CY8C5888AXI-LP096.cydsn". The following are the missing binaries: "arm-none-eabi-as.exe"
How can i fix this? I read something about a linking problem too but i don't know how to fix this.
i added the project file as attachment.
thank you for your help in advance.
Best Regards,
Daan
CSD2X_SetDefaultFingerThresholds()について確認させてください。
モジュールデータシートを確認しますと、このAPIはスキャン前に呼び出さなければなりませんと記載があります。
■モジュールデータシート(API)
CSD2X_SetDefaultFingerThresholds()
Description:
Loads the CSD2X_baBtnFThreshold[] array with the FingerThreshold parameter value.
This function must be called prior to scanning if the CSD2X_baBtnFThreshold[] array is not manually loaded with custom values.
しかし、サンプルコードでは、
InitializeBaselines();の後にSetDefaultFingerThresholds();を呼び出しております。
InitializeBaselines();時にスキャンを実行していると思いますが、
スキャン(InitializeBaselines();)後、SetDefaultFingerThresholds();を呼び出していいのでしょうか。
■モジュールデータシート(Sample Firmware Source Code)
M8C_EnableGInt;
CSD2X_Start();
CSD2X_InitializeBaselines() ; //scan all sensors first time, init baseline
CSD2X_SetDefaultFingerThresholds() ;
Hi,
I remember there's a Cypress document which contains a table listing the IRQs which clear their pending flag automatically on ISR entry on a PSoC 4/5 (Cortex M0/M3). Unfortunately I forgot which document contains this table
Anyone knows this document?
Regards
Show LessSo, I've been reading the component docs and looking at the example code for the LED Segment and Matrix Driver, but I still don't understand how it works.
If I use a LED driver chip, usually it has either common cathode or common anode pins and then a bunch of pins for the opposite. Let's say it's common anode. I connect all the anodes of my 8 LEDs to the common anode pin and then connect each LED cathode individually to the cathode pins of the chip. Then you can control the brightness using whatever API the chip provides (usually it does it internally via changing the PWM duty cycle). This makes complete sense.
However, I can't figure out how the commons and segments work in the psoc driver. The docs say that brightness will change the duty cycle of the common; but after hooking up a logic analyzer, it's changing the segment duty cycle instead and the commons duty cycle stays at a specific level somewhere around 10%. Either commons or segment can be set active high or active low. How would I use this for a common anode, individual cathode setup with brightness control of each led?
From the docs I figured that I would need to setup 8 commons and one segment. And from the example project, it shows both set as active high connected to a multi-digit 7-segment LED display. It says nothing about which is the anode and which is the cathode. So I have no idea how I should hook this up to my actual LEDs and what the "active" settings should be. Can anyone help me?
Thanks,
-m
Show LessHi
Have anyone else noticed the accuracy issue with the CountsTo_uVolts method on the delta sigma ADC?
For an input of 2.000V this method is off by as much as 3mV compared to the Volts and mVolts method...
Something Cypress should adress maybe, or have I got it wrong somehow?
Show Less