- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The WLAN firmware CLM download feature breaks compatibility and it also introduces new problems.
Can you provide WLAN firmware without CLM download feature?
I think cypress should provide a build option to disable the new feature if it brekas compatibility,
so existing users won't hit compatibility issue.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
grsr wrote:
The shipped firmware has no CLM built-in and thus a CLM download is required. We are only going to provide a single version of the firmware for a chip, not one with and without a built-in CLM. You could make modifications in WICED to:
1) use wicedfs and wifi FW LUT at the same time while putting the CLM blob in app OR
2) use only wicedfs LUT and make it fail-safe
You should just make your wlan firmware fail-safe.
i.e if wlan_blob missed it should still work.
But I'm a kind of give up now as I have repeated so many times about the issue.
For the past years, I keep saying the imprtance of compatible with older sdk.
But cypress seems keep breaking compatibility and asking your users to *workaround*
sdk issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cypress team,
Now we already move our application to sdk-5.2.0, but due to this issue we cannot
distribute our firmware.
Can someone tell when will this get fix?
Also please don't break compatibility for any reason.
At least you need to provide an option to avoid breaking compatibility with older sdks for existing users.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cypress team
Now I regret move our application to sdk-5.2.0 due to this issue and some new TLS issues.
I tried various ways to get response, however I don't get any valid fix.
Can you at least let me know if you are going to fix this or not.
If you are going to fix it, when will be the fix available.
We cannot wait endless, so we need to know if we have to use older SDK version or if
cypress can provide the fix or provide new release ASAP.
The issue with older SDK is mainly I'm afraid cypress won't provide any bug fix.
Especially, the LTS library is complete changed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
hi mifo
From other thread I got information that the upcoming WICED Studio 6.0 release, scheduled for October 28.
Just one thing I need to get confirm:
Will the new release fix the clm download blob file in resource filesystem issue?
I have descibed the problem here: https://community.cypress.com/message/142764#142764
I do very worry about this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I will need to check on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mifo wrote:
I will need to check on this.
Hi mifo
Any update?
I had reported this for 2 months, but don't get any valid feedback.
You can also check MyCase 00371811, where the only response I got was
1 month ago mentioned that this issue was discussing internally.
(I also have suggestions about addressing this issue, but no feedback at all.)
It's really very frustration about such situation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mifo
From WICED-6.0.0 changelog, I don't find anything related to address this issue.
Can you tell what is the situation regarding this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mifo
So I just test it with sdk-6.0.0 and confirm this issue still there.
This is a *blocking* issue for us and that is why I even emailed to you guys via
private emal and submitted to SPDF system.
Note, I even cannot use older sdk because of KRACK issue.
What do you suggest now?
Can you just provide a build option to disable clm_blob download?
It wont' be too hard.
Sigh, We spent too much time in waitting the fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In WICED SDK 6.0, some resources can be placed in direct resources. So you can place the WLAN firmware, CLM blob into direct resources instead of WICEDFS. You can use the macro INTERNAL_MEMORY_RESOURCES in platform makefile to add the resources as shown below:
INTERNAL_MEMORY_RESOURCES = resources/firmware/$(WLAN_CHIP)/$(WLAN_CHIP)$(WLAN_CHIP_REVISION)$(WLAN_CHIP_BIN_TYPE).bin resources/firmware/$(WLAN_CHIP)/$(WLAN_CHIP)$(WLAN_CHIP_REVISION)$(WLAN_CHIP_BIN_TYPE).clm_blob
A whitespace is used to separate the resources.
grga
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
grsr wrote:
Please check release notes Release Notes: WICED Studio 6.0.0 section 5.3 Infrastructure.
I know the documentaion.
It's wrong. It does not consider the case using
INTERNAL_MEMORY_RESOURCES and WIFI_FIRMWARE_IN_MULTI_APP at the same time.
see, it even won't pass compilation:
build/snip.scan-FreeRTOS-LwIP-43438/libraries/STM32F4xx.a(wwd_resources.o): In function `host_platform_resource_read_direct':
/home/axel/Documents/WICED-Studio-6.0/43xxx_Wi-Fi/WICED/platform/MCU/STM32F4xx/../wwd_resources.c:140: undefined reference to `wifi_firmware_image'
make[1]: *** [build/snip.scan-FreeRTOS-LwIP-43438/binary/snip.scan-FreeRTOS-LwIP-IGS02.elf] Error 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
grsr
We have been blocked by this issue for more than 2 months.
I feel cypress seems still don't figure out the problem at all.
Is it ok to release a wlan firmware works without additional CLM blob file?
Just give people an option to build without breaking compatibily.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
grsr
I workaround the issue by copy wlan firmware from sdk-4.1.3 which does not require additional CLM blob file.
I tried very hard to tell you the problem, really hope you guys can fix it in next release.
Allow disable CLM download feature to avoid breaking compatibility.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
axel.lin_1746341 wrote:
I workaround the issue by copy wlan firmware from sdk-4.1.3 which does not require additional CLM blob file.
I tried very hard to tell you the problem, really hope you guys can fix it in next release.
Allow disable CLM download feature to avoid breaking compatibility.
Hi mifo
Can you confirm if next sdk release can make CLM download optional?
Note, I currently copy the wlan firmware from sdk-4.1.3 as workaround.
However, it won't work because I also have reported other issues regarding
wlan firmware so I cannot use the wlan firmware from sdk-4.1.3 once cypress
has fixes for other issues in new sdk.
I had reported this issue for more than 3 months, but so far still nobody
can tell if next sdk release will fix it or not.
I do very worry about the schedule to get the fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
An internal JIRA has been created to address this issue. I'm not sure where the JIRA resides with regards to priority among the SW Engineering team.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mifo wrote:
An internal JIRA has been created to address this issue. I'm not sure where the JIRA resides with regards to priority among the SW Engineering team.
If a *regression* really takes a log time to fix, cypress should just revert it.
Then cypress can add it back after fix all issues.
This should be the classic pattern to fix *regression*.
The point is I already reported it for more than 3 months, but it's not fixed
in 6.0.0/6.0.1. If it missed in next release, I'll have to wait more months.
In additional, I asked what's the benefit of CLM download features for current users.
Nobody from cypress can answer the question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mifo wrote:
An internal JIRA has been created to address this issue. I'm not sure where the JIRA resides with regards to priority among the SW Engineering team.
mifo
Until now I still don't know the status.
The latest comment was asking me to use OTA2 instead.
However, OTA2 is only working for BCM43907 which is not possible for 43438/4343W.
I feel your engineers are not listening at all, seems they only care about BCM43907 platform.
What I asked was pretty simple:
The clm_blob support causes regression for 43438/4343W, can you either fix it or revert the change?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The shipped firmware has no CLM built-in and thus a CLM download is required. We are only going to provide a single version of the firmware for a chip, not one with and without a built-in CLM. You could make modifications in WICED to:
1) use wicedfs and wifi FW LUT at the same time while putting the CLM blob in app OR
2) use only wicedfs LUT and make it fail-safe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
grsr wrote:
The shipped firmware has no CLM built-in and thus a CLM download is required. We are only going to provide a single version of the firmware for a chip, not one with and without a built-in CLM. You could make modifications in WICED to:
1) use wicedfs and wifi FW LUT at the same time while putting the CLM blob in app OR
2) use only wicedfs LUT and make it fail-safe
You should just make your wlan firmware fail-safe.
i.e if wlan_blob missed it should still work.
But I'm a kind of give up now as I have repeated so many times about the issue.
For the past years, I keep saying the imprtance of compatible with older sdk.
But cypress seems keep breaking compatibility and asking your users to *workaround*
sdk issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
grsr wrote:
In WICED SDK 6.0, some resources can be placed in direct resources. So you can place the WLAN firmware, CLM blob into direct resources instead of WICEDFS. You can use the macro INTERNAL_MEMORY_RESOURCES in platform makefile to
That does not work.
Basically, the wlan firmware is quite big so it's not suitable to be in
direct resources. So in our case, we put wlan firmware in a seperate
section by setting MULTI_APP_WIFI_FIRMWARE.
The INTERNAL_MEMORY_RESOURCES requres GLOBAL_DEFINES += WWD_DIRECT_RESOURCES to
work. Define WWD_DIRECT_RESOURCES then WIFI_FIRMWARE_IN_MULTI_APP won't work.
In additional, using direct resource means it needs 2 copy of the CLM blob.
(One for application firmware, one for factory reset default firmware.)
The most simple solution is don't separate CLM blob.(Just like the wlan firmware in sdk-5.1)