Hello,
I am not starting it from the directory it's located - so we're probably seeing the same.
It should not cause a segmentation fault, however. That indicates that something is not right.
Thanks, Jacob
Posts by wifijacob
-
-
Well - it was caused by missing device-specific files (JLinkDevices.xml) etc.
-
And same on 6.32i.
Has it ever worked?
-
I get the same on v6.44f.
-
Hi,
I managed to reproduce by having two J-Links connected to the computer, clicking the target device drop-down and select a device.Thanks, Jacob
-
Hi,
When I try to connect to a PSoC 6 (CY8C6XX7_CM4) device using JLinkExe v6.46g on ARM I get this:Code
Display MoreThe selected device "CY8C6XX7_CM4" is unknown to this version of the J-Link software. Please make sure that at least the core J-Link shall connect to, is selected. Proper device selection is required to use the J-Link internal flash loaders for flash download or unlimited flash breakpoints. For some devices which require a special handling, selection of the correct device is important. No valid device has been selected. J-Link>Segmentation fault -
i'm having the same issue - JLinkRTTClient doesn't seem to connect to the server but telnet works.
-
hi,
i'm getting this segmentation fault when trying to use jlinkrttviewer (it occurs when clicking on the device selector):Code
Display MoreThread 1 "JLinkRTTViewer" received signal SIGSEGV, Segmentation fault. 0x0000000000421080 in ?? () (gdb) bt #0 0x0000000000421080 in ?? () #1 0x0000000000413be8 in ?? () #2 0x0000000000415aa3 in ?? () #3 0x00007ffff6d8f010 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x00007ffff769c4d1 in QComboBox::activated(int) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #5 0x00007ffff769c58e in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #6 0x00007ffff769cd29 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #7 0x00007ffff6d8f010 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x00007ffff794dda2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #9 0x00007ffff7697faa in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x00007ffff6d7aa76 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #11 0x00007ffff72a7fbc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x00007ffff72af0d6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x00007ffff6d7a90d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #14 0x00007ffff72ae6dd in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #15 0x00007ffff732cd7c in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #16 0x00007ffff732bc83 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #17 0x00007ffff7355542 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #18 0x00007ffff5239197 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007ffff52393f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007ffff523949c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007ffff6dab2ae in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #22 0x00007ffff7355616 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #23 0x00007ffff6d7918f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #24 0x00007ffff6d794f5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #25 0x00007ffff778aa3c in QDialog::exec() () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #26 0x0000000000418155 in ?? () #27 0x000000000041b353 in ?? () #28 0x0000000000416423 in ?? () #29 0x00007ffff597c830 in __libc_start_main (main=0x4162a0, argc=1, argv=0x7fffffffd3e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd3d8) at ../csu/libc-start.c:291 #30 0x0000000000411b69 in ?? () #31 0x00007fffffffd3d8 in ?? () #32 0x000000000000001c in ?? () #33 0x0000000000000001 in ?? () #34 0x00007fffffffd836 in ?? () #35 0x0000000000000000 in ?? ()i'm using ubuntu 16.04.
-
Hello,
I'm having issues flashing a PSoC 5 LP device using J-Link. If I flash the same .hex using PSoC Programmer and Cypress own MiniProg it works.
If I use PSoC Programmer and MiniProg to read out the memory, I can see that the only difference in the two cases is that when flashing with MiniProg 'Config Flash Area' address 0x0400 contains some data (roughly between 0x0400 and 0x0f80).- Anyone knows what this data is?
- How can I flash it using J-Link?
- Has anyone else successfully flashed a PSoC 5 LP device using J-Link?Thanks, Jacob
-
Hello,
We (and I know about others) use J-Link on Raspberry Pis, which generally run Debian-based systems.Can you please provide .deb packages for ARM? Or - alternatively - provide the build scripts used to build the x86 .debs.
Thanks, Jacob
-
-
The documentation states:
Code
Display More0x9030 0000 – Checksum (2 bytes). This is the checksumof the entire user flash section—the arithmetical sum ofevery byte in the user’s flash. Only the two least significantbytes (LSB) of the result are saved in this section, in big-endian format (most significant byte is first). The program-mer must use this to check the integrity of the hex file and toverify the quality of the programming. In this context, “integ-rity” means that the Checksum and User Flash sectionsmust be correlated in this file. At the end of programming,the checksum of flash (2 LSB) is compared to the checksumfrom the hex file. 0x9040 0000 – Flash Protection (32 bytes maximum). Thisdata is programmed into supervisory rows of the flash mac-ros (see Figure 2-1 on page 6). Every bit defines the write-protection setting for the corresponding user row. The num-ber of bytes to be read from this section depends on theflash size. -
Hello,
Log attached.Thanks.
-
Hello,
Linux
J-Link EDU, S/N 269402077
SEGGER J-Link Commander V6.14c
Yes.
Also, I sometimes get this:CodeDownloading file [program.hex]... Comparing flash [100%] Done. Erasing flash [100%] Done. Programming flash [100%] Done. Verifying flash [100%] Done. J-Link: Flash download: Restarting flash programming due to program error (possibly skipped erasure of half-way erased sector). J-Link: Flash download: Skip optimizations disabled for second try. Writing target memory failed.Your forum messes up newlines in code..!
Downloading file [program.hex]...
Comparing flash [100%] Done.
Erasing flash [100%] Done.
Programming flash [100%] Done.
Verifying flash [100%] Done.
J-Link: Flash download: Restarting flash programming due to program error (possibly skipped erasure of half-way erased sector).
J-Link: Flash download: Skip optimizations disabled for second try.
Writing target memory failed.
Thanks, Jacob -
Hello,
Trying to flash a Cypress PSoC CY8C4247 device using J-Link. Everything seems to work but I always get an error message when doing loadfile:Code
Display More> JLinkExe -if SWD -device CY8C4247XXX-LXXX -speed 1000 [halt/reset/erase etc] J-Link>loadfile program.hex Downloading file [program.hex]... Comparing flash [100%] Done. Erasing flash [100%] Done. Programming flash [100%] Done. Verifying flash [100%] Done. J-Link: Flash download: Flash programming performed for 1 range (131072 bytes) J-Link: Flash download: Total time needed: 3.940s (Prepare: 0.289s, Compare: 0.103s, Erase: 0.058s, Program: 3.171s, Verify: 0.103s, Restore: 0.215s) Writing target memory failed.However, after resetting, the system seems to start up just fine. It doesn't matter if I decrease the speed, it always gives the error like above.
What may cause this error message?
Thanks, Jacob