- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Working with:
Chip: 1LD 43438
Wiced: v6.4
I created 2 platforms with the only difference is one is used with internal flash, and the other one external flash. The files projects are the same.
the ONLY difference in the platform files are the following:
- platform_config.h :
- for the external flash platform, I have this additionnal line: #define USES_RESOURCE_FILESYSTEM
- PlatformwithIntFlash.mk :
- RESOURCES_LOCATION ?= RESOURCES_IN_DIRECT_RESOURCES
- PlatformwithExtFlash.mk :
- RESOURCES_LOCATION ?= RESOURCES_IN_WICEDFS
- DCT_IMAGE := $(OUTPUT_DIR)/DCT.stripped.elf
- FILESYSTEM_IMAGE := $(OUTPUT_DIR)/filesystem.bin
Then I use makefile to build one or this other:
MyApp.PlatformwithIntFlash VERBOSE=1 download run
MyApp.PlatformwithExtFlash VERBOSE=1 WIPE=1 download_apps download run
Solved! Go to Solution.
- Labels:
-
Memory
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
If no WIPE enabled , all can run well, it may be having problems when executing erase act after compile again.
You can enable DEBUG_PRINTF in sflash_write.c to see if any problems happened, I will do same act in my 43438 board.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
So the issue is using resource in filesystem, not on external flash , we can start a snip.scan with download_apps flag to see if all can run well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I get the same result with the snip.scan as with my App:
Running as expected with internal flash platform, and get stuck with external platform after the step "creating packet pools".
Seems the issue comes from my platform files, no ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I compare my platform files with Murata 1LD original files, I disabled the usart6 and associated DMA and IRQ, as this uart seems to be used for debug only and as I don't use it (not connected on my schematic).
Could it impact ?
I also notice a change in build file and openOcd log when I compile with or without WIPE option. (on the left: with WIPE, on the right without WIPE)
- the filesystem.bin is different
- And the DCT seems to not be downloaded without WIPE option:
=> could you detail all the impacts of the WIPE option on compile and download operations ?
As it seems to work on external flash when I remove the WIPE=1 option .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
If no WIPE enabled , all can run well, it may be having problems when executing erase act after compile again.
You can enable DEBUG_PRINTF in sflash_write.c to see if any problems happened, I will do same act in my 43438 board.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello:
I do not think you need to add WIPE to sflash , I have a compare with the log out, I think this is the reason why it will fail in the begginning.
left is ok without WIPE, right side gave wrong parameters.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So the WISE will erase the entire memory, and without WISE only the sector which need to be programmed are erased. Is it correct ?
I remove the wise and it seems to work.
I now have issues to write data to the external flash memory from my App running, but it is another problem I guess.