How to get the platform included for SB-WM-N03-SEVB Rev2.0?

[user_2199751]

Hi

I am currently trying to load images to SB-WM-N03-SEVB board (rev 2.0) which includes BCM4390. I was told to use this board is to use the platform name as BCM94390WCD2. But I have below failures.

Should I use the correct platform info instead of BCM94390WCD2?  If so, where can I get the correct platform info?

Creating Filesystem

Downloading Bootloader ...

platforms/BCM94390WCD2/BCM94390WCD2_targets.mk:111: recipe for target 'download_bootloader' failed

make.exe[1]: *** [download_bootloader] Error 1

make.exe[1]: *** Waiting for unfinished jobs....

Thanks

Won

[Anonymous]

Which SDK version are you using?

In my test, it's fine to build and download image for BCM94390WCD2 on SDK-3.1.2.

[user_2199751]

I used the Wiced SDK version: 3.1.2 which is installed to my labtop and the OS is Windows 8.1.

Thanks

Won

[Anonymous]

Maybe you can add VERBOSE=1 in your make command to see which part is wrong.

[user_2199751]

After I set VERBOSE=1, below is the log. It still showed failure.

**** Build of configuration Default for project Wiced-SDK ****

C:\Users\woncho2\Documents\WICED\WICED-SDK-3.1.2\Wiced-SDK\make.exe snip.scan-BCM94390WCD2 download run
Making .gdbinit
Building Bootloader
Building Serial Flash Loader App
Finished Building Bootloader
Finished Building Serial Flash Loader App

snip_scan-BCM94390WCD2
----------------------------------|---------|---------|
                                  |         |  Static |
              Module              |  Flash  |   RAM   |
----------------------------------+---------+---------|
App                               |       0 |     402 |
Host MCU-family library           |       0 |   19041 |
Interrupt Vectors                 |       0 |     440 |
libc                              |       0 |   24966 |
Networking                        |       0 |    8532 |
NetX                              |       0 |    3300 |
NetX-Duo - Interfaces & Stacks    |       0 |      12 |
Other                             |       0 |    4116 |
Packet Buffers                    |       0 |   23142 |
platform                          |       0 |    1886 |
Ring_Buffer                       |       0 |     128 |
Startup Stack & Link Script fill  |       0 |       6 |
Supplicant - BESL                 |       0 |      80 |
ThreadX                           |       0 |    8652 |
WICED                             |       0 |    4129 |
Wiced_RO_FS                       |       0 |     568 |
WWD                               |       0 |   11880 |
----------------------------------+---------+---------|
TOTAL (bytes)                     |       0 |  111280 |
----------------------------------|---------|---------|

Creating Filesystem
Downloading Bootloader ...
platforms/BCM94390WCD2/BCM94390WCD2_targets.mk:111: recipe for target 'download_bootloader' failed
make.exe[1]: *** [download_bootloader] Error 1
Makefile:186: recipe for target 'main_app' failed
make.exe[1]: *** Waiting for unfinished jobs....
make: *** [main_app] Error 2

[user_2199751]

BTW, in the reboot log from the EVB board, it says that SSBWMN04. But I am using N03.

Would this be a mistake?  It is a bit confusing.

Starting WICED v3.0.2-BETA1-RC2
Platform SSBWMN04 initialised
Started ThreadX v5.6
Initialising NetX v5.7_sp1
Creating Packet pools
WWD SoC/4390 interface initialised
WLAN MAC Address : B0:38:29:21:A3:87
WLAN Firmware    : wl0: Aug 27 2014 10:13:13 version 6.38.15 (TOB) (r496949 WLTEST)

[user_2199751]

As we debug this issue, we found out that the FTDI chip showed some strange behavior. It only recognized the USB serial driver which is different from other EVB board.

We asked Disty sales to replace the board.

Thanks

Won Sang Cho

[Anonymous]

Hello,

Sorry for the late reply. If your FTDI chip is showing some strange behavior, you might need to reprogram it.

Please refer to this link: WICED FTDI chip programming

