Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Thank you for the exe. I tried it and, alas, still no joy.
After the ****OpenOCD failed.... message, the openocd_log is showing:
Warn : Using DEPRECATED interface driver 'ft2232'
Info : Consider using the 'ftdi' interface driver, with configuration files in interface/ftdi/...
Error: unable to open ftdi device: device not found
The problem is with the bootloader. (build-> waf.bootloader-NoOS-CEL_WB4343WF3SP2)
If I use the PuTTY TELNET connection and download a .ELF file, it appears to transfer to the target.
Then If I force the debugger to start within WICED I can single step through the init code although I never seem to get as far as the ELF code I loaded. I get a watchdog trap instead. But my point is that I seem to be able to do everything but boot-load through WICED. Bear in mind that I am using the SWD interface as opposed to the JTAG interface.
I just have the feeling that I am just a setting or two away from success but with all these abstraction layers I just can't figure out what to set.
Over the weekend I ever tried all this at home using a fresh install just in case I set something wrong during these last 2 painful weeks.
Any thoughts on how to get the boot-loader to work?
The people at CEL provided me with a programming board that seems to solve my download problems. No more Segger or Olimex. No more SWD vs JTAG. This board uses a FTDI chip similar to the Broadcom Eval module I was using. Happy Happy day!
I re-installed WICED just to undo all the stuff I was tweaking for a fresh beginning.
I have new platform files that CEL provided describing thier module and added them to the platforms folder. The CEL module is very similar to the BCM94343WWCD1 platform so porting should be simple.
I can compile download and run with no problems. But when I try to compile debug and download I have a problem when I try to start the debugger. I get an error that says.
tools/makefiles/wiced_config.mk:356: *** No application specified. Options are: waf test README.txt wwd snip demo. Stop.
make: *** No rule to make target 'build/CEL_WB4343SP2/config.mk', needed by 'main_app'. Stop.
I added some print statements in the wiced_config.mk script that shows what the variable APP is set to. When I compile if shows the name of the program. But when I debug APP is empty.
If I ignore the error, and enter the debugger, it is stating in the console in red that
No source file named apps/snip/program_name/program_name.c
This happens even with the WICED program examples such as snip.scan.
I have tried all sorts of settings based on these and other forums and quick start guides. And I swear that I had this working properly back when I was using the Broadcom eval module but even that module behaves this way now.
I am so close to getting productive again I can taste it.