PINE64

Full Version: PADI programming/debugging with STLINK
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Has anyone been able to program or debug the PADI with an ST-LINK v2 in SWD/JTAG mode? Using either Arduino or direct from openocd and gdb? I'm connecting SWCLK to GE4, SWIO to GE3 and 3.3v/GND. I load up the WiFi AP Mode example with Board=PADI IoT Stamp and OpenOCD=STLink V2. I've verified the programmer works with the Arduino install works with the STLINK by uploading a program to a STM32 board.

Output of arduino build and upload:
Code:
Sketch uses 271236 bytes (10%) of program storage space. Maximum is 2499639 bytes.
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
adapter speed: 480 kHz
adapter_nsrst_delay: 100
rtl8710_reboot
Info : clock speed 480 kHz
Info : STLINK v2 JTAG v32 API v2 SWIM v7 VID 0x0483 PID 0x3748
Info : using stlink api v2
Info : Target voltage: 3.265469
Info : rtl8710.cpu: hardware has 6 breakpoints, 4 watchpoints
target halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x00000100 msp: 0x1ffffffc
auto erase on
auto verify on
initializing RTL8710 flasher
faultmask (/1): 0x01
sp (/32): 0x20000000
pc (/32): 0x10001000
RTL8710 flasher initialized
/Users/tclarke/Library/Arduino15/packages/padiiotstamp/tools/openocd_tools/0.0.1/rtl8710.ocd:261: Error: invalid command name "file"
in procedure 'rtl8710_flash_write' 
at file "/Users/tclarke/Library/Arduino15/packages/padiiotstamp/tools/openocd_tools/0.0.1/rtl8710.ocd", line 261
the selected serial port at file "/Users/tclarke/Library/Arduino15/packages/padiiotstamp/tools/openocd_tools/0.0.1/rtl8710.ocd", line 261
 does not exist or your board is not connected

Looks like the openocd file might be geared specifically for a different adapter?
Seems to be a problem with openocd 0.10.0.. The "file" module was mistakenly disabled for that release.