Hope it helps.

Thanks,

Arsh Buch

[VikramR_26]

Yes and also this issue has been seen on 4390, where the device get bricked if memory gets corrupted.

And you would have to use the below recovery procedure

1) Build the following command:
make waf.sflash_write-NoOS-NoNS-YOUR_PLATFORM WIPE=1

2) Boot the board, bypassing the sflash:
- Press and hold the de-brick button next to the SIP
- Momentarily press the Reset button
- Release the de-brick button.

3) Go to your Eclipse debug configuration
Run Menu -> Debug Configurations -> Startup Tab
Check the "Load Image" checkbox.

4) Debug and run the app in eclipse. This should wipe the serial flash and de-brick the board.

[Anonymous]

Hello,

Could you please verify that the name of your makefile is as follows:

<filename>-BCM94390WCD2 download run

where the file name is that of the napp you want to run.

Thanks,

Arsh Buch

[user_2199751]

Hi Arsh,

I have tried this WICED FTDI chip programming. However, I could not make the changes.

The FTDI chip showed Blank Device in EEPROM.

Chip Type: FT2232H   BLANK DEVICE

Vid: 0x0403

PiD 0x6010

Product Description: USB <-> Serial Converter

Thanks

[Anonymous]

Hello,

Please verify that you have made the following changes:

VID: 0A5C

PID: 43FA

I believe that should solve your problem.

Thanks,

Arsh Buch

[user_2199751]

Hi Arsh,

Thanks for your reply.

Actually, the issue is that I was not able to apply the changes to the FTDI chip.

Here are the steps which I tried.

1. Install FT Prog (v2.8.2.0) to my PC.

2. connect the SB-WM-N03-SEVB board (rev 2.0) to my pc.

3. I clicked the 'scan and parse' and it displayed my device on Device Tree as Device: 0 [Loc ID:0x121].

4. Click Device: 0 in the device tree and right click and Apply template > from file.  Choose BCM9WCD1EVAL1_FTDI.xml file and it showed 'the template was successfully applied."

In the property window of FT_prog, it showed the 0x0a5C, 0x43FA for VID and PID as you pointed out.

5. And then click Device>Program but it showed below messages.

Unhandled exception has occurred in your application ~~ Click continue...  It failed at this stage.

Details

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.IndexOutOfRangeException: Index was outside the bounds of the array.

   at FT_Prog.FT2232H.DataEEPROM()

   at FT_Prog.FT2232H.ProgramDevice(FTDI d2xx)

   at FT_Prog.ScanDevice.ProgramDevice(FTDevice ft)

   at FT_Prog.programForm.btProgram_Click(Object sender, EventArgs e)

   at System.Windows.Forms.Control.OnClick(EventArgs e)

   at System.Windows.Forms.Button.OnClick(EventArgs e)

   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ButtonBase.WndProc(Message& m)

   at System.Windows.Forms.Button.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.34014 built by: FX45W81RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

----------------------------------------

FT_Prog

    Assembly Version: 2.8.2.0

    Win32 Version: 2.8.2.0

    CodeBase: file:///C:/Program%20Files%20(x86)/FTDI/FT_Prog/FT_Prog.exe

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.34250 built by: FX452RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.34239 built by: FX452RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

Microsoft.GeneratedCode

    Assembly Version: 1.0.0.0

    Win32 Version: 4.0.30319.34230 built by: FX452RTMGDR

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

Accessibility

    Assembly Version: 4.0.0.0

    Win32 Version: 4.0.30319.33440 built by: FX45W81RTMREL

    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

Won

[Anonymous]

Hello Won,

Unfortunately, I was not able to reproduce your problem.  One thing you can try is to manually change the VID and PID properties instead of applying the BCM9WCD1EVAL1_FTDI.xml template as those are the only significant changes that are made. Once that is complete and you have reprogrammed the FTDI chip, please check in your device manager if you see "WICED USB Serial Port (COMxx)" as one of the Comports.

Hope that helps.

Thanks,

Arsh Buch