Bonjour, nous avons un projet ou ne devons piloter un véhicule en Bluetooth avec l'application , or nous ne parvenons pas a faire le code, le véhicule est déjà fait, les pins on déjà été associée a la carte Psoc4 BLE , il ne reste qu'a faire le code et l'injecter dans le véhicule et le configurer avec l'appli, c'est très simple et pas long mais nous y arrivons pas du tout.  Nous payons très bien pour les intéressée.

mail: lebsec.per2@gmail.com

On a PSOC4100PS I use a switched-cap VDAC
1.40. The output amplifier can be operated as a "Follower" or as an "OpAmp", configurable in the "Configure" dialog in PSoC Creator 4.2. In my application I need the option to switch this selection during operation. If I configure the output as "OpAmp", I can assign a PIN to the negative input of the OpAmp, if I then reconfigure it to "Follower", the PIN remains, but is internally not connected. Both configurations work great on their own. Unfortunately, the Application Programming Interface (API) does not provide me with a function to do this during operation.
Can we expect an extension of the API to include this function in the future?
Or is there another option? For example by modifying some register values somewhere?

I am trying to set up the code for the BNO055 sensor but I am a bit confused about how to write the .c file. I've been looking at the sample code produced by Bosch (https://github.com/BoschSensortec/BNO055_driver/blob/master/bno055.c) but I only need to read the quaternion orientation and the linear acceleration so I don't what to look for exactly. Any help would be great! Also, any sample codes would be greatly appreciated!

I have an application where I am using the Scan Response Packet to transfer data between my peripheral and a client quickly, without the need for a connection to be established.  This all works fine

But I want to implement this in a Fixed Stack OTA project, and no matter what I try, the Bootloadable code that makes a call to 'CyBle_GapUpdateAdvData' won't compile without an error.  The compiler kicks up an error claiming that that API doesn't exist, even though I've followed all of Cypress's documentation to correctly link the BLE code generated when I compile the Bootloader (which has the BLE component) to the Bootloadable code.

I think (now, keep in mind I'm a hardware engineer let loose on the firmware, so I could well be wrong) that there is an issue in the way the mk.bat and cm0ggc.ld files in the Bootloader are configured, meaning the appropriate API's generated in the Bootloader aren't included when the Bootloadable code is compiled.

I'm having a similar issue with any of the API's that are used to provide Current Time Service functionality, which means the part of my project that needs the CTS functionality is also bombing out at compile time, but I've stripped that out in the short term to focus on trying to establish why the Scan Response Packet API isn't working.

So, my question firstly is:

1.  Has anyone on here successfully implemented an OTA version of a project that utilises the API CyBle_GapUpdateAdvData?

2.  If so, did you have to make modifications to any of Cypress .bat or .ld files to get it to work?

3.  If you did, what were those mods?

Thanks and regards,

Mike

I get the following error
Please teach.

Hello,
I'm using a DMA connected to a RX SPI component.
The descriptor 0 capture just the first byte (just send it to trash)

I use this block to read 150 bytes from a SPI accelerometer
Sometime I need to change some value on the register or read it, so I send just 2 bytes (reg.address and 0x00)

My question is : how to reset the DMA index to restart it as it was initialized ?
I want to reset it before to send my 2 bytes, so like that I can read the data always at the same address.
If I don't reset, I can not to know which address was used for the data (only when I send 2 bytes)
I already try to use the Status of the DMA to get the current index position, but it's doesn't work properly when it was the first data or the last data captured by the DMA.
Thank you
Alex

Hello,

I am using an ECO-based PLL0 clock as HFCLK, but when I execute Em_EEPROM_1_Write (), it automatically switches the clock to IMO.

When I execute Em_EEPROM_1_Write (), it switches from PLL0 to IMO. Can EZI2C and Timer continue to operate without executing EZI2C_Stop () and Timer_Stop ()?

Best regards,

Yocchi