I am working with the CYBLE-416045-02 chip (with CY8CPROTO-063-BLE KIT) but i am declaring a function in my .h file as the following:
uint8_t WriteCommandPacket(uint16_t cmd);
and the user can send differents commands:
#define CMD_WATER (0x3608)
#define CMD_ALCOHOL (0x3615)
#define CMD_STOP_MEASUREMENT (0x3FF9)
#define CMD_SOFT_RESET (0x0006)
#define CMD_READ_I (0x367C)
#define CMD_READ_II (0xE102)
it is why i am using the uint16_t type to send this command. But the PSoC Creattor 4.4 is telling me the following error:
masterI2C.h:68:9: error: conflicting types for 'WriteCommandPacket'
uint8_t WriteCommandPacket(uint16_t cmd);
The strage thing that i can use this type inside of the functions
Can someone help me out?
GPIO LED on my PCB on when connected to programmer debugger MiniPro4 but cant toggle RGB LED on PCB
I am new to PSOC 6 microcontrollers, I have used ST, ATmel and Microchip and ATSAM ARM processors.
I am using a CY8C6347FMI-BLD53T and have 5 pin connection for programming and debugging.
See attached for program connection, LED connection and software connected to 5 of my PCBs with programmer debugger MiniPro4,
I watched the 101 video and did the same software set up, just changed micro type and pin connection.
Connects to my PCB, my Green LED on my PCB switches on when programming.
LED does not flash as per code
I managed to have two Apps (each with 2 cores) in the Psoc6 flash memory, How can I start the second App from the first one (I'm trying from the main() of the M0+)?
the first App start at 0x10000000
the second start at 0x100f0000
I tried SwitchToApp(0x08002000, 0x100f0000); from the cy_dfu.c but it triggers a HardFault
static void SwitchToApp(uint32_t stackPointer, uint32_t address )
__asm volatile(" MSR msp, %[sp]\n"
" BX %[address] \n" : : [sp]"r"(stackPointer), [address]"r"(address) : "sp", "memory");
I tested also a call to the address of the main() of the second App from the main() of the first App but it triggers a HardFault too
uint32 * p = (uint32 *)0x100f02b1;
fun_ptr= (void *)p;
this is form the map file
0x100f02b0 0x2a4 .\CortexM0p\ARM_GCC_541\Release\main_cm0p.o
the component is CY8C6347Show Less
We are currently working on utilizing both cores of the PSoC 6 (we have only been using the M4 till now). We are planning on running everything on the M0+ aside from some functions that are more complex and take longer to run.
Currently everything is running on the M0+ and it skips over the more complex tasks so the M4 is just sleeping. There are 2 rows that we write to but only one of them seems to work when executed from the M0+.
Is there a reason why writing to a row of flash would cause the device to crash when executed on the M0+ instead of the M4?
Any help would be appreciated.Show Less
I'm trying to find a flash programming solution for production use for our custom board that uses the CYBLE-416045-02. I would like to use a dedicated flash utility with a commercially available JTAG/SWD probe, but those two requirements seem to be mutually exclusive for this chip.
What other options are there? How are others managing this?
I'm hoping that someone would be able to take a look at a schematic for a custom PSoC 6 design (using the CY8C6245 chip) to verify that our design is implemented correctly (schematic PDF attached). A couple things in particular that I was hoping someone with more experience designing around this system could look at:
Thanks in advance!
I am performing a boot loading operation in PSoC6 using a UART Bootloader. App0 is my Bootloader and App1 is the Application. When the App1 size is small the bootloader is working perfectly fine. The linker file is attached below.
But when I am boot loading a bigger App1(Around 1000 Blocks) I am getting this error like mentioned below.
> Sent Data Row 992/1003
> Sent Data Row 993/1003
> Sent Data Row 994/1003
> Sent Data Row 995/1003
> Sent Data Row 996/1003
> Sent Data Row 997/1003
> Sent Data Row 998/1003
> Sent Data Row 999/1003
> Sent Data Row 1000/1003
> Sent Data Row 1001/1003
> Sent Data Row 1002/1003
> Sent Data Row 1003/1003
Finished sending the application to target.
> The application is NOT valid.
Ending DFU operation.
I have attached the Both working and Nonworking linker files below. Please have a look and let me know if anything is missing in this.
Due to project privacy, I can't attach the whole project.Show Less
When PSOC63 is master and 'useRxFifo' enabled we losing data within 28bytes if interrupts are disabled for more than 400msec or so.
Expected Data: 40011900031E030008000102038081828302D002FF020004881001AE
Received Data: 4001198302D002FF020004881001AEFFFFFFFFFFFFFFFFFFFFFFFFFF
When 'useRxFifo' is enabled the MCU suppose to receive up to 127 bytes on its own without intervention firmware right? Why are we seeing this effect for less than 32bytes?
We are planning to disable the useRxFifo, but want to understand just to make sure.Show Less
thanks your supports.
My name is david yu.
I sent a e-mail with the same subject in 2 July.
your reply is very helpful for me.
I also a little question about it.
1. the reflashing speed.
- I compared the two demon software, CE223726 in PSoC creator and emWin_TFT_FreeRTOS in ModusToolbox.
when changing the image, PSoc creator is faster than modustoolbox.
why PSoc creator is fast? I guess this because of RTOS .
Can I speed up the speed changing a image in RTOS?
2. the moving image
- I am trying to show the movie file in tft LCD using the enWinGraphic example file.
but i couldn't do it.
would you tell me the example source code?
i copy the previous e-mail in below
I am an engineer in Seoul, South Korea.
I got an PSoC6 Wifi BT Pioneer Kit with the TFT LCD 2.4 inch.
I am trying to work to show the sypress log using the example source code of the CE225248_DisplayBuffer.
But I cannot.
Would you give me the information for this?
also can you give me the source of the sypress log showing in the TFT LCD?
I use the PSoC creater 4.4 version.
My E-mail : email@example.com
I'm trying to program a PSOC6 using a miniprog4 using JTAG. The only option available is SWD. I've got two PSOC6 on my board, SWD is only for a single device.
Why is the JTAG option grayed out? I've updated firmware. The same issue appears using the Pioneer kit.
I Designed this circuit based on the PSOC6 design guide.
Everything works well on this circuit except the BLE functionality. I made a FindMe program that works on the psoc 6 pioneer kit (powered by CY8C6347BZI-BLD53). However, when I migrate it onto my own design, it does not work. Specifically, the program crashes when I start any BLE functionality, such as calling Cy_BLE_Start(0). More specifically, when I call Cy_BLE_Start(0), other functions such as UART and blinky all stopped working. I tried to enter debug mode, but the play button for debugging is grayed out, and I can't even run the program in debugging mode. I have attached my FindMe project to this pose; any help will be greatly appreciated.Show Less