Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I'm working on a project in Modus Toolbox where we generate a firmware (CY8C4146AZS-S265) and flash the device under Linux using a MiniProg4, and this...
I'm working on a project in Modus Toolbox where we generate a firmware (CY8C4146AZS-S265) and flash the device under Linux using a MiniProg4, and this works fine.
We have to send our HEX file to a manfacturer to be tested/flashed and they only use Windows, but it turns out that Modus generated HEX files are not compatible with PSoC Programmer.
As far as I'm concerned this is completely unacceptable, there should be a warning that a HEX file wasn't created by PSoC Creator and that's it. Having a flashing tool which doesn't support standard HEX files generated by your own toolchain is a very big disappointment.
We can't send the Modus project to the manufacturer in this instance so that's not an option.
I can't find an alternative graphical flashing tool that's easy to use and works with MiniProg4 which I can suggest our manufacturer use.
I found cyhextool.exe, but it's insufficiently documented and doesn't seem able to generate a compatible cypress hex file from a standard hex file, maybe I'm missing something?
I've written my own small Linux tool to create cypress compatible hex files but since the "metadata" section you use is apparently "confidential", I'm stuck here too. I'm very unimpressed that you'd consider a critical part of your development tooling to be "confidential" as though you can't trust your customers to flash their own devices.
I'm looking for one or more of the following solutions: 1. Can you provide me with the correct invocation of cyhextool to turn a standard hex file into a cypress flashable one? 2. Can you provide me with the "confidential" method for generating the metadata bits for a cypress HEX file? 3. Can you provide me with an alternative graphical programmer for Windows which supports flashing a standard HEX file using a MiniProg4 programmer to a PSoC4 device? 4. Can you provide me with a suitable alternative to MiniProg4 which comes with tools which can program a standard HEX file to a PSoC 4 device?
I am into writing a PSoC 3 based program wherein I have to control the period of a wave form using data obtained from UART. I have cre...
I am into writing a PSoC 3 based program wherein I have to control the period of a wave form using data obtained from UART. I have created a program where the data is received and it is converted to an integer value. the problem is I'm not able to use this value outside the "if" structure where i'm formatting the command. for example if I have to maintain an analog value in the output of VDAC for certain duration of time that was specified through UART, this delay is not reflected during the execution. only the initial delay is maintained. the change is not made. I'm new to UART interrupt based programming. I have attached a project file here. it might be an old version of creator. please help me.
We are working on CYBT-413055-02 MOD board which uses CYW20719 (QFN-40) SOC which is coin cell driven application,
This module is going t...
We are working on CYBT-413055-02 MOD board which uses CYW20719 (QFN-40)SOC which is coin cell driven application,
This module is going to in-tract with external MCU for data advertising. Normally CYBT-413055-02 Module would be in sleep mode & we need to do an external wake up (event based), this wake up will normally approx. after every 15 to 20 seconds.
The problem is like this,
This particular module which uses CYW20719 (QFN-40) SOC does not seem to have external wake up pin (BT_DEV_WAKE) is this correct?
However we have alternative CYW20719 (WLCSP-134) SOC seems to have a wake up pin (BT_DEV_WAKE) so,
1. Is there any way in this module to do external wake up by a pin.
2. Can we do a power on reset through GPIO connected to VDD of Module?