PSoC™ 4 Forum Discussions
Hello together,
I am facing some problems with the CY8C4045LQI-S411 IDAC. If I set the range to "RNG_152_4UA" or "RNG_304_8UA" I get the same output resoltion in meanings of Microampere/LSB. The reolution was measured by setting a defined current and charging the same capacity for the same time. So the Voltage of the capacitance (max 4 V using a supply voltage of 5 V) is giving me an indicator for the used current.
The current range is changed using the standard API function of the IDAC component. I checked the "IDAC_Control_Reg" using a constant setting of 6 LSB:
RNG_76_2UA: 0x0340 0x017F
RNG_152_4UA: 0x01C0 0x017F
RNG_304_8UA: 0x0180 0x017F
As I see changes in the upper word, I expect that the range has changed. But the charging behavior of my capacity doesn't change as described, so the effective current is the same. As mentioned, this only happens with the RNG_152_4UA/RNG_304_8UA, all other ranges are working fine.
Calculating the effective current backwards from charging time, capacitance and voltage gives me the resolution of "RNG_304_8UA", so it looks like the devices uses this in both range settings.
Questions:
1.) Is there a description of the "IDAC_Control_Reg" available for the PSOC4000S devices? I din't find it in the register TRM "002-10099 Rev. *E"
2.) Any idea what is going wrong here? Is there any known bug according the two mentioned ranges in the PSOC4000S devices?
Thanks a lot for your help!
Pascal
Edit: Heading changed to be more precise
Show Less
I have a problem when I try to debug a program with a custom board (with a PSoC CY8C4149AZI-S593). It fails with the following messages (especially in elements in bold characters) in the console:
...
** Silicon: 0xFFFF, Family: 0xBE, Rev.: 0x11 (A0)
** Detected Family: PSoC 4100S Max
** The connected device is not available in the device database
** Main Flash size will be auto-detected
** Chip Protection: UNKNOWN
*****************************************
Info : gdb port disabled
Info : starting gdb server for psoc4.cpu on 3333
Info : Listening on port 3333 for gdb connections
Info : SWD DPIDR 0x0bc11477
Info : kitprog3: acquiring the device (mode: reset)...
[psoc4.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x61000000 pc: 0x10000040 msp: 0x20007fe8
** Device acquired successfully
** Programming Started **
auto erase enabled
Error: API not Available in DEAD Mode
Error: failed erasing sectors 0 to 15
** Program operation failed **
I made an update of the MiniProg4 firmware because it appeared to be outdated but this problem remains. I hope that it is not a hardware issue: even if the detected Silicon ID is (probably) incorrect (FFFF), the debugger is able to detect the family (PSoC 4100S Max).
Show Less
I only use the MOSI of the SPI to send data, and there is no need for oversampling, how can I increase the rate of the SPI?
I See the max baud of SPI is 4MHz, and I need it to be 8MHz, the oversample is at least 6, how to config it to 3??
the chip is CY8C4025, thanks.
Show LessHi Infineon.
Could you please let us know how to use external clock instead of internal clock on PSoC 4000S?
Can user use external clock by following 2 steps?
Are there any other steps required to use external clock, such as adding code other than below 2 steps?
If user implement below 2 steps, will the clock source be switched from IMO to external clock?
If user implement below 2 steps, will IMO stop and switch to PSoC operation using external clock?
=========================================================
Step 1:
Check EXTCLK to enable external clock.
Change HFCLK source from IMO to EXTCLK in the pull-down menu.
Step2:
Connect an external clock to P0_6.
=========================================================
Best Regards.
YuMa
Show Less如题,用的软件是Psoc creator4.4,开始时可以识别烧录,接着插在板子上调试,最近插上软件就识别不到,烧录也不行(试了备用的烧录器是OK的),拆开烧录器,无明显损坏痕迹,也不存在芯片发热烧毁(以前有发热烧毁,更换芯片后就OK了),请问社区的大佬们,有谁知道大概啥方向的问题?主要拆开看没啥明显问题,又没电路参考,很难分析有啥问题?
Show LessHi,
In order to solidify the value of the corresponding variable to the corresponding address in Flash when using PSoC, it was added to cm0plusgcc.ld
.eepromConstBlock Address: {
KEEP(*(.EEPROMSection))
} > FLASH
However, after recompiling the code added here, it was optimized. This poses a hidden danger to the software and requires that this function be added frequently.
How to change it like PSOC's firmware, it only needs to be added once and then it won't be optimized, thank you.
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-4/PSOC-%E6%9B%B4%E6%94%B9%E4%BA%86%E9%A1%B6%E5%B1%82%E8%AE%BE%E8%AE%A1%E6%80%8E%E6%A0%B7%E4%BF%9D%E6%8C%81cm0plusgcc-ld-%E4%B8%AD%E6%B7%BB%E5%8A%A0%E6%B7%BB%E5%8A%A0%E7%9A%84%E4%BB%A3%E7%A0%81%E4%B8%8D%E8%A2%AB%E4%BC%98%E5%8C%96/td-p/685955
Show Less如题,昨天使用miniprog3烧录器发现烧录器发热严重,然后拆开外壳发现U12电源芯片发热烧毁,请问有大佬知道该芯片型号多少?,想先换个电源芯片试试,新的还没到。
I use DMA to capture the data from ADC, but the data captured with DMA in release mode and debug mode are different.
The config of DMA is as follow:
Show Less