PSoC™ 6 Forum Discussions
Hi, I'd like to know is it right?
When I change bsp mcu target, from default CY8C6244LQI-S4D92 to CY8C6244AZI-S4D93, I can program the kit successfully.
I was expected an error from programmer tool. I'm using ModusToolbox 3.0.
In .hex file how can I check there is right metadata?
Show LessHi,
Understand that this example project "PSoC 6 MCU with BLE Connectivity: Battery Level (FreeRTOS)" works with PSoC 6 BLE Prototyping Kit (CY8CPROTO-063-BLE) EVK - and it is currently working with ModusToolbox version 2.x, does this example project support ModusToolbox software version 3.0? If not, any plan to bring-up this project to support latest ModusToolbox version 3.0?
Thank you.
Show LessI have a project that's using an external sync clock signal that I want to use an input to a counter. The signal of interest is connected to the P7.6 pin. I'm confused as to whether GPIO inputs can be assigned for this function. From the PDL documentation. The TRM for this chip family describes 16 available trigger inputs.
Each TCPWM block has 14 Trigger_In signals, which come from other on-chip resources such as other TCPWMs, SCBs, or
DMA. The Trigger_In signals are shared with all counters inside of one TCPWM block. Use the Trigger Mux registers to
configure which signals get routed to the Trigger_In for each TCPWM block. See the Trigger Multiplexer Block chapter on
page 267 for more details. Two constant trigger inputs ‘0’ and ‘1’ are available in addition to the 14 Trigger_In. For each
counter, the trigger input source is selected using the TCPWM_CNT_TR_CTRL0 register.
I'm not sure if a GPIO signal would be considered an other on-chip resource. For my particular case, the sync signal is connected to P7.6. I attempted to use the device configurator (v4.0) tool, but when I select count_input to be a rising edge, I don't see P7.6 as an available Count signal option.
From the Pins tab of the device configurator, I can set up P7.6 as a digital High-Z input, and then the Digital Output drop down allows me to assign it to TCPWM[0] Counter7, which is the counter I'm attempting to use, but something doesn't seem complete with this.
I also see following 'fixme' in tasks
Task: The personality 'Timer - Counter' instantiated at block 'TCPWM[0] 32-bit Counter 7' does not expose the port line. [CY8C6136BZI-F34: TCPWM[0] 32-bit Counter 7 [TCPWM[0] 32-bit Counter 7]]
Also, since I haven't selected a Count Signal (because I don't see P7.6 as an option, I also have this fix me note
Task: The 'Count Signal' parameter must not be empty. [CY8C6136BZI-F34: TCPWM[0] 32-bit Counter 7 [Count Signal]]
Show Less
Hi,
Framework MTB SDK
Board:PSoc 62S2
I tried connect to hidden ssid by giving only mac address, security type and channel number and SSID len as with zero len and SSID empty string, here BSSID is hard coded for test purpose and made SSID to empty explicitly.
I Used whd_wifi_join_specific to join, in this API I commented SSID length sanity check. after using this am not able connect to hidden SSID,
```
whd_wifi_join_specific: set_ssid result (err 0); left network
whd_wifi_join_wait_for_complete: not ready to transceive (err 33555457); left network
Function whd_wifi_join_specific failed at line 1677 checkres = 33555457
Failed to join AP [33555457]. Retrying...
IN whd_wifi_join_specific
whd_wifi_join_specific: set_ssid result (err 0); left network
whd_wifi_join_wait_for_complete: not ready to transceive (err 33555457); left network
Function whd_wifi_join_specific failed at line 1677 checkres = 33555457
Failed to join AP [33555457]. Retrying.
```
but when I change this SSID as active network in AP, am able to connect. Please let me know if am missing something.
@vsubbiah
Hi,
In we are using PSoC 6 Controller in one of our project, So I tried installing Modus Toolbox in my linux machine as suggested in the user guide. After installation I am trying to create a new application I am facing the below error always. The help will be appreciated.
Loading the manifest data
Loading super manfiest files from all sources
Getting manifests from remote and/or local sources
Processing system manifest 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Downloading super manifest file 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
Finished loading super manifest files from all sources
Finished download of file 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml'
WARNING:Error downloading 'https://modustoolbox.infineon.com/manifests/mtb-super-manifest/v2.X/mtb-super-manifest-fv2.xml' -- Socket operation timed out
ERROR:all super manifests were invalid, no data loaded
ERROR:Manifest loading completed with error.
2 error(s), 1 warning(s)
Press "Retry" to try again.
Thanks
Deepak H M
Show LessIn PDL CAT1 version 2.4.1, there is a define, CY_DELAY_MS_OVERFLOW, that is defined in cy_syslib.h.
However, in PDL version 3.0.0, that define has not been included in cy_syslib.h.
Where does that #define now reside in PDL 3.0.0?
Show LessHello,
i'm trying to minimize the power usage of our Psoc6 based ble-enabled battery-powered pcb. I made use of the ULP mode and lower CPU Frequency and the use of Sleep mode (with timers still enabled).
But i came across a strange behaviour when measuring the power usage in different scenarious. When running the program normally (without debugger attached) the whole pcb is drawing about 2,3mA (combined of all components and the psoc6 included). but if I attach the debugger and run it without a breakpoint (the program behaves the same way), the power consumption drops significantly (to ~ 1,1mA). It doesn't make any sense to me.
Does anyone know why this is like this ? And how can I get the same effect of this "magic power mode" in my application ?
Regards,
Matthias
Show LessHello community members,
I have been using ModusToolBox 2.4 for the last 6 months, but still trying to solve why indexing is not working in ModusToolBox IDE. I have been working with PSoC 6 development boards and writing firmware for the boards, but the different functions, enums, structures, etc. and not indexed within the IDE. I have to go through different source or header files to look at that functions and enums. This is very frustrating for me.
look at those red errors, they are not going anywhere, the code building correctly every time, but the indexing of every file is not working. Please help me to solve this issue. Do I have to change some settings in the Preference window or what, please help!!
Thanks & Regards,
Vivek Karna
Hi all,
MTB3.0 is ModusToolBox 3.0
I have a custom board that works with MTB2.4 (and MTB3.0). Now I'm using MTB3.0 and I'm programming the board. The code is just a couple of lines to blink two LEDs on the board. The LEDs blink just fine. The project is the Dual core empty app with the modifications to the linker files in this post. I also commented out a line in the makefile as indicated in this other post but that gave me "Error: [psoc6.cpu.cm4] clearing lockup after double fault" so instead I changed it to match the size in the script file: "DEFINES+=CY_CORTEX_M4_APPL_ADDR=CY_FLASH_BASE+0x8000U". As I said the LEDs blink just fine. But Eclipse is showing some stuff after programming that I don't know what to make of it. I was expecting a "programming ok" or something like that. Eclipse also opens up a new tab titled "0x190" (picture below). I'll include a copy of the weird text after the picture... it is long.
My question is ... what is that text at the end and why does Eclipse opens the new tab?
Here is the text. I'm including everything that shows up after I click program (kitprog3...). I'm interested to know what the stuff is towards the end. I'll mark it as bold: Thanks.
Started by GNU MCU Eclipse
Open On-Chip Debugger 0.11.0+dev-4.4.0.2134 (2022-09-08-13:07)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
kitprog3 set_latest_version: C:/Users/wgates/ModusToolbox/tools_3.0/fw-loader 2.40.1241
adapter speed: 2000 kHz
adapter srst delay: 25
adapter srst pulse_width: 25
** Auto-acquire enabled, use "set ENABLE_ACQUIRE 0" to disable
cortex_m reset_config sysresetreq
cortex_m reset_config sysresetreq
Info : Using CMSIS-flash algorithms 'CY8C6xxA_SMIF' for bank 'psoc6_smif0_cm0' (footprint 17056 bytes)
Info : CMSIS-flash: ELF path: ../flm/cypress/cat1a/CY8C6xxA_SMIF.FLM
Info : CMSIS-flash: Address range: 0x18000000-0x1FFFFFFF
Info : CMSIS-flash: Program page size: 0x00001000 bytes
Info : CMSIS-flash: Erase sector size: 0x00040000 bytes, unified
Warn : SFlash programming allowed for regions: USER, TOC, KEY
Info : Using CMSIS-DAPv2 interface with VID:PID=0x04b4:0xf155, serial=050A0DF301237400
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 1 SWDIO/TMS = 1 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1
Info : CMSIS-DAP: Interface ready
Info : KitProg3: FW version: 2.40.1241
Info : KitProg3: Pipelined transfers enabled
Info : KitProg3: Asynchronous USB transfers enabled
Info : VTarget = 3.032 V
Info : kitprog3: acquiring the device (mode: reset)...
Info : clock speed 2000 kHz
Info : SWD DPIDR 0x6ba02477
Info : [psoc6.cpu.cm0] Cortex-M0+ r0p1 processor detected
Info : [psoc6.cpu.cm0] target has 4 breakpoints, 2 watchpoints
Info : [psoc6.cpu.cm0] external reset detected
***************************************
** Silicon: 0xE40B, Family: 0x102, Rev.: 0x11 (A0)
** Detected Device: CY8C624AAZI-D44
** Detected Main Flash size, kb: 2048
** Flash Boot version: 3.1.0.45
** Chip Protection: VIRGIN
***************************************
Info : [psoc6.cpu.cm4] Cortex-M4 r0p1 processor detected
Info : [psoc6.cpu.cm4] target has 6 breakpoints, 4 watchpoints
Info : [psoc6.cpu.cm4] external reset detected
Info : starting gdb server for psoc6.cpu.cm0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for psoc6.cpu.cm4 on 3334
Info : Listening on port 3334 for gdb connections
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring the device (mode: reset)...
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x41000000 pc: 0x00000190 msp: 0x080ff800
** Device acquired successfully
** psoc6.cpu.cm4: Ran after reset and before halt...
psoc6.cpu.cm4 halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0000012a msp: 0x080ff800
Started by GNU MCU Eclipse
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : accepting 'gdb' connection on tcp/3333
Info : New GDB Connection: 1, Target psoc6.cpu.cm0, state: halted
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Verifying region (0x10000000, 23768)... Match
Verifying region (0x10008000, 10900)... Mismatch
Info : Data mismatch, proceeding with flash programming
Info : Flash write discontinued at 0x10005cd8, next section at 0x10008000
Info : Padding image section 0 at 0x10005cd8 with 296 bytes (bank write end alignment)
[ 31%] [######### ] [ Erasing ]
[ 34%] [########## ] [ Erasing ]
[ 36%] [########### ] [ Erasing ]
[ 40%] [############ ] [ Erasing ]
[ 42%] [############# ] [ Erasing ]
[ 46%] [############## ] [ Erasing ]
[ 48%] [############### ] [ Erasing ]
[ 53%] [################ ] [ Erasing ]
[ 55%] [################# ] [ Erasing ]
[ 57%] [################## ] [ Erasing ]
[ 63%] [#################### ] [ Erasing ]
[ 68%] [##################### ] [ Erasing ]
[ 70%] [###################### ] [ Erasing ]
[ 72%] [####################### ] [ Erasing ]
[ 76%] [######################## ] [ Erasing ]
[ 82%] [########################## ] [ Erasing ]
[ 85%] [########################### ] [ Erasing ]
[ 89%] [############################ ] [ Erasing ]
[ 93%] [############################# ] [ Erasing ]
[ 95%] [############################## ] [ Erasing ]
[100%] [################################] [ Erasing ]
[100%] [################################] [ Programming ]
Info : Padding image section 1 at 0x1000aa94 with 364 bytes (bank write end alignment)
[ 68%] [##################### ] [ Erasing ]
[ 72%] [####################### ] [ Erasing ]
[ 77%] [######################## ] [ Erasing ]
[ 81%] [######################### ] [ Erasing ]
[ 86%] [########################### ] [ Erasing ]
[ 90%] [############################ ] [ Erasing ]
[100%] [################################] [ Erasing ]
[100%] [################################] [ Programming ]
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring the device (mode: reset)...
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x41000000 pc: 0x00000190 msp: 0x080ff800
** Device acquired successfully
** psoc6.cpu.cm4: Ran after reset and before halt...
psoc6.cpu.cm4 halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0000012a msp: 0x080ff800
Info : SWD DPIDR 0x6ba02477
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x81000000 pc: 0x10002776 msp: 0x08001fe0
Info : dropped 'gdb' connection
Hi ,
I have been spending the last few days trying to figure out how to increase the flash size according to the linkers scripts for GCC -Arm compiler.
According to the documentation and a few of the posts this should not be that difficult but it is proving to be an big challenge .
According to the documentation in the dual system design guide,in the CMOP linker script the following should be the correct changes , with 512 byte blocks for the flash
ram (rwx) : ORIGIN = 0x08000000, LENGTH = 0x8000
flash (rx) : ORIGIN = 0x10000000, LENGTH = 0x40000
According to the documentation in the dual system design guide I only need to change the following for the CM4 linker script
/* The size of the Cortex-M0+ application image at the start of FLASH */
FLASH_CM0P_SIZE =0x40000;
However if I change to anything above 0x2000 for the flash on the CM0 both cores stop working .
Compiling does not complain about the changes which seem to indicate its correct but when programming a hard fault gets generated . I am unable to pin point the hard fault and this only happens when the flash is changed in the linker scripts .
[100%] [################################] [ Programming ]
Info : SWD DPIDR 0x6ba02477
Info : kitprog3: acquiring the device (mode: reset)...
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00001f34 msp: 0x080477a8
** Device acquired successfully
** psoc6.cpu.cm4: Ran after reset and before halt...
psoc6.cpu.cm4 halted due to debug-request, current mode: Thread
xPSR: 0x61000000 pc: 0x1600400c msp: 00000000
Info : SWD DPIDR 0x6ba02477
Error: [psoc6.cpu.cm4] clearing lockup after double fault
psoc6.cpu.cm4 halted due to debug-request, current mode: Handler HardFault
xPSR: 0x41000003 pc: 0x8008f3ee msp: 0x080457e0
psoc6.cpu.cm0 halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x080002ba msp: 0x08001fb8
Info : dropped 'gdb' connection
Any assistance is welcome
C
Show Less