AN211293の日本語版を入手したいのですが、Link先が誤っています。

(日本語版のLinkを踏むと、AN210781が開きます)

URLを張り替えてください(もしくは、正しいURLを教えてください)。

http://www.cypress.com/documentation/application-notes/an211293-getting-started-psoc-analog-coprocessor

Hello,

I need help with understanding how to program a PSoC4 chip given our hardware design.

Right now I have a PSoC 4 L-Series Pioneer Kit (CY8CKIT-046).  To program it I use PSoC Creator by pushing the "Program" button and that does all the magic.  However my target hardware is a slat with a few standalone PSoC4 processors: a Linux (Yocto) board (SoM) is connected to one of the PSoC processors (master) via UART and Serial Wire Debug (SWD).  The rest of the processors (slaves) are connected to the master with SWD.  The configuration is captured in the attached image.

My question is: how can I program the master and the slave processors?  At this point I am completely clueless.  Where do I start? What should I be looking at?  How complex is this problem?  How much work needs to be done?

I am fresh new to PSoCs programming and embedded programming in general.  I really appreciate any help that I can get.

Also the hardware design is not set in stone just yet.  If there is anything that we can change to alleviate the problem then our HW engineer would consider it given his restrictions.

Thank you!

Hi,

I have a PSOC4 device with BLE and I want to work in a mode of unauthenticated pairing with encryption and with bonding.

I want to be able to save the bonding key to the flash and I saw in the documentation that only 4 keys could be saved in the flash.

It is also a function to erase the oldest bonded device from the list if its full.

So I want to implement a code that the BLEapplication triggers the code due to a bonding event and I then save that bonded device. If the list is full I should check if that device is already listed in the list and if not then erase the oldest device from the list.

How do I verify that the external device ID that was just paired isn't already stored so that I don't save it twice?

Thanks,
David

Hi sir,

I am trying to install PSoc4 creator 4.1 on 32 bit windows7. but installation getting stuck at license agreement page. after some time it is showing error  "CyInstaller has stopped working". please suggest how to resolve it.

   I am developing a product using the MBR3. The product is looking to sense a user input for (possibly) hours at a time and we want to make sure moderate temperature changes while operating do not cause the output to remain on after the user releases the sensor. However, we have found that the unit has a fairly large change in detected capacitance based on temperature. We are taking steps to mitigate faster temperature changes, although I would be interested in information about mitigating that as well.

     Our main concern right now is that if the product experiences even a very slow temperature change while receiving a valid input it will cause the unit to continue to output even after the user is no longer activating the sensor for very reasonable temperature changes because the baseline has not changed. We have investigated the available options in settings including the auto-reset period but have not found anything to mitigate this problem since we want the output to remain on during the entire user activation and stop only when they release it.

Here are my questions, then:

1. What options do we have with the MBR3 chip to mitigate the change in detected capacitance due to temperature other than lowering the sensitivity?
2. Are there options that becomes available if we upgrade to a different unit to help with the same problem?
3. Is there a solution to the problem of temperature changes causing the detected capacitance to change so much during valid input that it causes false outputs after the user has released the sensor?

Hello,

following issue concerns me:

Our customers receive .hexfiles from us containing the whole application for an PSOC4. The application contains our knowledge, therefore we do not want the customer to get the source code of the application project.

With other microcontrollers, the customer could change parameters in hexfiles on negotiated adresses. But on PSOC4, hexfile merging or changing seems a bit more complex, since the hexfile is extended by the CyElfTool with further metadata. However, the PSOC Programmer returns an error when trying to load an adapted hexfile.

Are there any simple solutions, like re-calculating the metadata of a hexfile by the CyElftool after the customer changed some config values?

Thank you !