Welcome to the Infineon Developer Community

In my project there are three interrupts (isr).

The first one is on the button (start), the second one periodically calls a subroutine with "IDAC" using "Timer" to output signal counts. The third also calls the subroutine, but which stops the work (timer is set to Run Mode: One Shot).

These two timers start simultaneously in the start subroutine. But there is a problem, everything works except that the stop subroutine is not called.

I want to note that the timer works, I checked it with a trigger and LED. Also the same interrupt (which doesn't work) when I connect it to the button likewise the connected interrupt "start" it works.

I am using cy8ckit-042 psoc 4 pioneer kit.

Show Less

I need to update CY8C29X66 software hat was written in Assembler using PSOC 4 system. Is there any modern equivalent In Circuit Emulation (ICE) available today to update the software?

Show Less

due to unavailability of the CY8C5488AXI-LP120 and CY8C5467AXI-LP108 chips I designed a new card using psoc 6, in order not to throw away around 80 old boards I would need to complete them with chips that can be one of the two models.
if anyone has boards or components to sell me please contact me urgently thanks.

Show Less

For some context, we have an old board that uses the older SX2 chip. We've made a new board that replaces the SX2 with an FX3 and I've written firmware to make it work. The new board works great.

The thing I'm running into now is that I have the newer cyusb3 drivers installed on the machine, but the older chip worked with older cyusb drivers. Now, I can see the old board with the device manager, and when I try to connect to it, sometimes it works, and sometimes it doesn't.

As far as backwards compatibility goes, should the old board work with the new drivers, and if so, what things can I do to make it more consistent?

Show Less

In working on migrating a project to the newer Anycloud MQTT Client project, I noticed that when I published messages to the client, the MQTT broker would close the TCP/IP socket, thus disconnecting from the client. This is caused by the client not sending a PINGREQ in the allotted MQTT_KEEP_ALIVE_SECONDS time and the MQTT broker assumes the client no longer exists.

I would expect the client to stay connected regardless of Quality of Service, but the broker disconnects occur with QoS of 0. I have yet to see a disconnect when publishing to the client with a QoS of 1.

While this issues exists with version 4.0.0 of the demo project and with the ModusToolbox v2.4.0 toolset, it is reproducible with the latest version of the demo project and version 3.0.0 of ModusToolbox.

To duplicate the issue:

• Create the project as in the Readme.md: project-creator-cli --board-id CY8CKIT-062S2-43012 --app-id mtb-example-wifi-mqtt-client --user-app-name MQTTClient --target-dir .
• Modify config/wifi_config.h to local router
• Modify config/mqtt_client_config.h to local Mosquitto broker (ensures only local traffic) and MQTT_KEEP_ALIVE_SECONDS to 5 (reveals issue faster).
• make build -j8; make program
• Publish to client: mosquitto_pub -h 192.168.4.2 -t "ledstatus" -m "0123456" -q 0

There isn't a disconnect every time publishing to the client with QoS of 0, but I've attached client output, the mosquitto broker log, and a Wireshark capture of where the first publish to the client causes the client to stop making PINGREQs.

In this instance, the broker is 192.168.4.2 and the client is 192.168.4.10. In the Wireshark capture, the last PINGREQ is highlighted, packet 26. In packet 30, the broker closes the socket about 7.2 seconds after the last request which is almost 1.5x the keep alive timeout. The second Wireshark screenshot shows packet 28 with the PUBLISH packet and that it's a QoS of 0 or "Fire and Forget".

The default Quality of Service is set to 1 and when I publish to the client with a QoS of 1, I do not see the disconnect. I also set the changed MQTT_MESSAGES_QOS to 0 for the client, but I still saw the broker disconnect when publishing to the client with QoS of 0.

I noticed a similar problem with version 4 of the demo and v2.4 of ModusToolbox when I add a hardware timer. For some reason, the FreeRTOS software timer used generate the PINGREQ failed to fire and the MQTT broker would disconnect due to a timeout.

Thankfully, it seems that I can work around this issue by changing all of my publishes to a QoS of 1, but it would be nice to use a QoS based on the design and not a work around.

Any help would be appreciated,

Matt

Show Less

We have a Laird Sterling LWB5 WiFi Bluetooth module with a Cypress CYW43353 chip. When streaming audio via Bluetooth A2DP (SBC codec with data rate 300 kbps - 900 kbps), if there is traffic on 2.4 GHz WiFi, then the Bluetooth audio stutters/cracks to the point of being unusable. We have the same problem which was discussed at https://github.com/raspberrypi/linux/issues/1402 for Raspberry Pi 3.

We tried driver version 8.2.0.16 and 10.4.0.10 from Laird. Both have the same problem. If WiFi is on the 5 GHz band then there is no problem. It seems that it is a WiFi Bluetooth coexistence problem inside the Cypress CYW43353 chip and it may be improved in the firmware. I was wondering if there is any update of the driver/firmware with tuned radio coexistence parameters that solve the problem? Thank you very much.

Show Less

i am using AurixDevStudio and following code to init EVADC.

As long as i use this opt. settings everything runs fine.

However, if i switch to these setting, the code gets stuck at 

BR
Thomas

 

Show Less

I am using Creator since the new BLE stack and OTA for MTB is not yet available. My project uses an upgradable stack and a minimal bootloader app. Is there anything that will keep me from updating my Creator based project to a MTB based project using BLE OTA? If it can be done, is there anything that needs to be accounted for on the bootloader app to make sure it will load the BLE stack app and main application app? 

Thanks for the help!

Josh

Show Less

I have been unable to determine how to blow the efuses on a CY8C6144LQI-S4F92. I have tried Psoc Programmer, Cypress Programmer, and JFlash.

The CY8C6144LQI-S4F92 does not appear in the list of mcus that are supported by Psoc Programmer.

With Cypress Programmer, every time I try to program the efuses I get an error and have been unable to find what the error means or how to solve.

I have 2.56 V on the VDD lines. I am able to program the main firmware without issues.

Show Less

Hi Guys

I`ve begun to write a bootloader for my project. For that reason my bootloader has to be able write data in the PFLASH part in the memory. I write a test code to see whether can i write
datas in the Flash memory part. My reference documant was this:

https://www.infineon.com/dgdl/Infineon-AURIX_Program_Memory_Unit-Training-v01_00-EN.pdf?fileId=5546d46269bda8df0169ca89a7cb2567

Unfortunately i couldn't able to write datas in any PFLASH part of memory. But fortunately, I was able to write datas in the DFLASH part. you can see below my example code for flash memory:

uint32_t testArray[64]={
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,

0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,
0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555,0x55555555
};

uint16_t i;

//////////////////////////////////////////////////////PFLASH//////////////////////////////////////////////////77
for(i=0; i<32; i++){
IfxFlash_clearStatus(IFXFLASH_NUM_MODULES);
IfxFlash_enterPageMode(0xA0038000 + i*0x8);
IfxFlash_loadPage2X32(0xA0038000 + i*0x8, testArray[2*i], testArray[2*i+1]);
IfxFlash_writePage(0xA0038000 + i*0x8);
IfxFlash_waitUnbusy(0, IfxFlash_FlashType_Fa);
}

////////////////////////////////////////////////DFLASH///////////////////////////////////

for(i=0; i<32; i++){
IfxFlash_clearStatus(IFXFLASH_NUM_MODULES);
IfxFlash_enterPageMode(0xAF000000 + i*0x8);
IfxFlash_loadPage2X32(0xAF000000 + i*0x8, testArray[2*i], testArray[2*i+1]);
IfxFlash_writePage(0xAF000000 + i*0x8);
IfxFlash_waitUnbusy(0, IfxFlash_FlashType_P0);
}

I think for the PFLASH unit of memory theres a protection and if the code is once executed on the hardware and then no one can write any data in the PFLAH section.
But it should be an setting to diasble the write protection.
I ll be appreciated if someone can help me further?

best regards
Ismail Show Less