Wi-Fi Combo Forum Discussions
How to change flash memory map to remove SPI flash?
Main purpose is that we would like to put OTA application (no need factory reset APP) in MUC in Flash area like "0x080c 0000"
for no used external SPI flash.
Current SDK does operation with external SPI flash for OTA and Factory Reset App...
but we are making way for no use of external SPI flash .
ex>
In booting time, if flash is cheked as broken in any issues, loader jump to MCU Flash addrss 0x080c-0000 ( OTA application Area)
if there is script for this , it will be very helpful to us or if this option is applied to build target then it is very convient.
//--------------------------------------------------------------------------------------------------------------------------------------------
we are evaluating WiCED SDK 2.4 WCD4 EVB. It seems to be flash mapped as belows
1.) Flash
0x0800 0000 0x0800 3FFF (4K) BootLoader
0x0800 4000 0x0800 BFFF (32K) OTA and User Parameter
0x0800 C000 0x080E FFFF User Application
2. RAM
0x2000 0000 for the Ram addressing.
3. SPI Flash
OTA + Factory Reset APP + Factory Reset DCT
//--------------------------------------------------------------------------------------------------------------------------------------------
- Our target Flash memory Map
0x0800 0000 0x0800 3FFF (4K) BootLoader
0x0800 4000 0x0800 BFFF (32K) OTA and User Parameter
0x0800 C000 0x080B FFFF User Application
0x080C 0000 0x080E FFFF OTA application.
Any comment will be very appreciated
Show LessI have been looking for a wireless chip for an (ultra) low power Wi-Fi interface for our embedded products.
I was surprised to find Broadcom actually offering a development environment so I joined up today.
The software structure seems well thought out, but there doesn't seem to be a roadmap as it were for integration of the BCM43362 chip and its successors.
If I want to have a Wi-Fi interface in my products it's got to be 5% of the total BOM, not 50% and and likewise in terms of space requirements. A quick glance it the SDK shows its not unfeasible to connect the BCM43362 to the uP of my choice but a search of the Broadcom site for BCM43362 comes up with three links (2 news, and one to Wiced), that's right, no data sheet, sample Gerbers etc. No roadmap for the device family. When I try to get a handle of pricing all I can find is a listing as an un-stocked part with a 5000 MOQ from one supplier.
The more questions I pose, that darker the picture gets. And I can see it all leading to me being told, you should have just used one of our "module partner" modules!! to which the answer is No, because they are too expensive, too big, too power hungry, don't do what I need them to do, are single sourced, and only save my 10% on the FCC tests I'll have to have done on my product anyway.
Someone please get back to me and tell me I've got it all wrong.
Many thanks.
Karel
Show LessHello,
I've been perusing the DCT code to get a better feel for how it works. (My main concern was how/if backwards compatibility would be handled if, for example, the device was upgraded to v1.2 which added new DCT data, then downgraded back to v1.1. Looks like this will be fine.)
Anyway, if I understand the code correctly, the data-length check at the beginning of platform_write_dct() isn't quite right. It's currently:
/* Check if the data is too big to write */
if ( data_length + data_start_offset > ( PLATFORM_DCT_COPY1_END_ADDRESS - PLATFORM_DCT_COPY1_START_ADDRESS ) )
{
return -1;
}
But I think it should be:
/* Check if the data is too big to write */
if ( sizeof(platform_dct_header_t) + data_length + data_start_offset > ( PLATFORM_DCT_COPY1_END_ADDRESS - PLATFORM_DCT_COPY1_START_ADDRESS ) )
{
return -1;
}
More generally -- is this the place you'd like people to be submitting bug reports?
Cheers!
Show LessHello,
I'm developing on the BCM943362WCD4 and I would like to know if it is possible to replace the existing application by another one directly from a running application, something like.
- The current running application download an update from the internet
- It updates itself and reboots
- The new application starts
I tried the ota_upgrade application but it never compiled (section `.bss' will not fit in region `SRAM') and when I also see that it does not use the Wiced framework.
Is there a possibility to accomplish what I mentioned ?
Thank you in advance,
Arthur.
Show LessHi
1. Using WICED version Wiced-SDK-2.4.0-IDE-Installer.zip
2. Apply patch's
TG_WICED240_DMG_BASELINE_11152013 and TG_WICED240_DMG_BASELINE_02262014
3. Driver are ok, WICED usb Jtag port and WICED usb serial port
when i try to download the program I get:
Error in final launch sequence Failed to execute MI command: target remote localhost:3333 Error message from debugger back end:
Remote communication error. Target disconnected.: No error. Remote communication error. Target disconnected.: No error.
"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading Application ...
the debugger in IDE is set to:
generic TCP/IP localhost 3333
How can I run the SN8200 with WICED ?
Attach the log file from openOCD
Show LessDoes WICED SDK support the Macraigor System JTAG ? With the Macraigor JTAG connected, the JTAG scan utility can find the ARM Cortec processor, but it is unable to download code. Seems like the openOCD is not responding or configured properly.
Show LessI'd like to use Color LCD controlled by WICED.
Is there any module available?
I'd also like to have sample code for the LCD.
* STM32F429 seems to support LCD.
Show Less