Kx error kx device fonoff

kx error kx device fonoff

I FLASH/RECALL: Used to disconnect the current call and make another call without hanging up. The KX-NT400 can display video feeds from Panasonic Network Cameras (e.g., KX-HCM/BB-HCM/BL-C disconnect the equipment until the problem is resolved. 3. Dial the outside party's phone number. Redial. 1. Go off-hook. 2. Press [REDIAL]. kx error kx device fonoff

youtube video

How to repair a Panasonic KX-TGA651 cordless phone button in 5 minutes

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-03ThreadNoel Diviney via OpenOCD-devel

Hi Tom, You are right and I will be looking into that and a whole raft of other issues on the K22FX512 Preamp Project. The Low Power operation in particular is not working at all. I inherited this project which is based on Arduino and more specifically on a hack of Teensy. The K22FX512 is not covered by Teensy so I have a bit of work to do. Previously a Teensy board was used as an EzPort programmer but of course this results in a lack of debug capability, Whilst I will continue to use the Arduino Framework I will be moving to a CMake Build System to give me debug support. All of this of course will be based on the current NXP K22F512 SDK build. Thanks to you and the Openocd Team am now happily moving forward. Best regards to all. Noel. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Kx error kx device fonoff Fri Jul 03, 2020 06:44 PM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: kx error kx device fonoff (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing, kx error kx device fonoff. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read rpm error conflicts with file from package at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured, kx error kx device fonoff. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-03ThreadTom via OpenOCD-devel

BTW FOPT = 0xf9 might be set for a good reason. Check NMI pin in your board. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Fri Jul 03, 2020 08:03 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank nserror to nsstring kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, kx error kx device fonoff, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed an internal error occured in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg importerror no module named camera -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, kx error kx device fonoff, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ I am having difficulty understanding how to manage the FCF flash block. Any help would be much appreciated, kx error kx device fonoff. Many Thanks Noel Diviney --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-02ThreadNoel Diviney via OpenOCD-devel

Hi Paul, kx error kx device fonoff, Thank you for the instructions. This is proving to be a great learning exercise for me, I have carried out the git fetches and done a MAKEPKG-mingw PKGBUILD on kx error kx device fonoff results. I now get the following when I program the flash :- [email protected] MSYS /w/arduino1-1812/portable/sketchbook/BlinkBlue1/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkBlue1.ino.bin erase verify 0x" Open On-Chip Debugger 0.10.0+dev-01293-g7c88e76a7-dirty (2020-07-02-20:47) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag", kx error kx device fonoff. To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info ipad 2 restore error 3194 WDOG_STCTRLH = 0x01d2 ** Programming Started ** Info : Strange unsecure mode 0xde requested in the programmed file, set FSEC = 0xfe in the startup code! Info : FOPT requested in the programmed file differs from current setting, set 'kinetis fopt 0xf9'. Info : Trying to re-prorgam FCF. Info : Flash re-programming may fail on this device! Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:521: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 582 at file "embedded:startup.tcl", line 521 [email protected] MSYS /w/arduino1-1812/portable/sketchbook/BlinkBlue1/build Tomorrow I will do some more reading ref the Kinetis FCF block. Thanks for all the help it is most appreciated. Noel. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Thu Jul 02, 2020 11:12 AM UTC kx error kx device fonoff nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, kx error kx device fonoff, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip kx error kx device fonoff unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening kx error kx device fonoff port runtime error 5 file access denied gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, kx error kx device fonoff, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-02ThreadNoel Diviney via OpenOCD-devel

Hi Tom, Finished dinner and back again. I have done a clean build of the latest sources from https://git.code.sf.net/p/openocd/code The log now says :- [email protected] MSYS /w/arduino1-1812/portable/sketchbook/BlinkBlue1/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkBlue1.ino.bin erase verify 0x" Open On-Chip Debugger 0.10.0+dev-01293-g7c88e76a7-dirty (2020-07-02-20:47) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: unipatch 1c 8.2 file open error (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:521: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 582 at file "embedded:startup.tcl", line 521 [email protected] MSYS /w/arduino1-1812/portable/sketchbook/BlinkBlue1/build I have not applied patches to openocd build before so can you please show me whats involved. I am using a Msys64 commandline terminal as inicated above. Thanks Noel. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Thu Jul 02, 2020 09:20 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: kx error kx device fonoff (ARM Ltd.), system error 1396 has occurred 0xba00, kx error kx device fonoff, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes delete user from shaper error FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Kx error kx device fonoff ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-02ThreadTom via OpenOCD-devel

Noel, thanks for warm words! Please test http://openocd.zylin.com/5753 The change does not fix the problem itself but improves verbosity so that an user should know what's wrong. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Thu Jul 02, 2020 01:27 AM UTC **Owner:** nobody Hi nall, Error 1309 error reading file address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be kx error kx device fonoff somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx error kx device fonoff Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Error c2133 unknown size Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at kx error kx device fonoff "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, kx error kx device fonoff, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed kx error kx device fonoff read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ I am having difficulty understanding how to manage the FCF flash block. Any help would be much appreciated. Many Thanks Noel Diviney --- Sent from sourceforge.net because

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-01ThreadNoel Diviney via OpenOCD-devel

Hi Tom. I have just switched on my Lockdown lab set up on the dining room table and saw this great news from you. This is a lifesavour as I was in danger of going totally mental. I have read the Kinetis documentation many times over and my only conclusion is that the guy that wrote the manual needs to go back and have some lessons in Technical Writing. You have provided a lot of detailed information so now I will go off and learn more about programming the FCF Block. I have noted your suggestion to experiment away from the address range 0x400 - 0x40f and I will move it to 0x500 to try things out. I have reasonable experience in Bootloaders, having written my first one at the Adelaide University for the Control Data 6400 back in 1967, however the K22FX512 is another story all together. I work with http://eicon.xyz/ and I am under pressure to get the production programming of a Digital Preamp board sorted out to do a whole panel of boards together. We currently use a Teensy as a single EzPort Programmer, kx error kx device fonoff. We bought a programmer that claimed to do the K22FX kx error kx device fonoff but it did not work so I am now making my own using the FT2232H/Ft4232H chip and Openocd. I would also like to port the Kinetis SDK to Arduino as I am a bit of a fan of Arduino, however, I want to use CMake and the CodeLite Ide as the IDE and Build System. I will now see how I go programming the K22FX512 but I may need to defer to your superior knowlege on Kinetis if that is Ok. Many thanks again for spending the time to kx error kx device fonoff me with this Best regards. Noel. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Wed Jul 01, 2020 09:07 PM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 kx error kx device fonoff 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Kx error kx device fonoff ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 kx error kx device fonoff [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-07-01ThreadTom via OpenOCD-devel

Finally Comedy of errors - disobey 2011 understand what's causing the problem. Sector erase does not set FSEC field to unsecure as mass erase does. So if kx error kx device fonoff issue sector erase followed device reset then the device gets locked (not permanently but it's a trouble as well). To prevent this the OpenOCD kx error kx device fonoff flash driver builds its own FCF and writes it immediately after erase of the sector containing FCF. Ideally the generated FCF is same as FCF data in programmed file. The FCF data in files you send are correct. I was suspicious as there is no dedicated section in elf but this does not matter for flash programming. So the simplest solution to your problem is to switch off FCF checking in OpenOCD by command "kinetis fcf_source write" - be aware that in this mode incorrect FCF data in programmed file can peramnently lock the device. See http://openocd.org/doc/html/Flash-Commands.html#index-kinetis for details. Although the Arduino generated FCF is correct, it differs from one generated by OpenOCD. You should let know OpenOCD about the used FOPT value by command "kinetis fopt". Unfortunately this is not enough. Arduino sets FSEC byte to 0xde. This is ok according to RM but MEEN field is used just in secure modes so there is no point to set it in unsecure state. That's why OpenOCD uses FSEC value 0xfe, same as mass erase sets, kx error kx device fonoff. So this should be fixed somewhere in the startup code of Arduino. Kinetis K22 doesn't implement ECC (error check and correction) in the flash module. Based on the flash principle it is possible to program already programmed flash word and the resulted data is "bitwise and". Of course this canon pixma ip5000 6a00 error not a good practice as it overstress the flash memory cell. RM 29.4.12.8 Program Section command, paragraph CAUTION strictly prohibits this. But if you want to program FOPT to something else than 0xff and the device is mass-erased then reprogramming takes place. That's why the flash driver allows reprogramming of FCF if differs in programmed file. By the time I wrote that code Kx error kx device fonoff didn't know how unreliable is reprogramming of the Kinetis flash. You can try it at any flash location (I would recommend to keep out of FCF): ~~~ > flash fillw 0x7e000 0xfffe 1 wrote 4 bytes to 0x0007e000 in 0.018735s (0.209 KiB/s) > flash fillw 0x7e000 0xf9de 1 Flash write error at 0x0007e000 Failed to read memory at 0x0007e004 error reading to flash at address 0x at offset 0x0007e000 ~~~ The memory location is unreadable after the second flash programming. Interesting this fails on newer rev A silicon only, older MK22FN1M0 withstands the same sequence without problem. Anyway the more zeroes in the second write the more likely the word gets unreadable. The fillw command sequence simulates what happens during programming: Generated FCF is succesfully written ~~~ Debug: 750 1049 kinetis.c:1825 kinetis_write_inner(): flash write @ 0x0400 Debug: 751 1049 kinetis.c:1760 kinetis_write_sections(): write section @ 0x0400 with length 16 bytes Debug: 752 1049 target.c:2523 target_write_u8(): address: 0x4002, value: 0x80 ~~~ and reprogramming fails: ~~~ Debug: 775 1134 kinetis.c:1760 kinetis_write_sections(): write section @ 0x0400 with length 1024 bytes Debug: 776 1134 target.c:2523 target_write_u8(): address: 0x4002, value: 0x80 Debug: 777 1134 target.c:2440 target_read_u8(): address: 0x4002, value: 0x00 Debug: 778 1134 target.c:2440 target_read_u8(): address: 0x4002, value: 0x00 Debug: 779 1149 target.c:2440 target_read_u8(): kx error kx device fonoff 0x4002, value: 0x81 Error: 780 1149 kinetis.c:1782 kinetis_write_sections(): Flash write error at 0x0400 ~~~ The Bauknecht dishwasher f2 error driver should check if FCF is going to be reprogrammed and at least warn in this case. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Wed Jul 01, 2020 09:09 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis Kx error kx device fonoff However, when I press the reset buuton after programming the Svchost .exe application error Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Make optimize.lo error 1 0X400 - 0x40f

2020-07-01ThreadNoel Diviney via OpenOCD-devel

Hello Tom, Nice to hear from you again. I have attached the files. BlinkBlue1 = 0x start address cisco pppoe port error BlinkBlue2 = 0x4000 address Cheers Noel Attachments: - [BlinkBlueFiles.zip](https://sourceforge.net/p/openocd/tickets/_discuss/thread/995dfd8a84/7fac/attachment/BlinkBlueFiles.zip) (151.0 kB; application/x-zip-compressed) --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Wed Jul 01, 2020 08:57 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg kx error kx device fonoff -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: error c2236 unexpected Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, kx error kx device fonoff, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, kx error kx device fonoff, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ I am having difficulty understanding how to

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-30ThreadNoel Diviney via OpenOCD-devel

Hi all. Update. I have created two builds of a Blink Led program for test purposes. The attachment contains the dbug output log. The first build is linked to start at absolute zero and is programmed with the following results:- [email protected] MSYS /w/arduino1-1812/portable/sketchbook/BlinkBlue1/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkBlue1.ino.bin erase verify 0x" Open On-Chip Debugger 0.10.0+dev-01289-g8833c889d-dirty (2020-06-24-10:07) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Kx error kx device fonoff on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = ewa net error code 50 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:521: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 582 at file "embedded:startup.tcl", line 521 --- The second build is linked to start at 0x4000 ie a offset of 16 Kb This one is programmed with the same command and produces the following results :- -- [email protected] MSYS /w/arduino2-1812/portable/sketchbook/BlinkBlue2/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkBlue2.ino.bin erase verify 0x4000" Open On-Chip Debugger 0.10.0+dev-01289-g8833c889d-dirty (2020-06-24-10:07) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on javascript error undefined variable audio Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured, kx error kx device fonoff. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** ** Programming Finished ** ** Verify Started ** ** Verified OK ** Info : Listening on port for tcl connections Info : Listening on port for telnet connections The first one fails at absolute address 0x400, whereas the second one programs and verifies ok. It is my understanding that the FCF block at 0x400 - 0x40f has to be programmed using 32 bit long words, whereas the "program" tcl proc programs a section at a time. I have attached a zip file of the -d3 debug output from both programming attempts. Now my objective is to create a Production line programmer (0x00 start address) and be able to program a whole panel of boards containging the k22f512-128 chip. It is my kx error kx device fonoff that this is not a bug but a a problem with programming this Kinetis k22f512 Why they put this block as an obstacle to normal programming is beyond belief, kx error kx device fonoff. I have attached openocd-drbug.zip which has fulll debug output of both programming attempts. Best regards Noel

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-27ThreadTom via OpenOCD-devel

> I will put together Github tutorial on this and include the "Bash Script" for > creating a nice "OpenOCD Programmer" over the next week. Please do not. The hackish way works for you but offseting slpitted parts of bin file is error prone and pontentially dangerous for others. Better learn more about gnu linker scripts and also read OpenOCD doc. I strongly reccomend elf file for flashing. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Sat Jun 27, 2020 11:55 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) kx error kx device fonoff Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed winapi getlasterror 183 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), kx error kx device fonoff, kx error kx device fonoff 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : Kx error kx device fonoff Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset bde error 8458 goldmine Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip kx error kx device fonoff unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error php error chmod operation not permitted 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' kx error kx device fonoff at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-27ThreadNoel Diviney via OpenOCD-devel

