Browse the Community
The ModusToolbox™ forum includes discussions regarding multi-platform development tools and a comprehensive suite of GitHub-hosted firmware libraries accompanied by thoroughly tested code example applications.
Discussion forum regarding WICED™ Studio related topics.
Discussion forum regarding PSoC Creator & Designer Software topics.
The AURIX™ Development Studio is a free of charge Integrated Development Environment (IDE) for the TriCore™-based AURIX™ microcontroller family. It is a comprehensive development environment, including Eclipse IDE, C-Compiler, Multi-core Debugger, Infineon low-level driver (iLLD), with no time and code-size limitations that enables editing, compiling, and debugging of application code. Combined with numerous code example projects, the IDE can be used to evaluate the powerful architecture of the AURIX™ microcontroller family. It supports Microsoft Windows 10 as a host operating system (OS).
today I tried a simple example to read a pin into status register and failed at build time.
*** ERROR L127: UNRESOLVED EXTERNAL SYMBOL
MODULE: .\DP8051\DP8051_Keil_951\Debug\main.obj (MAIN)
*** ERROR L128: REFERENCE MADE TO UNRESOLVED EXTERNAL
MODULE: .\DP8051\DP8051_Keil_951\Debug\main.obj (MAIN)
Program Size: data=14.0 xdata=96 const=40 code=1950
The command 'LX51.exe' failed with exit code '2'.
Well, the Fitter tells
ADD: mpr.M0037: information: Unused pieces of the design have been optimized out. See the Tech mapping section of the report file for details.
where the report file doesn't give any new/more informations to me. In deed, the generated Status.c contains
#if !defined(Status_sts_sts_reg__REMOVED) /* Check for removal by optimization */
where cyfitter.h holds:
/* Status */
#define Status_sts_sts_reg__REMOVED 1u
All this explains the problem faced me but doesn't solve it since is problem is related to code generation stage ... A documentation search also doesn't brought more clearity.
So, where is a check mark and documentation about those optimization? Optmization on hardware level is a good thing (obvioulsy happened here) but the software is forgotten - how to fix it?
I'm trying to configure one of the ACLK pins to provide a clock to an external device. I've tried adding the following lines but it does not appear to have any affect:
wiced_hal_gpio_configure_pin(WICED_P36, GPIO_OUTPUT_ENABLE, 0);
wiced_hal_aclk_enable(24000000, ACLK0, ACLK_FREQ_24_MHZ);
I could not find anything that explicitly tells the GPIO driver what function I want on the pin, how does it know I want ACLK0 on P36 (rather than P32).
Similar to this question but a different device: CYW20735 ACLK on pin
I'm using CYW43907 eval kit with WICED SDK 6.2.1. I am porting a C based networking application to WICED SDK (FreeRTOS + LWIP) and it uses TCP client-server model for inter-thread communication. My issue is, the "wiced_tcp_connect" API always returns error and communication is not established between the threads. The same threads are able to connect to remote server/client respectively but not to each other. Is there any limitation in WICED SDK (FreeRTOS + LWIP) that does not allow socket connections between threads of same application?Show Less
I have installed WICED-Studio-220.127.116.11-IDE.
I am porting a source code to 43xxx_Wi-Fi project.
Source code which i am porting is already having customized LwIP 2.1.2
In WICED folder also customized LwIP 2.0.3 is present.
I understand from my previous question (with title Upgradation of LwIP to 2.1.2)
in this community that combining these two customized LwIPs is not a recommended
I have decided to keep both the LwIPs.
1.Idea is not to touch LwIP in source code being ported.(As source code not to be changed).
2.And LwIP present In WICED folder to be compiled using 'namespace' after changing all the required
files to .cpp extension.
My concern is with pre-processor directives.
When i search for "#define " directive i am getting 3781 hits in 222 files of WICED LwIP 2.0.3.
These pre-processor macros which may be common in both LwIPs(application LwIP 2.1.2 and WICED LwIP 2.0.3) may either
cause compilation error or runtime error.
Any idea to handle this kind of situation?Show Less
If the customer would like to connect external memory as instruction ROM with CYW43907,
Q1: which interface can the customer use? e,g SPI or other?
Q2: how much is the maximum memory size to expand memory size of ROM by external memory.
Is there any APIs to set the number of MAC retries (retransmissions)?
I am talking about something similar to "iw phy phy3 set retry short 1" in linux.Show Less
How long before the beacon arrival time a station wakes up?
How long a station will stay awake if the beacon is missed?
Where these timers have been defined?Show Less
thanks Show Less
Greetings again Cypress/WICED community!
wolfSSL has received a request to do a demo using TLS v1.3 on a WICED device.
We are looking for input on which device the community would find most useful in addition to features that may be more preferred over others!
Demo Features we'd like commentary on:
- TLS 1.3 on an embedded device with which one:
- Wifi Module (standard SSL/TLS over TCP)?
- Ethernet (standard SSL/TLS over TCP)?
IE Doing SSL/TLS over Bluetooth using the wolfSSL I/O abstraction layer and not using bluetooth protocol
- Possibly taking advantage of on-board crypto (if available)?
- Cipher suites? (Which algorithms would the community like to see running on a WICED device)?
- Specific algorithms? (Stream ciphers, block ciphers, AEAD modes, Perfect forward secrecy... etc)?
- Optimized build? (only showing the smallest footprint conscious features)
- Full Featured build? (Show off everything with no regard for build size)
Let us know your thoughts and feedback!
Kaleb and the wolfSSL TeamShow Less
Running EAP-TTLS security on 1LD module (STM32F412 + CYW43438) and getting less Wi-Fi throughput than expected. Has any testing been done that can provide the RAM and CPU utilization? Would like to know if I'm resource constrained or if there is room for improvement.Show Less