- HP EliteBook 8440P
- Architecture: x86_64
- CPU op-mode(s): 32-bit, 64-bit
- Byte Order: Little Endian
- CPU(s): 4
- On-line CPU(s) list: 0-3
- Thread(s) per core: 2
- Core(s) per socket: 2
- Socket(s): 1
- NUMA node(s) 1
- Vendor ID: GenuineIntel
- CPU family: 6
- Model: 37
- Stepping: 2
- CPU MHz: 2534.000
- BogoMIPS: 5054.20
- Virtualisation: VT-x
- L1d cache: 32K
- L1i cache: 32K
- L2 cache: 256K
- L3 cache: 3072K
- NUMA node0 CPU(s): 0-3
- OS: LinuxMint 17.3
- Arduino Ver 1.6.10
- STM32 Lib (ex GitHub)
- $ lsusb
Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 008: ID 12f7:1d23 Memorex Products, Inc.
Bus 002 Device 006: ID 1366:0101 SEGGER J-Link PLUS
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 04f2:b15e Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader
Bus 001 Device 003: ID 03f0:231d Hewlett-Packard Broadcom 2070 Bluetooth Combo
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
So, back to my problem. Although I have been able to load the STM32 libraries but I cannot get my J-Link talk to my mini-STM32 board through the Arduino IDE?
There are many ways to skin a cat. I assume that there are many ways to program the SMT32 using an Arduino IDE environment on a LinuxMint platform.
Just like skinning a cat (the easiest way is to ensure the cat is dead). The analogy to the cat is to suggest that there must be preparatory activities that must be done to ensure success.
Surely there is a script, or documented sequence of tasks to be performed to enable me to program the STM32 on a Linux platform.
One last item: When I compile something like the ubiquitous "blink" sketch, I get the following message;-
- Failed to open serial device.
dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
dfu-util: No DFU capable USB device available
An error occurred while uploading the sketch
Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to firstname.lastname@example.org
Deducing device DFU version from functional descriptor length
Are there any members who have achieved this goal. Most references I have found are based on a Windows or Mac platforms.
Anyone having the same challenges I am?