WICED™ Studio Forum Discussions

We have found an issue within WICED Studio 6.6 where GKI_find_buf_start() appears to be accessing an uninitized variable. We noticed that following a soft reset the RAM contents are not zeroed. Therefore GKI_find_buf_start() interpretation of the data leads to unpredicted behavior. The behavior tends to vary with changes to our application code, which is why we say it is unpredictable. However, the behaviour remains the same for each build. For example, in one case we found the BLE would not report the BTM_ENABLED_EVT following init.

Our temporary solution, given that fixing the GKI_find_buf_start() function is not an option (black box), the only solution available was to ensure the data is initialised. The solution is then to write zeros in RAM during the initialisation sequence (_start()), which fixes the issue.

    /* Enable CPU Cycle counting */
    CoreDebug->DEMCR |= CoreDebug_DEMCR_TRCENA_Msk; /* Global Enable for DWT */
    DWT->CYCCNT = 0;                                /* Reset the counter */
    DWT->CTRL |= DWT_CTRL_CYCCNTENA_Msk;            /* Enable cycle counter */

    // Reset whole RAM
    memset((uint8_t *)SRAM1_BASE, 0, SRAM1_SIZE_MAX);
    memset((uint8_t *)SRAM2_BASE, 0, SRAM2_SIZE);

@Hello.

I review CYW20706 and  found that I cannot use i2c and PUART flow control. because puart flow control shares i2c.

Or can you tell me how I can configure it?

I am using a RS232 FTDI adapter to download a hello_sensor_app through the HCI interface. The communication goes fine and the minidriver is launched OK but  the log file shows  the module memory has a mistmatch in the bytes writen and read.

I append here the last lines of the log:

A total of 2 contiguous memory areas were filled:

[FF000000..FF000027] DATA (40 bytes)

[FF003000..FF01419B] DATA (70044 bytes)

Download config error trying to verify 40 bytes at address 0xFF000000    (SOURCE:  CONFIG   Configuration data   build/hello_sensor-CYBT_343026_EVAL-rom-ram-Wiced-release/hello_sensor-CYBT_343026_EVAL-rom-ram-Wiced-release.hex) (Data mismatch at address 0xFF000000. Expected byte value 0x01 but device contains 0x66)

Please, help.

Thanks,

I want to wire a CYBT-353027-EVAL to the CODEC MAX 98090 via I2S running the Headset Demo Application.

Try #1: CYBT-353027 is I2S Master

I programmed the Headset app into the BT module and paired it to a cell phone. I wired the I2S to the MAX 98090 Eval Board. I started a music player on the phone. As a consequence, I can hear music in the earphones connected to the MAX 98090. I can also see that there is an I2S BCLK, I2S LRCLK and I2S Data going on using a Logic Analyzer. The LRCLK rate is 48 kHz.

I ended the music player app on the phone an initiated a phone call to another cell phone. The I2S BCLK and I2S LRCLK changed. The LRCLK is now running on 16 kHz. However, there is *nothing* to be seen on the SDIN and SDOUT lines. I disconnected the SDIN and SDOUT lines and, funny enough, there is a signal on the SDOUT line at least.

I assumed, it is pulled to low by the MAX 98090 CODEC.

So I decided to change the roles and make the CODEC the I2S master and the BT module the slave.

Try #2: MAX 98090 is I2S Master

I changed the source code to make the Headset Demo app configure the BT module as I2S Slave and set up the MAX 98090 as I2S master, running the LRCLK at 16 kHz with BCLK set to 64 x fs and an MCLK of 12 MHz.

I checked with the music player app on the phone - it works (although the sound is too loud and clipped).

I tried to make a phone call and again - nothing is on SDIN and SDOUT.

Question: Does this even work?

Which CODEC is recommended to use with the CYBT-353027 to get the I2S working in a bidirectional manner?

Hi,

我想把hci_audio_gateway demo里的hci_ag_cfg_settings里的ble_scan_cfg.high_duty_scan_duration=0设置成永远都在high scan,但是测试下来以后，好像scan了一轮后就不scan了。如下是我的的配置。请帮我确认一下