Hello,
I'd like to set a flag in our bootloader which then should be read by the bootloadable (=application). I can't find anything in the datasheet about this. Is there any standard way of doing it? The metadata doesn't seem to have any custom fields that can be used for things like this.
Thanks, Jacob
Hello, I found a great article that explains how to use a clock output on the PSoC 4:
http://www.cypress.com/blog/psoc-sensei-blog/using-clocks-psoc-4
Scroll down to where it has
"This is not allowed on PSoC 4 since clocks can't be used as data signals. However, PSoC 4 has some new pin capabilities and they allow the clock to be sent directly to a pin. In fact there are a bunch of new clocking capabilities for pins. Right now I'll just take a look at the one that allows this function to be implemented with PSoC 4."
There you will see the component that I can't seem to find in the PSoc Creator. Can someone help me find this "Pins" component?
Thanks,
Joe
Is there a simple example of how to set up I2S code to Tx-only a buffer of canned data to I2S using DMA on PSoC 4200 BLE.
I found a PSoC 3 example that uses a different DMA component.
The DMA examples only offer bi-dir UART, SPI and ADC.
Many function calls, but no explanation of the required/mandatory sequences to implement a simple I2S Tx. So painful.
I have a bootloadable project.
Select project --> Bootloadable_PROJ_NAME Resources to get the Bootloadable_PROJ_NAME.cydwr window.
Using the bottom tab "Flash security". I selected the flash space that is used by the boot loader 1..73.
I programmed the boot loader then used the Bootloader host to load the application (the bootloadable) It all works great.
But we must be sure that the boot loader is safe, before we permanently install it into the sensor.
Is there an easy way to verify that the flash rows I assigned to write protect are actually assigned to write-protect in the device?
Hello,
I have been having concerns about the sleep modes on PSoC. How do I know if a device is ready to be put to sleep? I tried calling CySysPmSleep() but the current still reads about 18mA.
The current reading if I call CySysPmDeepSleep() reads 0mA (have not gotten an accurate reading but at least this seems in the ballpark of what is written in the documentation) but I am unable to wake up the device from deep sleep. If I use debugging, then the device does not seem to go into deep sleep and is back at 18mA.
I am trying to trigger the interrupt through an I2C slave device which sends a pulse when certain conditions are met. I can confirm that the pulse is being sent because I have read the pulse using an oscilloscope. I tried to read the pin that it goes into the PSoC but am consistently getting a value of 0V and no sign of a pulse.
I have also tried using a switch instead of the I2C but am still getting a problem.
Any help would be appreciated. Thanks.
Using EZ-BLE 4100 and GPIO P1(0) configured as pulled-down normally-low input with interrupt set to rising edge and attached to an isr component which is set to DERIVED, the device will not wakeup after going into deepsleep mode. In the debugger it works fine!
PSoC 4.0 Code segment:
isr_SW_Enable();
SW_ClearInterrupt();
isr_SW_ClearPending();
isr_SW_StartEx(&PowerOn);
CyGlobalIntEnable;
CySysPmDeepSleep();
I've tried changing the input to pulled up with falling edge and moving it to a different GPIO, P3(5), with no difference. Why does the same code work without any problem in the debugger but not when programmed as stand-alone?
ps I've decided to use deepsleep instead of the preferred hibernate due to the same problem I had with detecting the pin. What goes here?
Rick
Hello;
I am working with CY8CKIT-042 PSOC 4 PIONEER KIT ,I am interested to store few bytes of data into Flash memory and retrieve when required ,I could successfully write data into the flash memory using the API CySysFlashWriteRow( ),and finding a issue on how to read the stored data from Flash memory .I could not find any API for reading data from Flash memory,is there a way to read the data that has been stored into Flash memory,can someone help me out solving the issue.
Hi.
I would like to be able to generate software interrupts, to run code in higher priority.
Is it possible on PSoC4 (4200M) ?
I can't use UDB's for this project, so using a Control Register connected to an Interrupt component is not an option.
Thanks.
The update SP1 for PSoC Creator 4.0 lists the Em_EEProm 1.20. The datasheet still shows usage for PSoC 3, 4, and 5. I cannot find that component in the catalog for any PSoC4, am I missing something???
Bob
I'd like to play .wav files from the CY8C4247AZI-M485. Application note AN2388 describes how to do this but it is marked as obsolete. Is there a current app note that I can refer to instead?
Hello
i had the following error
E2071: Unable to pack the design into 4 UDBs. See the Digital Placement section of the report file for details. For additional assistance, see the Mapper, Placer, Router section in the PSoC Creator help.
i can't find the report file and i don't know what did i do wrong i am allowed to use 4 timer/counters in cy8c4245 according to the datasheet and i only use 3
i only had this error when i use the counter how can i view the report and how to avoid this erorr
thanks in advanced
Hello,
I developed project for CY8C4146AZI-S423 but I cannot write it to flash using SWD programmer Miniprog3, because on the form "Select Debug Target" of PSoC Creator this chip do not shown. If I try to use PSoC Programmer, the same result - fields "Device Family" and "Device" are not accessible. I try to use Bootloader made my project bootable and using SW1 connected to P0[7] and pressed it before powering the device, but "Bootloader Host" of PSoC Creator told me "Unable read data from the target device". My project developed in PSoC Creator 4.0 Update 1 and I am using PSoC Programmer 3.25.0. The previous device I used is CY8C4125AZI-483 and the device successfully programmed via Miniprog3 and Bootloader with the same project.
Is there any way to program CY8C4146AZI-S423 device?
Thanks in advance
Hi, I am using the PSoC 4M prototyping kit and there are 3 pins for power, VDDIO, VDDA and VDDD.
This post explains nicely the difference between VDDA and VDDD. http://www.cypress.com/forum/psoc-5-device-programming/vdd-vdda-vddd
But what about the difference between VDDIO and VDDD? And also, how would you go about connecting the VDD's together if i am planning to use a 3.3v battery source? If anyone has a hardware schematic on how to connect the 3 power sources, that would be very appreciated. Thank you!
I have setup a project based on the CE210291_CapSense_One_Button example code using a CY8CKIT-042-BLE pioneer kit and a CYBLE-014008-EVAL module. The configuration I need to test requires to enable a shield pin in addition to the Button pin (i.e. sensor), so I have enabled the shield tank (Csh) capacitor in CapSense->CSD_Settings (CapSense_P4_v3_10 component). Now, in the Desig_Wide_Resources->Pins window I am required to setup the modulator capacitor “CapSense:Cmod” and the shield-tank capacitor “CapSense:Csh”. I have consulted the CYBLE-014008-00 datasheet and I understand the module includes a Cmod = 2.2nF (located at port P4_0) and Ctank=10nF (located at port P4_1) , so I have assigned P4_0 port to “CapSense:Cmod” and P4_1 to “CapSense:Csh”. At this point, in the Pin tab window, under the Pin_name section I get a warning icon “Invalid pin assignment P4[0]. This pin does not support ANALOG.” for CapSense:Cmod and another warning icon “Invalid pin assignment P4[1]. This pin does not support ANALOG.” for CapSense:Csh; furthermore, port P4_0 gets assigned Pin 33 and port P4_1 gets assigned pin 34, however the CYBLE-014008-EVAL module only has 32 pins. Any comments on what is the proper way to setup this configuration for the CYBLE-014008-EVAL module?
Hello all,
I'm trying to drive multiple servos using a single PWM block and DEMUX. Normally, I have enough PWM blocks to drive 4 servos. However, there are some applications that we require to use nearly all TCPWM/UDBs. So I'd like to know if it is possible to drive multiple pins with PWM using a single PWM block and DEMUX.
The idea is as follows:
PWM frequency is 50 Hz. Duty cycle on time is around 0.5 ms to 5 ms. So, I thought that I could start pwm on pin 1, wait for a falling edge interrupt. After that, switch to pin 2 and start PWM again with counter reset and new compare value. Same stuff for pin 3 and 4. After we get a final falling edge on pin 4, I write the total elapsed on time to PWM counter and let it generate an interrupt on TC. After TC is reached, the processes loops. So, this should in theory, make me able to use 1 single PWM block and vary its compare match value to drive multiple pins. However, the project does not work as expected. There is much jitter on the servos. Can anyone help me with this issue?
Thanks, in advance.
Attached is the example project that I've been working on.
Hi.
I've got Psoc 4 l-series pioneer kit and I'm trying to use the UART USB example (this SDK http://www.cypress.com/documentation/development-kitsboards/cy8ckit-046-...)
The UART communication wasn't responding in any way so I started going trough the kitprog user guide for this kit (http://www.cypress.com/file/226201/download).
I've used the PSoC Creator ( 3.3 SP1 (3.3.0.7343)) for flashing and debugger works fine.
The kitprog user guide however mentioned updating the firmware for the kitprog and that's not working. If I start up the PSoc programmer (3.25.0.2504) it doesn't contain the CY8C4xxx -family. Should I be able to upgrade the firmware via this tool or is the info in the documentation obsolete? Or is the problem the CCG3 SDK that I had installed before (I uninstalled it before installing this).
Hi.
I would like to get some SWO trace from CY8CKIT-046 PSoC® 4 L-Series Pioneer Kit. I'm Seggert jlink (ultra+) and J-link gdb server.
Is there any instructions how to configure the printf output to swo? I've checked this, but I don't have Keil or IAR workbench.:
http://www.cypress.com/knowledge-base-article/using-embedded-trace-macro...
Hello!
I'm trying to use Emulated EEPROM to store some data and I'm running into the known problem with the Bootloader. After a power cycle my program wont start anymore. I don't own any hardware programmer so it doesn't seem possible to update the Bootloader itself. With the prototyping kit alone it looks like I'm stuck. Or is there another way?
It seems like an unnecessary task to include the Bootloader image in the Bootloadable component this way.
Many Greetings!
Remo
Hi,
My example is next:
unsigned char value=0x10;
unsigned char* US_InQEnd;
unsigned char US_InBuffer[3];
Test_Write(1u);
InQEnd = US_InBuffer; // getting buffer address
*(US_InQEnd++) = value++; // writing at buffer first location
*(US_InQEnd++) = value++; // writing at buffer second location
*(US_InQEnd) = value++; // writing at buffer third location
Test_Write(0u);
I can see Test pin getting up but not getting down. Is there any mistake ?
Thank you,
Asier.
Funny development kit...
I don't find any KitProg driver to use, how to fix it?
Thanks a lot.
