PSoC™ Creator & Designer Forum Discussions
I have a miniprog4 and running creator 4.3, I am having mahjor issues with debugging. First off we are using OTA Fixed stack bootloader, which is difficult to emulate because the tool cannot handle the bootloader, so when you connect via "Attach to running targer" you only can connect and run to break once, then you have to stop debugging and start over, please do not say "just debug your program and then add the OTA" that is wishful thinking and not viable in the field, there has to be some way to effectively emulate this scenario. At least I could see values on the debugger, but that has changed now.
We have tried a miniprog 3 and also 4.2 same results.
We are completely frozen for code development, this must be address immediately.
Since upgrading to 4.3 and the miniprog4 I can get no data on break, and more over, I cannot even stop and restart emulation, I can ONLY, attach to the target and run to a break point, no data is present by the emulator. Below are
1. My created setup
2. Output windown details on a break
3. Image of an attempt to continue after attach and stop, tells me I am inserting break point, but there are no break point set?
1. Environment:
PSoC Creator 4.3 (4.3.0.1445)
Culture: English (United States)
OS Version: Microsoft Windows NT 10.0.18362.0
CLR Version: 4.0.30319.42000
Installed CyInstaller Products:
CY8CKIT-042 PSoC 4 Pioneer Kit Rev*C
CY8CKIT-062-BLE PSoC 6 BLE Pioneer Kit 1.0 Rev.*E
CY8CKIT-149 PSoC 4100S Plus Prototyping Kit 1.0 Rev.**
Cypress Document Manager 1.0 SP1
CySmart 1.3
Peripheral Driver Library 2.1.0
Peripheral Driver Library 3.0.1
Peripheral Driver Library 3.0.3
Peripheral Driver Library 3.0.4
Peripheral Driver Library 3.1.0
Peripheral Driver Library 3.1.1
Peripheral Driver Library 3.1.2
PSoC Programmer 3.28.7
PSoC Creator 3.3 CP3
PSoC Creator 4.2
PSoC Creator 4.3
Loaded Plugins:
Name: Customizer Loader
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Loads component customizers.
Name: Addin Discovery
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Discovers PSoC Creator addins (kits, language packs, etc)
Name: Device Catalog
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Device Catalog Plugin
Name: Documentation
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Adds the topics available in the documentation.
Name: Start Page
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Adds a start page to the framework.
Name: Output Window Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Adds the output window
Name: SCC Manager
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The Source Code Control Manager is the central class used for SCC actions within PSoC Creator.
Name: Symbol, Schematic and SchMacro Factory
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The Symbol and Schematic Factory is used to load, cache, and retrieve symbols and schematics.
Name: Project Manager Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Adds project management related functionality.
Name: GDE Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Loads the Symbol and Schematic editors
Name: Language Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Supports user files in multiple languages
Name: Workspace Factory
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The Workspace Factory is used to retrieve instances of PSoC Creator workspaces.
Name: Project Factory
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The Project Factory is used to retrieve instances of PSoC Creator projects.
Name: Toolchain Manager
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: PSoC Creator Toolchain Manager
Name: ARM GCC Generic
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: ARM GNU Generic
Name: ARM MDK Generic
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: ARM MDK Generic
Name: ARM IAR Generic
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: ARM IAR Generic
Name: DP8051 Keil Generic
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: DP8051 Keil Generic
Name: Device Selector
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Adds a dialog that allows the user to select a device.
Name: File Editor Factory Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Add file editors to the framework.
Name: Transport Framework
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Provides a generic device communication framework for use by other plugins.
Name: Debugger Core
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The Core Debugger provides an architecture independent framework for the common debug features.
Name: PSoC Debugger
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Provides debugging support for the different PSoC families through a GDB back end.
Name: FM Debugger
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Provides debugging support for FM device families
Name: Device IO Transport
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Provides device IO support for Cypress devices though PSoC Programmer APIs.
Name: Serial Transport
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Provides basic serial device support for the rest of the tool.
Name: Bootloader Host
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Provides a host tool to perform bootloading operations.
Name: Background Elaborator
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: PSoC Creator Background Elaborator.
Name: TypeCache Factory
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The TypeCache Factory is used to retrieve instances of TypeCaches.
Name: PSoC Fitter
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: PSoC Fitter Plugin
Name: FM Fitter
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: FM Fitter Plugin
Name: DWR Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Registers resource editors with devices.
Name: DMA Wizard
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Enables quick and correct development of applications that use DMA.
Name: Tuner Plugin
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: Manages custom component tuner executables
Name: Notice Window
Version: 4.3.0.1445
Company: Cypress Semiconductor
Description: The Notice Window displays notices (status messages / errors with managed lifetimes).
2. Output window detail of a break attempt, not the error that no data was received
Info: dbg.M0020: Do you want to delete all breakpoints?
YES
Continuing target program
The target program has stopped at: file: CyBootAsmGnu.s line: 69 function: CyDelayCycles_loop address: 0x0001BB76
Error '' received while attempting to read memory 0x20002882-0x2000288A
Error '' received while attempting to read memory 0x20002882-0x20002883
Error '' received while attempting to read memory 0x20002882-0x20002883
Error '' received while attempting to read memory 0x20002882-0x20002883
Error '' received while attempting to read memory 0x20002884-0x20002885
Error '' received while attempting to read memory 0x20002885-0x20002886
Error '' received while attempting to read memory 0x20002886-0x20002887
Error '' received while attempting to read memory 0x20002887-0x20002888
Error '' received while attempting to read memory 0x20002888-0x20002889
Error '' received while attempting to read memory 0x20002889-0x2000288A
Error '' received while attempting to read memory 0x2000288A-0x2000288B
Error '' received while attempting to read memory 0x2000288B-0x2000288C
Error '' received while attempting to read memory 0x2000288C-0x2000288D
Error '' received while attempting to read memory 0x2000288D-0x2000288E
Error '' received while attempting to read memory 0x2000288E-0x2000288F
Error '' received while attempting to read memory 0x2000288F-0x20002890
Error '' received while attempting to write memory 0xE000EDF4-0xE000EDF8
Error '' received while attempting to read memory 0xE000EDF8-0xE000EDFC
Error '' received while attempting to read memory 0x20002884-0x2000288C
Error '' received while attempting to read memory 0x20002884-0x20002885
Error '' received while attempting to read memory 0x20002884-0x20002885
Error '' received while attempting to read memory 0x20002885-0x2000288D
Error '' received while attempting to read memory 0x20002885-0x20002886
Error '' received while attempting to read memory 0x20002885-0x20002886
Error '' received while attempting to read memory 0x20002886-0x2000288E
Error '' received while attempting to read memory 0x20002886-0x20002887
Error '' received while attempting to read memory 0x20002886-0x20002887
Error '' received while attempting to read memory 0x20002887-0x2000288F
Error '' received while attempting to read memory 0x20002887-0x20002888
Error '' received while attempting to read memory 0x20002887-0x20002888
Error '' received while attempting to read memory 0x20002888-0x20002890
Error '' received while attempting to read memory 0x20002888-0x20002889
Error '' received while attempting to read memory 0x20002888-0x20002889
Error '' received while attempting to read memory 0x20002889-0x20002891
Error '' received while attempting to read memory 0x20002889-0x2000288A
Error '' received while attempting to read memory 0x20002889-0x2000288A
Error '' received while attempting to read memory 0x2000288A-0x20002892
Error '' received while attempting to read memory 0x2000288A-0x2000288B
Error '' received while attempting to read memory 0x2000288A-0x2000288B
Error '' received while attempting to read memory 0x2000288B-0x20002893
Error '' received while attempting to read memory 0x2000288B-0x2000288C
Error '' received while attempting to read memory 0x2000288B-0x2000288C
Error '' received while attempting to read memory 0x2000288C-0x20002894
Error '' received while attempting to read memory 0x2000288C-0x2000288D
Error '' received while attempting to read memory 0x2000288C-0x2000288D
Error '' received while attempting to read memory 0x2000288D-0x20002895
Error '' received while attempting to read memory 0x2000288D-0x2000288E
Error '' received while attempting to read memory 0x2000288D-0x2000288E
Error '' received while attempting to read memory 0x2000288E-0x20002896
Error '' received while attempting to read memory 0x2000288E-0x2000288F
Error '' received while attempting to read memory 0x2000288E-0x2000288F
Error '' received while attempting to read memory 0x2000288F-0x20002897
Error '' received while attempting to read memory 0x2000288F-0x20002890
Error '' received while attempting to read memory 0x2000288F-0x20002890
Error '' received while attempting to write memory 0xE0002008-0xE000200C
Error: dbg.M0007: The run request failed. Encountered error (Warning:
Cannot insert hardware breakpoint 1.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.
3. creator window showing attempt to restart after halt, no break points were set, and in the watch window you can see blanks in the data fields, they never populate
Show Less
Läuft PSoc Creator langsam (besonders wenn das Projekt auf einem Netzlaufwerk liegt), dann kann es daran liegen, dass bei Aronis True Image 2020 die Funktion "Acronis Active Protection" eingeschaltet ist. Wird diese Funktion ausgeschaltet, dann läuft PSoC Creator wieder ohne Probleme.
Mit freundlichen Grüßen
Andreas
Sincerely yours
Andreas
Show Less
If I go to Tools → Options → Text Editor → Fonts and colors and change font to Deja Vu Sans Mono 8pt for all file types, and then restart PSoC Creator and copy text and then paste it into another program, it has a black background and is unreadable. Somehow changing the font is changing the default background color.
Show LessHello All,
I have noticed something strange in PSoC 6 API files generated by PSoC Creator. As I see it, the PDL does the real work and the API uses customized functions to make the PDL more user friendly. It appears that the API code and header files reference definitions in file cyfitter.h.
Here is the strange part. It seems that, in at least one of my API files, cyfitter.h is not included, nor is it included in any of other included files. Does anyone know how the compiler and the "intelligent" editor in PSoC Creator know these definitions?
The reason I ask is because I am trying to compile the API outside of PSoC Creator, but the compiler (also GCC) can't find the definitions. And as I look closely at the API files, I don't see any way the compiler should be able to find them. So why do the compiler and editor in PSoC Creator not have this problem?
Why am I trying to do this? I like PSoC Creator and am using it to configure my project. However, I can't use PSoC Creator to build and debug the project (I won't bore you with the details unless someone really wants to know). I have to build and debug outside of PSoC Creator. I use a third party tool to bring the configuration from PSoC Creator into my project. However, this tool doesn't import the API, so I have manually copied the API. But it won't compile outside of PSoC Creator.
If anyone can tell me why the API files can compile within PSoC Creator, even though they don't include required definitions, I would appreciate it.
Paul
Show LessGreatings All!
Using a PSOC6 (BLE Pioneer kit) for BLDC control. I want the PSOC to generate an interrupt when the external "ADC_BUSY" pin goes low (I.E. "interrupt on negative edge"). When I place an interrupt in the schematic, the only edge-triggered option that I have is rising-edge. Normally, I would just use a logic inverter gate to fix this, but the logic gate elements seem to be missing in my IDE:
How do I get the logic gates back?
Show LessI am a newbie to management of Em_EEPROM/Flash and trying to get a handle on how best to store/retrieve data. I have the processes for read/write figured out, but management is the question.
I understand that the PSoC6 Em_EEPROM is byte-addressable. I have a data set that I need to manage, about 800 records of 10 bytes each that I also need to be able to search and update where required. Just wondering how best to store the data, whether I should have a 3D array of 80 Rows, each row containing 10 x 10-byte records.
Does anyone have examples of 2D/3D EEPROM data management? Is there such method for the above example of having eeArray
When searching through the data, do I need to figure out the physical addresses, or is this done by reference to my array configuration? eg eeArray[7][6] sufficient to retrieve the data?
Show LessThe help says "Incompatible – An incompatible Component version means that the selected Component and version is not compatible with the selected device for your design. PSoC Creator will display a warning or error about this Component version in the Notice List Window."
but it says that for all component versions:
and this is a source code project that doesn't have a device associated with it, so I'm not sure what this means.
Show LessHi,
In order to manage different hardware variants of hardware in a single project (controlled by a config file), is it possible to enable / disable schematic pages created in PSoc Creator using #ifdef?
Something like:
#ifdef i2c-comm
i2c_page = enabled;
serial_page = disabled;
usb_page = disabled;
#endif
#ifdef serial
i2c_page = disabled;
serial_page = enabled;
usb_page = disabled;
#endif
... and so on....
Show LessGreetings!
Using a PSOC6 BLE Pioneer kit with an external 16-bit parallel ADC. I want to trigger the ADC to convert (let's say, at a 20kHz rate), then interrupt on the ADC "done signal", and then read the 16 data pins from the ADC.
On the BLE Pioneer board, there is no group of 16 pins that is contiguous across a single port. In order to read the 16 data pins, I can do one of two things:
1. Read pins in software:
*Pseudo code here*
[In "ADC conversion done" interrupt]:
ADC_RESULT = Cy_GPIO_Read(Port 7, pin 6) | //ADC bit 0
Cy_GPIO_Read(Port 7, pin 7) << 1 | //ADC bit 1
Cy_GPIO_Read(Port 9, pin 0) << 2 | //ADC bit 2
Cy_GPIO_Read(Port 10, pin 0) << 3 | //ADC bit 3.... (do this for all 16 pins)
2. Read pins from two "8-bit" Status registers in the Creator schematic:
[In "ADC conversion done" interrupt]:
ADC_RESULT = StatusReg1_Read() | (StatusReg2_Read() << 8);
Is one of these methods faster than the other? Is there a third option that could read all 16 pins even faster?
Show Less