Hi Tom and the OpenOCD Team Another progress update, kx error kx device fonoff. Because I am programming my Flash from absolute zero (ie no linker offset), I am convinced that the Tcl Proc "program" is not able to write the FCF at 0x400 - 0x40f ( it requires a 32 bit double word write instead of the "program sections" used by the "program" command. I have created a bash script to split my binary image into 3 parts as follows :- vect,bin0x000 - kx error kx device fonoff fcf,bin0x400 - 0x40f app.bin 0x410 - EOF I now launch a Msys2 Terminal to erase and kx error kx device fonoff the Flash as follows :- [email protected] MSYS /w/arduino-1812/portable/sketchbook/BlinkTestBlue $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program vect.bin erase verify 0x00" -c "flash write_image app.bin 0x410;" -c "flash verify_bank 0 app.bin 0x410" -c "reset run" -c "exit" Open On-Chip Debugger 0.10.0+dev-01289-g8833c889d-dirty (2020-06-24-10:07) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Info : Device security requested in programmed file! Info : Expect verify errors at FCF (0x408-0x40f). Warn : Flash Configuration Field written. Warn : Reset or power off the device to make settings effective. ** Programming Finished ** ** Verify Started ** ** Verified OK ** Warn : Flash Configuration Field written. Warn : Reset or power off the device to make settings effective. wrote 8388 bytes from file app.bin in 0.234998s (34.857 KiB/s) read 8388 bytes from file app.bin and flash bank 0 at offset 0x0410 in 0.136057s (60.206 KiB/s) contents match Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, kx error kx device fonoff, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. [email protected] MSYS /w/arduino-1812/portable/sketchbook/BlinkTestBlue $ This results in a "verified OK" and a "contents match" for the app.bin part. And I am presented with a "Bright Flashing Blue Led". By the way the "mass_erase" sets the FCF block to default value so that it will not get bricked, kx error kx device fonoff. So I leave that as is for now. I sopcast sp-sc-auth syntax error put together Github tutorial on this and include the "Bash Script" for creating a nice "OpenOCD Programmer" over the next week. A big "thank you" to all for the tremendous work in getting the better of Kinetis, kx error kx device fonoff. Now How Do i close this ticket??? Best regards. Noel Diviney. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, udpxy http/1.1 500 service error 06:14 AM UTC by Noel Diviney **Last Updated:** Wed Jun 24, 2020 12:03 PM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally, kx error kx device fonoff. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select ', kx error kx device fonoff. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-24ThreadNoel Diviney via OpenOCD-devel

Hi Tom. A progress update. Adjusted the msys2 PKGBUILD script to get the latest version from https://github.com/ntfreak/openocd which should get me on the same wavelength. see as follows :- -- $ openocd --version Open On-Chip Debugger 0.10.0+dev-01289-g8833c889d-dirty (2020-06-24-10:07) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.h --- I am now working on creating a "BlinkLed" build for my kinetis MK22FX512AVLH12 board to make it possible to compare my results with your's. stay tuned, Best regards Noel --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Tue Jun 23, 2020 08:21 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kx error kx device fonoff kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-23ThreadNoel Diviney via OpenOCD-devel

Hi Tom, kx error kx device fonoff, Thanks Tom, I had already started to look at MCUXpresso, so now I wll get on with that. So far I have not bricked any chips yet so luck has been on my side. BTW. Are the tomvdb of EduBot fame. I have been learning all about boards.txt etc for the Stm32 from the arduino_edubot project, kx error kx device fonoff. Thanks again, Noel. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, kx error kx device fonoff, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Tue Jun 23, 2020 07:56 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, kx error kx device fonoff, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 kx error kx device fonoff [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already kx error kx device fonoff swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : kx error kx device fonoff FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH kx error kx device fonoff 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Kx error kx device fonoff Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Kx error kx device fonoff Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ I am having difficulty understanding how to manage the FCF flash

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-23ThreadTom via OpenOCD-devel

My code uses Kinetis SDK. It is available for free, you just need to make account @ nxp and request SDK from the generator at https://mcuxpresso.nxp.com The SDK is far from perfect, but you can at least take some inspiration from it. BTW if the FCF block is missing from your binary at all then OpenOCD probably saved your MCU from beeing bricked permanently. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Tue Jun kx error kx device fonoff, 2020 07:41 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally, kx error kx device fonoff. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: a network error occurred skype (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Kx error kx device fonoff Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg kx error kx device fonoff -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed kx error kx device fonoff GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug kx error kx device fonoff, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Error 170 usb connection error on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", kx error kx device fonoff, line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ I am having

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-23ThreadNoel Diviney via OpenOCD-devel

Hi Tom, Thank you for your response, it has a lot very usefull information, kx error kx device fonoff. Looking at your objectdump it is most likely the linker script holds the secret. I would now like to delve into spi connect error postgresql some more as it is a great learning experience. I inherited this project. It is using Arduino and running a hack of the Teensy3 core, which is where the linker script is coming from. The version of Arduino is 1.6.11 and Teensy is circa 1.3.0so it needs some work. What build system did kx error kx device fonoff use ? I would like to duplicate what you have done and then I think we are almost there. I will post my progress as I go. Many thanks again for your assistance. Noel --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Tue Jun 23, 2020 06:43 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, kx error kx device fonoff, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select ', kx error kx device fonoff. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), kx error kx device fonoff 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, kx error kx device fonoff, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing, kx error kx device fonoff. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as error generating image. drupal flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to read memory at

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-23ThreadTom via OpenOCD-devel

Looks strange. Please be aware that code base [https://github.com/sysprogs/openocd] is not same as our "official" source, so it might be a problem of sysprog's changes. Let's hope it's not the case. I tested programming with our fresh git master code in almost identical setup: FTDI based SWD resistor hack and MK22FX512, just the blink test is not arduino based - and gues what - programming works: javascript internal server error Open On-Chip Debugger 0.10.0+dev-01267-g0b02281-dirty (2020-05-28-18:10) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Info : add flash_bank kinetis kx.pflash Info : clock speed 1000 kHz Info : SWD DPIDR kx error kx device fonoff Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x04e8 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes Flex RAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = kx error kx device fonoff ** Programming Started ** ** Programming Finished ** ** Verify Started ** ** Verified OK ** ** Resetting Target ** Info : MDM: Chip is unsecured. Continuing. Info : Listening on port for tcl connections Info : Listening on port for telnet connections Please first check if FCF field is configured properly in your binary ~~~ arm-none-eabi-objdump -h BlinkTestBlue.ino.elf ~~~ should look like: ~~~ Sections: Idx Name Size VMA LMA File off Algn 0 .interrupts 0400 8000 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 1 .flash_config 0010 0400 0400 8400 2**0 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 .text 5068 0410 0410 8410 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE . ~~~ If not, the check linker ld script. If FCF is ok, then please re-run programming cmd with -d3 and put the result log somewhere --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Tue Jun 23, 2020 03:18 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, kx error kx device fonoff, when I press the reset buuton after programming the Led All errors php normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH kx error kx device fonoff 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' fr.error openbox 200 procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-22ThreadNoel Diviney via OpenOCD-devel

Hi all My problem is due to programming all of the flash at once using the following. A different algorithm is needed for the FCF block at 0x400 - 0x40f $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Could somebody tell me where the tcl proc "program" code is located so that I can write a similar proc myself to program the different sections. I am confident that I then should be able to solve my problem. BTW "Hats off" to all for the great work done in getting Kinetis to work. Thank you in anticipation and best regards. Noel Diviney. --- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** kx error kx device fonoff **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Sun Jun 14, 2020 06:14 AM UTC **Owner:** nobody Hi nall, Error at address 0x400 when programming flash on Kinetis MK22F512xxx12 However, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block have to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured, kx error kx device fonoff. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device php pdo error 42000 kx error kx device fonoff (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 kx error kx device fonoff 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port 500 server error iis gdb connections Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to

[OpenOCD-devel] [openocd:tickets] #270 Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f

2020-06-14ThreadNoel Diviney via OpenOCD-devel

--- ** [tickets:#270] Kinetis MK22FX512: Error writing FCF Block 0X400 - 0x40f** **Status:** new **Milestone:** 0.9.0 **Created:** Sun Jun 14, 2020 06:14 AM UTC by Noel Diviney **Last Updated:** Sun Jun 14, 2020 06:14 AM UTC **Owner:** nobody Hi nall, Error kx error kx device fonoff address 0x400 when kx error kx device fonoff flash on Kinetis Kx error kx device fonoff However, kx error kx device fonoff, when I press the reset buuton after programming the Led Blinks normally. Does the FCF block hp printer device communication error 5012 to be skipped somehow? Is the "Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED" a problem given that the program runs. The terminal output is as follows :- [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select '. Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : JTAG tap: kx.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd.), part: 0xba00, ver: 0x4) Info : MDM: Chip is unsecured. Continuing. target halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Error: JTAG-DP STICKY ERROR Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ openocd -f interface/ftdi/olimex-arm-usb-ocd.cfg -f interface/ftdi/swd-resistor-hack.cfg -c "transport select swd" -f target/kx.cfg -c "program BlinkTestBlue.ino.elf verify reset" Open On-Chip Debugger 0.10.0 (2020-05-30) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 09e75e98b4d9ea7909e8837b7a3f00dda4589dc3 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : FTDI SWD mode enabled Warn : Transport "swd" was already selected swd Info : add flash_bank kinetis kx.pflash Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED Info : clock speed 1000 kHz Info : SWD DPIDR 0x2ba01477 Info : kx.cpu: hardware has 6 breakpoints, 4 watchpoints Info : kx.cpu: external reset detected Info : MDM: Chip is unsecured, kx error kx device fonoff. Continuing. Info : starting gdb server for kx.cpu on Info : Listening on port for gdb connections Info : MDM: Chip is unsecured. Continuing. pioneer k .error halted due to debug-request, current mode: Thread xPSR: 0x0100 pc: 0x0188 msp: 0x2001 Info : Kinetis MK22FX512xxx12 detected: 2 flash blocks Info : 1 PFlash banks: 512k total Info : 1 FlexNVM banks: 128k total, 128k available as data flash, 4096bytes FlexRAM Info : Disabling Kinetis watchdog (initial WDOG_STCTRLH = 0x01d3) Info : WDOG_STCTRLH = 0x01d2 ** Programming Started ** Error: Flash write error at 0x0400 ** Programming Finished ** ** Verify Started ** Error: timed out while waiting for target halted Error: error executing cortex_m crc algorithm Info : SWD DPIDR 0x2ba01477 Error: Failed to read memory at 0x0404 embedded:startup.tcl:500: Error: ** Verify Failed ** in procedure 'program' in procedure 'program_error' called at file "embedded:startup.tcl", line 561 at file "embedded:startup.tcl", line 500 [email protected] MSYS /w/adgp-1611/portable/sketchbook/BlinkTestBlue/build $ I am having difficulty understanding how to manage the FCF flash block. Any help would be much appreciated. Many Thanks Noel Diviney --- Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/openocd/tickets/ To unsubscribe from further messages, a project admin can change settings at

close

No.Fixed issue1 Modification :
Fixed issue :
When REFER transfer is operated, the phone doesn't display the updated information from INVETE including Replaces header.
2 Modification
CSTA bugs are fixed.

Fixed issue :
- Can't answer incomming call from over 10 digits telephone number.
- Call information (Caller / Called) becomes reversed when the call is established.
3 Improvement
Update client-certificate and private-key SHA1 to SHA2.
4 Modification
Fixed issue :
There are ceses where HTTPS provisioning (Client Certificate) fails when the provisiong server is MS IIS.
5 Modification
Fixed issue :
There is a case that the phone does not restart when the restart target parameters has changed in the config download.
6 Modification
Fixed issue :
There are cases where SIP process http / nsis.sf.net/nsis_error deadlocked by sending SIP message and receiving the hole punching packet at the same time.
7 Improvement
Enhance XML functions
- Increase entrypoints for XML
- Add new XML-element (MissedCallOff, CancelKey)
kx error kx device fonoff parameters :
- XML_SOFT_KEY_NAMEx
- XMLAPP_URL_SOFT_KEY
- XMLAPP_URL_FLEX_BUTTONx

Related parameters :
- XMLAPP_INITIAL_URL
- XML_INITIATE_KEY_SOFT1 (HDV130/230)
- XML_INITIATE_KEY_SOFT2 (HDV130/230)
- XML_INITIATE_KEY_SOFT3 (HDV130/230)
- FLEX_BUTTON_FACILITY_ACTx
- DSS_BUTTON_FACILITY_ACTx (HDV230/330)
8 Modification
Fixed issue :
A phone kx error kx device fonoff answer an incoming call which has phone number over 10 digits on uaCSTA.
9 Modification
Fixed issue :
A phone exchanges information about calling party and called party on uaCSTA after answering an incoming call.
10 Modification
Fixed issue :
A call is disconnected when an other line is selected while having a conversation even on AUTO_CALL_HOLD="Y".
11 Improvement
When a phone checks voice mail, it can send SUBSCRIBE message including mailbox name.

New parameter:
VM_SUBSCRIBE_SPECIFIC_n
12 Modification
Fixed issue of TR-069: Uptime is incorrect.
13 Improvement
A phone doesn't care case-sensitive search of XSI phonebook.
14 Improvement
Certificate overview is displayable via TR-069 management using Vendor Specific parameter.
15 Modification
Fixed issue :
Ring back tone rings against RINGBACK_TONE_TIMING configuration.
16 kx error kx device fonoff A user can change "Edit" character string display in 1st line of XML Testbox.
17 Improvement
A phone can display other party's CLIP information on phone screen when fatal error call + of duty user makes an outgoing call with XML Trigger function.
18 Improvement
After a user refers call list in XML application, missed call kx error kx device fonoff deleted in call list.
19 Improvement
A user can specify an indivisual URL for XLM start by soft key. Besides, a user can change soft key label.
20 Improvement
A user can customize configuration of HOME screen.

New parameter:
SYS_HOME_MENU_ICONx
SYS_HOME_MENU_XML_NAMEx
SYS_HOME_MENU_XML_URLx
SYS_HOME_MENU_XML_ICONx
21 Improvement
Customize Home Screen
22 Improvement
Changing the Status Bar display method
If the icons are less than 3, it displays icons and “Display Name” at same time.
23 Improvement
Add some configuration parameters to separate the update timing of the XSI phonbook data from provisioning.

New parameter:
XSI_PHONEBOOK_CYCLIC_INTVL
XSI_PHONEBOOK_RESYNC_DURATION
24 Improvement
LED status of the ACD key now synchronizes its status in accordance with every message sent by the server correctly.
25 Improvement
When TGP600/HDV begins N-way conference call, the hold music plays for the held outside caller for the entire hold duration

New config parameter:
CONF_SERVER_HOLD_ENABLE="Y" ( default value is "N", kx error kx device fonoff. )
26 Modification
Fixed issue :
There are ceses that the terminal does not send invite when it receives refer.
27 Modification
Fixed issue :
There are ceses where HTTPS provisioning fails when the terminal starts up after factory reset operation.
28 Improvement
Enhance the XML function.
- Softkey name can be changed by provisioning
- Add activating XML function to the program key
29 Improvement
Add application to activate XML function into the program key.

New parameter:
XMLAPP_URL_FLEX_BUTTONx
30 Modification
Fixed issue :
Dial plan bug fixed.
31 Modification
Fixed issue :
When importing a config file via WebUI that has any parameter mistake, an error will be displayed.
32 Modification
Fixed issue :
Disable CANCEL key during seaching Bluetooth headset.
33 Improvement
BLF number is not displayed when dialiing.

New parameter:
BLF_DISPLAY_OFF_OUTGOING
34 Modification
BLF doesn't work after a phone in factory reset imports cofiguration file from provisioning server.
35 Modification
A phone continue to seize line even after a call is terminated.

New parameter:
SHARED_STOP_LINE_SEIZE
36 Modification
Fixed issue:
1) Once update firmware to default firmware by typical database errors and their solutions to Redirection server, below configuration parameters are specified automatically.
- CFG_STANDARD_FILE_PATH="https://provisioning.e-connecting.net/redirect/conf/{mac}.cfg"
- FIRM_FILE_PATH="http://fw-provi.e-connecting.net/firm/000/HDVx30-yy.zzz.fw" - FIRM_VERSION="HDVx30-yy.zzz"
note) yy.zzz is firmware version of default firmware on Redirection server
2) After restart or Power cycle, access to Redirection server.
3) Compare current firmware version with default firmware version.
4) If default firmware version is higherthe phone eoleexception ole error 800a03ec firmware.
37 Inprovement
1. Device doesn't reboot when resetting line with TR-069.
2. Line status of TR-069 is supported.
38 Modification
Fixed issue: Some of Cyrillic alphabet is mistake.
39 Modification
Fixed issue: Some words of Russian menu are mistranslation.
40 Modification
Fixed issue :
There are ceses that the transfer function doesn't work when the terminal receives invite including replace.
41 Modification
Fixed issue :
The one way audio occures when the terminal receives invite including replace.
42 Modification
Fixed issue :
There are ceses registration-loss occurs.
43 Modification
Fixed issue:
The call can't be released with the sequence below.
1. Sending "session timer reInvite"
2. Receiving "Bye"
3. Receiving "200OK of ReInvite"
44 Modification
Fixed issue of TR-069:
1. Config file download is failed (Error 9015).
2. Perodic Inform isn't executed when PERIODIC INTERVAL is set more than 24 hours.
45 Modification
Fixed issue :
When importing a config file via WebUI that has any parameter mistake, an error will be displayed.
46 Modification
Fixed issue of TR-069:
Parametrs associated with SIP don't work porperly.
47 Improvement
Handle presence JID with case ignored.
48 Modification
Fixed issue :
In case of TGP600 use TCP and no massage during 120[s], failed INVITE messages (failed with 408 responses back from the SBC) after 120[s] .
->[Modification]the keep-alive time will be changed in the Panasonic phone dynamically based on the SBC expire time received in the 200 OK register.
49 Modification
Fixed issue :
Cancel key is not available when a user is transferring a call.

