PSoC™ 4 Forum Discussions
Hi All,
I am working on CY8C4248LQI-BL583. I am able to run an OTA boot loader and UART boot loader separately,
I want to combine the 2 boot loaders into one project so I will be able to load my project via UART or via BLE,
Did someone create such a boot loader? What is the way to combine 2 boot loaders?
Thanks in advance
Show Lesshello,When i program to 481,it stopped,why?
Hello, my name is Matthias Roth, I'm a senior Software Developer and new to the Cyble-022001-00 chip.
For a customer I'll try to implement an application where I basically need to read 2 rpm Signals and send both on request from a BLT Master.
- which pins do I use for the RPM signals?
- I have tried to configure a digital Pin as input for a counter with Psoc Creator 4 TopDesigne.cysch but failed. Only possible Configuration is Timer Counter with an clock source. Which I don't have / don't need.
- Is ist possible to configure a Port as RPM input for a counter with Psoc Creator 4 TopDesigne.cysch if so how?
- which computer chip is used at Cyble-022001-00 (for example atmel ATXmega), can I use the components(counter) of this chip directly without graphical configuration tool of Psoc Creator 4. Where can I get all necessary specification for the chip?
Thanks in advance
Matthias Roth
Show LessHi folks!
I am working with the CYBLE-022001-00 module. So I have my firmware and it compiles perfectly fine in the PSoC Creator. Unfortunately the Creator doesn't support STLink v2. So I tried to export the whole project to uVision. I have only uVision 5. But this export is still in Beta. When I compile my project in uVision I get the error:
.\UVBuild\230VSwitch.sct(7): error: L6236E: No section matches selector - no section to be FIRST/LAST.
So sadly no programming for me right now.
Can anyone tell me if they managed to use and STLink v2 to program the PSoC and how? If not so, can anyone help me with the uVision compilation error? I do not want to use uVision that bad, but I think it should work with STLink, so yeah that's my best option right now, I feel.
Thanks in advance!
Peace Noah
Show LessHello,
I work with a self made PCB. My CYBLE ship is a CYBLE-022001-00. On my PCB, i have a male header of 3 pins for programming (SWDIO, SWCLK and GND ). I know normally we need 5 pins, but the board is self powered and we do not use the XRES pin.
I would like to program it but i don't know how to do it. In fact, i do not have programmer like MiniProg3. I have been told that with my CYBLE-022001-00, i do not need programmer because it is already integrated. But i am a bit septic. In Psoc creator, we have to choose a programmer among the list ( KitProg, KitProg2,MiniProg3...) but assuming CYBLE-022001-00 has its own, no one in the list is suitable.
I thought of using PSOC Programmer, but first i have to link the CYBLE-022001-00 to my computer. I have been told that it was possible using a USB cable. I should denude the extremity and plug the right wires to my header. It looks like a bit extreme, but assuming it works, then, i should use the bootloable and bootloader components in two differents projects, right ? I am quite lost as you can see. I forgot to say that i have the CY8CKIT-042-BLE kit. I hope someone will be able to guide me !
Best regards,
Karl
Show LessHi there,
I made a project on the Psoc 4200 (non ble version) and I want to move it to Psoc4 4200BLE, so I did the following:
-changed target device
-updated components
-changed the pins (I looked at the board and shield and 'matched' the pins) both for the shield and leds and proximity loop, also chenged the target for the rgb led (as I am using it in my project)
My project runs based on a 1ms task that calls 2 sensors and interprets the movement (on one axis) as swipe or swipe & hold or reset. Based on what it detects it drives a state machine and that way I call the appropriate functions for what I want to do.
What I want to do with the 4200ble send those commands (as a uint8) via BLE from CySmart (next step being an phone app). What I want to get is a behavior like this: I send 1 I want to execute the command X, if I send 2 command Y, etc. all while my original program still works and it reads for gesture input via Proximity shield.
I looked at the Cypress Youtube video "How to Create a PSoC BLE App" and I just added in my project a BLE component and configured it in a similar way (my service should just read one value, and according to it register a gesture and then call the appropriate function) and also I wrote the code as showed in the video (for the Handler).
Now, my problem is that nothing from my original project works anymore, not the Proximity Shield(LEDs don't light up when I hover my hand above and not sensors are red to register gestures); the BLE component sort of works, only that sometimes (like 4/5 tries) it will display the error message "Exchange GATT MTU Size timed out"(gpm.M0117) and also it will fail to reconnect after I disconnect.
My reading gesture is based on task (for now I decided to call it every 1ms) and my BLE handler (via "CyBle_ProcessEvents") is called each 100ms.
What should I do? Is there a compatibility problem with the shield working in the same time with the BLE? How do I configure the Psoc4200BLE to work with that shield?
Where do I find some example code on how should I configure and write some code so that the BLE will just recieve one number and send it to some function that will do something?
Show LessOK, so I'm trying to do a PSoC4 BLE device that has a fair number of blocks, and I seem to have run out of control cells. I'm using a SCB UART, SCB I2C and UDB SPI, the SARMUX ADC, 2 op amps and the 4.2 BLE Stack. I'm trying to add switchable gain by adding 2 AMUXes, but when I do that, the placer fails with no useful error messages (i.e. it just says "the placer has failed" and refers me to the placer section of the .rpt file which, of course, just says the same thing). If I remove one of the AMUXes, it works, and the rpt file shows control cells at 100%.
If I replace the AMUXes with hardware AMUXes and tie the select line to ground, it builds, but then I'd need to add a control register block so I can affect the select line, and when I do that, I still run out of control cells.
So my conclusion is that I've run out of control cells.
I can use virtualMuxes and have two versions of the firmware, but it seems ridiculous to OTAP 100K+ of Flash in order to just reconfigure the switching fabric. I'm guessing if I dig deep enough into the TRM, I can figure out how to do that via registers... but if it's as simple as that, why can't I do it dynamically via a switchable virtual MUX block?
Or is there some other way somebody can think of to recover control cells, or avoid needing them?
Thanks!
---
LATE UPDATE:
I managed to get this working. It wasn't a lack of control cells.
Basically, the solution was to leave the defined op amp pin unallocated and have neither of the AMUX inputs go to the pin that is specified for the op amp. Instead, I picked two unrelated pins for the AMUX inputs -- they were yellow instead of green in the pin map.
Then I let the switching fabric route those to the AMUX and thence to the opamp. I guess it makes sense-- if you're already using the external pin that's specific to that opamp as a MUX input, nothing else can use it. But not obvious, and there were two error messages-- one of them wrong ("out of control cells") and the other one useless ("sjplacer couldn't find a solution")
Gotta step up the error message quality, Cypress!
Show LessHi,
I have a BLE Pioneer kit and used EZ-BLE PRoC Modules (with CYBLE-012011-00). Configure the Bluetooth, wrote the basic code and enabled for advertisement. With this, I can see my device in phone (using CYSMART application). This gave us the confidence that this can be used for our customer design and got the CYBLE-012012-10 module (basically same part but uncertified), and connected only VDD, VDDR (Radio), Gnd, XRES, P0_7 and P0_6 wires from the module. Used these connection to program from the Pioneer kit and able to program. After this when I power on (giving power to VDD, VDDR and ground to GND pin of CYBLE-012012-10 module) with other pins left open - I see it is detected only my phone (with Cysmart app). No matter what I do, it is not seen in any other phone. I used many other google play store apps to sniff the BTLE device and none of them seems to be recognizing this CYBLE-012012-10 module.
Problem seems weird and not sure, what I am missing. Can you please help me in isolating the problem? Do I need to put other pins of the module into some specific state?
With best regards,
Phani.
Show LessDoes anybody know how to wake up the PSOC4 from deep sleep using a button press? I know were supposed to use the global signal reference component from reading in the forum but, I'm not sure how to use it. Also, do we treat it like a normal interrupt in the code.
Show Less