cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

New Contributor II

Hi Cypress, and inoue_tomohiro_1742091 from Murata,

Compal project (CTI3) build-in Murata Type1LD module withour external flash, however wifi malfunction after download "test.console-MurataType1LD download run" through WICED-Studio-6.2 with commentout two line in MurataType1LD.mk (*3) in N1- 4629_Type1LD-Quick_Start_Guide_1.3.pdf (page 10) on both [Murata Type1LD Evaluation board with external flash], and [CTI3 Type1LD w/o external flash]

(*3) commentout two line in MurataType1LD.mk

#ifneq ($(NO_WIFI_FIRMWARE),)

#endif

CTI3_without_ExternalFlash.png

Could you please tell me how to build and run test.console without external flash to make wifi work on both [CTI3 Type1LD] without external flash?

After (*3) commentout two line in MurataType1LD.mk with
Starting WICED vWiced_006.002.001.0002
Platform MurataType1LD initialised
Started ThreadX v5.8
Initialising NetX_Duo v5.10_sp3
Creating Packet pools
fail: func=wwd_bus_write_backplane_value line=613
fail: func=wwd_bus_sdio_download_firmware line=801
Console app
> status
WICED Version  : Wiced_006.002.001.0002
Platform       : MurataType1LD

Many thanks.

Caspar

0 Likes
Reply
1 Solution
Moderator
Moderator

If total bytes is not larger than internal memory, the application should work fine. If the memory size overflows, the download process itself will throw an overflow error message and quit, If you check the tcp_client csv file as attached in the previous interaction, you can find from row #3281 WiFI FW binary is placed from the starting address of 0x080dae04, which comes under the internal flash memory range (0x0800 0000 - 0x080F FFFF) of STM32F412. You can verify the same for CLM_BLOB as well from row #3003 0x08076628 which also falls under the internal flash memory range. Hope this helps!

View solution in original post

9 Replies
Moderator
Moderator

Can you modify RESOURCES_LOCATION ?= RESOURCES_IN_WICEDFS to RESOURCES_LOCATION ?= RESOURCES_IN_RESOURCES_IN_DIRECT_RESOURCES? Additionally, please comment out #define USES_RESOURCE_FILESYSTEM in platform_config.h. If you are already doing that, please check whether you are seeing any overflow message in your console while downloading. The error log that you have mentioned is pointing to the fact it's failing to write the NVRAM image to the internal flash, which is most likely occurring due to the space overflow. My suggestion is that instead of trying to download the test.console example, you can try to check the issue with somewhat simpler application; like snip.scan and see if you are receiving the same error.

Contributor

You modified wrong location. Please search this and modify it.

# WIFI_FIRMWARE and WIFI_FIRMWARE_CLM_BLOB are now included into resources

# RESOURCES_LOCATION default to RESOURCES_IN_WICEDFS. But can be optionally config to RESOURCES_IN_DIRECT_RESOURCES

# WARNING: Config RESOURCES_LOCATION to RESOURCES_IN_DIRECT_RESOURCES will build firmware and blob to into main application

# and may cause internal flash to overflow

RESOURCES_LOCATION ?= RESOURCES_IN_WICEDFS

New Contributor II

Hi mifo​, inoue_tomohiro_1742091

Would you please tell me how to know the way # WIFI_FIRMWARE and WIFI_FIRMWARE_CLM_BLOB are now included into resources ? and how wiced download wifi firmware, and wifi firmware clm blob files into DUT.

I follow two steps, and wi-fi can scan.

1). N1- 4629_Type1LD-Quick_Start_Guide_1.3.pdf

(*3) commentout two line in MurataType1LD.mk

#ifneq ($(NO_WIFI_FIRMWARE),)

#endif

2). follow Re: SDK 6.2.1 OTA appears to be broken

\WICED-Studio-6.2\43xxx_Wi-Fi\platforms\MurataType1LD\platform_config.h  (attached)

#ifndef WWD_DIRECT_RESOURCES

#define USES_RESOURCE_FILESYSTEM

#endif

CTI3_Type1LD_WiFi_Scan.png

0 Likes
Reply
Moderator
Moderator

Request you to kindly check the previous comments. You have to change RESOURCES_LOCATION ?= RESOURCES_IN_RESOURCES_IN_DIRECT_RESOURCES in your MurataType1LD.mk which might cause internal flash to overflow. To check whether the wifi FW and clm blob has been correctly placed in the internal memory or not, you can first look for config.mk created in the build directory and look for the map file as well.

New Contributor II

Hi rroy​,

1). Did "RESOURCES_LOCATION ?= RESOURCES_IN_DIRECT_RESOURCES" declare if not assign any value to RESOURCES_LOCATION, RESOURCES_LOCATION would be RESOURCES_IN_DIRECT_RESOURCES ?

2). How to check whether the wifi FW, and clm blob has been correctly placed in the internal memory ? (attached config.mk) please kindly help  to provide me the way to check it.

3). How to check memory partition for those build image okay for internal memory ? (attached snip.tcp_client-MurataType1LD_map.csv)

Many thanks.

Caspar

0 Likes
Reply
Moderator
Moderator

Hi caspar_tsai_3766536​,

If you check the line #580 in the config.mk attached in your previous response, you can find out that the resources are placed in internal flash only (i.e DIRECT_RESOURCES). Unfortunately, the csv file that you have attached seems to be an invalid file. I have attached  a valid one compiled with RESOURCES_IN_WICEDFS option here where if you search for firmware, you can find out the memory location where FW, Blob are placed.

New Contributor II

Hi rroy

Okay

Dose that mean my project is running in internal memory while RESOURCES_LOCATION  := RESOURCES_IN_DIRECT_RESOURCES include WiFi FW(43438A1.bin), and 43438A1.clm_blob ?

Attached "snip.tcp_client-MurataType1LD_map.csv" again, please take a look.

How to well know the memory size in internal memory or external flash in .cvs ?

In snip.link_status-NEB1DX_01_map.csv  TOTAL (bytes) = Flash(124497)  + Static RAM(48424) = 168.868 Kb

In snip.tcp_client-MurataType1LD_map.csv Did TOTAL (bytes) = Flash(852386)  + Static RAM(78504) = 909.072 Kb

If TOTAL(bytes) not larger than internal memory, did everything work well with internal memory ?

Many thanks.

Caspar

0 Likes
Reply
Moderator
Moderator

If total bytes is not larger than internal memory, the application should work fine. If the memory size overflows, the download process itself will throw an overflow error message and quit, If you check the tcp_client csv file as attached in the previous interaction, you can find from row #3281 WiFI FW binary is placed from the starting address of 0x080dae04, which comes under the internal flash memory range (0x0800 0000 - 0x080F FFFF) of STM32F412. You can verify the same for CLM_BLOB as well from row #3003 0x08076628 which also falls under the internal flash memory range. Hope this helps!

View solution in original post