Panasonic KX-TS3282W 2-Line Corded Phone with Caller ID and Intercom, White

Product Description

Kxts3282Wwht- 2-Line Integrated Phone System.

From the Manufacturer


.gray {color:#666;} div.aplusBody { color:#333; font-family: Arial, Helvetica, sans-serif; font-size: 15px; } div.aplusTitle { color:#333; font-size: 20px; font-weight: bold; font-family: Kx error kx device fonoff, Helvetica, sans-serif; line-height: 2em; } div.aplusBox { color:#333; font-size: 14px; font-family: Arial, Helvetica, sans-serif; margin-right: 20px; line-height: 1.5em; padding: 15px 0 0 30px; float:left; } div.aplusBox ul { list-style-position:outside; margin:0em .6em 0em; padding:0em .6em 0em; } div.aplusBoxPop { padding: 15px 0 0 30px; float:left; font-family: Arial, Helvetica, sans-serif; font-size: 15px; } div.aplusBody h1 { color:#333; font-family: Arial, Helvetica, sans-serif; font-size: 24px; vertical-align:bottom; line-height:1em; } div.aplusBody h2 { color:#333; font-family: Arial, Helvetica, sans-serif; font-size: 16px; font-weight:bold; line-height:1em; } div.aplusBody sup { font-size: 75%; line-height: 0; position: relative; vertical-align: baseline; top: -0.5em; } div.aplusBodyLegal { font-size: 11px; font-weight: normal; font-family: Arial, Helvetica, sans-serif; margin:1em 0 1em 0; } div.aplusBodyLegal ol { list-style-position:outside; margin:0em 1em 0em; padding:0em 1em kx error kx device fonoff } table.aplusComparisonHeader { padding:15px 30px; } table.aplusComparisonHeader .current { color:#CC6600; font-weight:bold; font-style:italic; } table.aplusComparisonHeader img { padding-top:5px; } table.aplusComparisonGroup { border-top:1px solid #999; padding:3px 0; } table.aplusComparisonGroup:last-child { border-bottom:1px solid #999; } table.aplusComparison { color:#333; font-family: Arial, Helvetica, sans-serif; font-size: 12px; line-height:1.2em; } table.aplusComparison td { padding:10px 0; } table.aplusComparison tr.odd { background-color:#e2e2e2; vertical-align:text-top; } table.aplusComparison tr.even { background-color:#f9f9f9; vertical-align:text-top; } table.aplusComparison td.feature { padding-left:15px; font-weight:bold; }

The Panasonic KX-TS3282W two-line integrated phone system with features such as an integrated speakerphone, 3-way conferencing, and Call Waiting Caller ID makes this phone system a convenient solution to all your small-office telephone needs. With Call Waiting Caller ID, you can see how's calling even if you're already on the phone. The KX-TS3282W will also work during a power outage, kx error kx device fonoff, so you'll never have to worry about making or receiving a call in the case of emergency.
Enlarge
PRODUCT COMPARISONS

Phone Features

Kx error kx device fonoff (Current)
KX-TS3282WBetter
KX-TS208WGood
KX-TS620W

General

Type of Phone Corded Corded Corded Number of Phone Lines 2 2 1 Answering Device No No Yes Speakerphone Yes Yes Yes Caller ID Yes Yes Yes Bluetooth Capability No No No

Base

Wall Mount Yes Yes Yes Keypad at Base Yes Yes Yes Call Waiting Yes *1 Yes *1 Yes *1 Number of Mailboxes Yes *3 Yes *3 Yes *3 Speed Dial Yes Yes Yes Backlit keypads No No No Ringer 3-Step Volume Control 3-Step Volume Control Yes *4 / Yes Headset Jack Yes Yes No Color White (Black also available) White White

Brand Specific

Talking Caller ID No No No Intelligent Eco Mode No No No Power Back Up Operation Yes Yes Yes
WHAT'S IN THE BOX
  • AC Adapter
  • One (1) Telephone Line Cord
  • One (1) Handset
  • Three (3) AA Batteries
  • One (1) 4-Wire Telephone Line Cord with green plugs
  • One (1) 2-Wire Telephone Line Cord

  1. Requires subscription to name-and Number Caller ID, Call Waiting and/or Voice Mail service.
  2. Requires number registration in the call block list.
  3. Requires registration in Phonebook function. Name pronunciation may vary.
  4. Optional Handset required.

0 Comments

Leave a Comment