Wi-Fi Combo Forum Discussions
请问有没有CYW43907的SDIO寄存器介绍文档,我在调试SDIO host模式时遇到很多问题,没法解决
CYW43907的SDIO host功能是不是没有经过测试?因为我看到以下代码:
另外,我调试遇到很多错误信息,但是无法知道这些信息代表的含义,如下:
sdstd_check_errs: ErrorIntrStatus 0x0001 (clearing), IntrStatus 0x8010 PresentState 0x01ff0400
16: W Reg 0x32, Data 0x1
sdstd_check_errs: issuing CMD reset
08: W Reg 0x2f, Data 0x2
08: R Reg 0x2f, Data 0x0
sdstd_check_errs: requesting abort for function 1 after cmd 53
I Just downloaded &installed
BM-Windows-WICED-Studio-6.6.0.9-IDE-Installer.zip.
As described in document
CY8CKIT-062-WiFi-BT PSoC 6 WiFi-BT Pioneer Kit Guide.pdf
create the following make target:
snip.scan-CY8CKIT_062 download_apps download run
WIKED reported 2 errors:
09:53:26 **** Build of configuration Default for project 43xxx_Wi-Fi ****
"C:\\Users\\leo\\Documents\\WICED-Studio-6.6\\43xxx_Wi-Fi\\make.exe" snip.scan-CY8CKIT_062 download_apps download run
MAKEFILE MAKECMDGOALS=snip.scan-CY8CKIT_062 download_apps download run OTA2_SUPPORT is disabled
Making config file for first time
tools/makefiles/wiced_config.mk:256: platforms//.mk: No such file or directory
tools/makefiles/wiced_config.mk:269: *** Unknown component: CY8CKIT_062. Stop.
make: *** No rule to make target 'build/snip.scan-CY8CKIT_062/config.mk', needed by 'main_app'. Stop.
09:53:26 Build Finished (took 637ms)
How can I solve this problem?
Hello, i'm using wiced studio software , after installing it im not able to get patch files to be added to it.
And in make Target im unable to find TYPE1LD device name.
Show LessWe are using the cyw94343wwcd1_evb. It is not in WICED. Is This platform supported.
We found the strength of BT signal to be too low
As suggested by FAE, want to load path to fix this problem
But after setting the patch, it is found that the patch should still not be loaded successfully
Is it correct to put .hcd in /etc/firmware path?
If patch not found is displayed, what is the possible reason?
Show Less
@ShawnA_01 please modify the bellow change in nx_user.h in netX stack for fragmentation experiments
enable NX_FRAGMENT_IMMEDIATE_ASSEMBLY
please build netx stack with the modified file & build the libraries.
Show LessHello, We loaded the FCC frequency sweeping FW ( wl43909B0) for testing by the lab, but after the initiate command, the signal comes on for a few seconds and turns off.
- Is the FW still correct?
- Are there any new commands?
Show Less
Hello,
I am working with the platform ISM43903_R8_L54. I'm using WICED STUDIO version 6.6, and testing on custom hardware.
While configuring my inputs, I have an input signal on pin 26. According to the platforms SDK I've downloaded, in the file WICED-Studio-6.6\43xxx_Wi-Fi\platforms\ISM43903_R48_L54\platform.c, it comments that the pin 26 should be WICED_GPIO_4.
// eS-WiFi Signal L44 +10/L54
[WICED_GPIO_4 ] = { PIN_GPIO_8 }, //GPIO3 26
However when I configured this input as WICED_GPIO_4, the input signal change was not getting detected.
After some investigation, configuring the WICED_GPIO_11 as the input for pin 26 that I'm testing with seems to have worked.
In platform.c it's indicated that WICED_GPIO_11 pin is "N/A" as below:
// eS-WiFi Signal L44 +10/L54
[WICED_GPIO_11 ] = { PIN_GPIO_15 }, //NA
I've also reviewed the ISM43903_Functional_Spec and the table for GPIO there indicates the following:
Pin No. Type Pin Definition Descriptions
26 I/O GPIO BCM_GPIO9
Is there somehow a mistake in the SDK I have downloaded? Or perhaps have I misunderstood something related WICED_GPIO and PIN number mapping?
thanks,
Jason
I am working on a project built on the ISM43903 using WICED STUDIO version 6.6 . This project was an updated project ported from ISM43362 using WICED STUDIO version 3.5.2.
I have a Green LED on pin 23 aka GPIO 0. Below is the code for platform initialization.
Setup/Initialization code:
led1_init_result = platform_gpio_init( &platform_gpio_pins[WICED_LED1], OUTPUT_PUSH_PULL );
Where WICED_LED1 is defined by
#define WICED_LED1 ( WICED_GPIO_1 )
Where WICED_GPIO_1 appears in the patform_gpio_pins[] array here:
[WICED_GPIO_1 ] = { PIN_GPIO_0 }, //GPIO0/I2C1_SD 23
In the application code, I can set the Green led high prior to wiced_init() is called just fine. After wiced_init is called, control to the GPIO is ignored.
After some investigation, the function index appears to be changing from 0 (PIN_FUNCTION_TYPE_UNKNOWN) to 16 (PIN_FUNCTION_TYPE_GPIO) following wiced_init() calls.
By modifying the platform SDK code, I've managed to work around this by modifying platform_gpio_output_high calls:
/* Lookup the pin internal configuration and current function index value */
gpio_result = platform_pinmux_get_function_config(gpio->pin, &pin_conf, &pin_function_index);
then adding a check for the function type problem, then deinit + reinit as below:
if ((pin_conf->pin_pad_name == PIN_GPIO_0) && ((uint32_t)pin_conf->pin_function_selection[pin_function_index].pin_function_type == PIN_FUNCTION_TYPE_UNKNOWN))
{
gpio_result = platform_gpio_deinit( &platform_gpio_pins_[0] );
gpio_result = platform_gpio_init( &platform_gpio_pins_[0], OUTPUT_PUSH_PULL );
}
Where platform_gpio_pins_[0] is crudly built as
const platform_gpio_t platform_gpio_pins_[] =
{
[0] = { PIN_GPIO_0 },
};
I have searched my project for references to WICED_GPIO_1 and GPIO_0. The results are
- WICED_USB_HOST_OVERCURRENT within BCM4390x subfolder. This application doesn't enable USB.
- I2C 1 SDA - This project uses I2C0, not I2C1.
- #define PLATFORM_FACTORY_RESET_LED_GPIO ( WICED_LED1 )
Is there any other way to determine what might be repurposing or uninitializing this GPIO?
I'd prefer to find the root cause rather than this "hack" of the platform_gpio module.
I haven't found documentation to describe the GPIO control registers for this, but in debugging the code I've determined that a control register must be set in order to configure the function index of a GPIO.
any thoughts, or even documentation to help identify GPIO Control registers and how it's handled would be helpful.
Thanks,
Jason
Show LessI followed this guide to make WOWL work on 43455 with magic packet.
https://community.infineon.com/t5/Resource-Library/Wake-on-WLAN-with-43455/ta-p/246041
After the wakeup, I can't ping the 43455 anymore. Are there steps required to reconnect?
I'm using the Nuttx OS with a slim down version of bcmf_driver for the chip.
Show Less