I downloaded the Showcaseapp-1.9.6.apk. (I am on android)
I downloaded 1.9.0_hr_wakeup_DFU.zip
The showcase app does not show my Smart Sensor (movesense) in the app under "movesense connection" also can't select device because its not listed.
The following message from the readme is confusing me:
WARNING: in case the new firmware is not based on the latest Movesense stack, the device looses the capability to be updated!!!
Does this mean I have to update from 1.1 to 1.2 to 1.3 and so on?
Kind regards
No worries, you can update directly from 1.1 => 1.9. However, since your firmware is that old you need to use the "_w_bootloader" DFU packet (contains updated bootloader which was introduced in v1.2). Basic rule is that you'll need the "_w_bootloader" DFU packet if there was softdevice / bootloader change between the two versions.
There may be some issues updating the sensor if you are using the latest Android showcase app (1.9.x). In that case you can download older version from movesense-mobile-lib bitbucket site / downloads. iOS sample app should not have that limitation but you will need also the nrf connect / nrf toolbox apps.
Full Disclosure: I work for the Movesense team
I have downloaded Latest version of Eclipse, ARM build tools. But my ARM vendor details are not present in CMSIS pack. I am working on Cortex M4, the code is compiled successfully. The linker file is provided by vendor.
The issue I am facing are:
1) The DEVICE field in Project/Properties/C C++ Build/Settings is empty.
- What need to be done to get the device details.
- Only Vendor can fill up this part or programmer can do it
2) Which debugging part should I use?
- GDB Hardware debugging
- GDB open ocd debugging
- GDB J-Link debugging
Code is compiled successfully but I can't program/debug my board.
Majority of the tutorials are based on STM32.
But as my ARM Vendor doesn't have CMSIS PACK' in this case what needs to done?
I have just installed Tizen Studio 2.0 and I was trying to update my old application (version wearable 2.2) with new features.
The target device is a Samsung "Gear 2" (not "Gear S2").
By means of the package manager I installed both the Samsung certificate and the Samsung wearable extension.
I removed all the old certificates and acquired a new one via the certificate manager (Samsung option). The new certificate results active.
From the device manager/file explorer I selected "permit to install applications". The result was en error and an invitation to create and activate a Samsung certificate. Exactly what I had done previoulsy!!!!!!
Trying to install the app via debugger the result was:
[Initializing the launch environment...]
RDS: On
Target information: SM-R380
Application information: Id(Z8KnFDT3ds.ride), Package Name(Z8KnFDT3ds),
Project Name(ride)
[Transferring the package...]
Transferred the package: wgt stream -> /opt/usr/apps/tmp/ride.wgt
[Installing the package...]
path is /opt/usr/apps/tmp/ride.wgt
processing result : FATAL_ERROR [61] failed
spend time for pkgcmd is [94]ms
cmd_ret:61
An exception occurred
(Installing the package... > Fail)
An exception occurred
Unexpected stop progress...
(9.763 sec)"
I have already tried (uselessly) to:
regenerate the .medata file,
to create a new the workspace,
to reinstall Tizen 2.0.,
to create a new certificate,
to install the wgt via sdb.
The time and the date on the Gear 2 are correctly synchronized with my host computer (OS Windows 10).
I noticed an anomaly in my Gear 2 DUID (PB+hcyFaLdbqjuVe+Gcn4vBlSYw=)
Considering what reported at the link: http://developer.samsung.com/gear/develop/getting-certificates/permit the DUID should be in any case preceded by a #1.0 or #2.0. This is not true in my case.
By changing manually the DUID to: 1.0#PB+hcyFaLdbqjuVe+Gcn4vBlSYw= a certficate is apparently correctly uploaded on the target even if the FATAL error 61 persits.
Any idea?
Regards
I have been having insurmountable problems with SDK 2.0 as well. Eventually I decided to roll back to the previous version but was struggling to find out how or where to get it. I got a response from the Tizen support team with the following instructions.
Launch Package Manager
click the "Configuration" icon in the top right corner of the Package Manager window.
Turn OFF the "Auto Update" feature
You will be able to see the list of previous versions of Tizen Studio. Select your desired version and click "OK"
This will prompt you that its going to update the previous version. please follow the UI prompt to uninstall this version and install the previous version.
This may or may not work for you.
I have a
NUCLEO-F401RE board
(with STM32F401RE)
and it has been working fine for the most part. Here recently, I followed a tutorial in the book
"Mastering STM32"
where it says to install
OpenOCD.
I had been following along before this as well, and I had been able to connect to my board and flashing it with no problem.
After attempting to get OpenOCD to work though, this is no longer possible. Every time I try to connect to my board, I simply get the following error message:
No ST-LINK detected
I have tried updating the drivers multiple times, rebooting the board, reinstalling the ST-LINK Utility, switching the USB-Cable, resetting the board and reinstalling everything and I have also tried the trick where you hold down the reset button and try to erase the chip.
So far, none of this has worked for me unfortunately.
Here you find a picture of my board.
On my desktop, I am using Windows 10. On my board, and I am using FreeRTOS.
Here you find an image of my Windows Device Manager.
I have also tried to update the firmware on my board using the ST-Link upgrade, but without luck. When attempting this, I either do not have the option to select my device (when using the .jar app) or when using the .exe app, I just get the following error messages:
No ST-Link device detected
Please connect it and then retry
I have not been able to find a solution for this anywhere, so I hope you guys can help! If you need any further relevant information, just let me know. Thank you very much.
As mentioned in other answers, the problem is almost certainly due to a competing driver (something like libusb) taking control of the device.
However, you do not need to "uninstall and reinstall everything" to select the correct driver, assuming that you have already installed it once before. Moreover, the reinstallation procedure most likely won't help, because the uninstallers usually do not uninstall the drivers anyway, and Windows will keep prefering the same wrong driver.
Instead, open Device Manager, find your STM32 STLink device, double-click to open the Properties dialog. Then click "Update Driver", then "Browse my computer for driver software", then "Let me pick from a list of available drivers on my computer", and you should see something like that:
You see that in this example, at least four different drivers available on the system are happy to service the device. The first two are generic libusb drivers, not specific to the dongle (OpenOCD is happy to use either of those, if I remember correctly). The ST-Link utility, however, wants a dedicated driver, developed by STM - those are the two entries below on my picture. If you do not see those, try installing the ST-Link utility again (no need to uninstall anything) or download just the driver from the STM website.
You can now click on the preferred driver in this list and have it replace whatever driver was assigned to the device before.
From my poor experience the "No ST-LINK detected" message in the STM32 Utility shows when you are disconnected or when other program is using a ST-LINK. So, if this start happens after installing OpenOCD try to uninstall this and try again (maybe with option "Connect under reset"?).
For your information. When you plug the cable to the PC and the board is power on then in the settings (STM32 Utility) you can see available ST-Links (even blocked). Here is example when ST-Link is blocked
From what I have learned and understood (but everyone can correct me :)), your board is divided in two parts :
The ST-Link debugger part ;
The rest with the actual microcontroller.
The ST-Link part is used to flash the microcontroller and can be used to flash any other STM32F4 device through SWD. With your picture :
The STM32 ST-Link Utility uses the ST-Link part of your board to flash it. My point is that if you have the "No ST-Link detected", the issue, I am quite sure, doesn't come from the microcontroller part but comes from the ST-Link part. And since you did say that it worked before you install openocd, I would suggest the driver part in W10 that may be the root of your problems.
Try to uninstall everything (and I mean everything) related to the STM32 (openocd, STM32 ST-Link Utility and its driver through Device Manager).
Reinstall only STM32 ST-Link utility (if you did uninstall the drivers correctly, it should ask you the permission to install the drivers during set up) and try to connect your board.
You can also try to remove the SWD jumpers (connector CN2) on your board to detach the ST-Link from the built-in microcontroller part. Since the ST-Link part is independent it will still be detected by the STM32 ST-Link Utility (but you will have to put the jumpers back if you want to actually program your microcontroller).
Just ran into this. The problem boiled down to using nucleo boards and trying to interface with them using older versions of ST-LINK (ST's search for ST-Link's first hit led me to stsw-link0004, which was not installing the right drivers). Why they don't point you to the latest greatest first, who knows.
Whenever I tried to install drivers, I could only select USB Composite device as a compatible driver, despite repeatedly uninstalling/reinstalling stlink0004.
You need to install the newest st-link e.g. stsw-link0009 (or newer).
Uninstall device (device manager had it under USB Composite Device)
Uninstall ST-LINK
Disconnect nucleo.
Reboot.
Install ST-link (stsw-link0009)
The prompt should have you install 3+ drivers. Not just 2.
Plug in. Voila.
I have set up the board according to the RX cpu example in eclipse, and everything seemed to be working fine till I wanted to get the example running on the board. When I click the option to hardware debug, I get an error saying "Error launching GDB server. Check installation".
Am I to re install eclipse, or the GCC toolchain for the RX cpu, or anything else?
I don't know anything about your specifics (that is Renesas or the RX62N). I do use eclipse for embedded work. Typically on a new platform I would make sure I can build and download a release version first. Once you have that working then see if you can get a Debug build and the debugger running. On the platforms I am used to, you have to put in hooks (typically just a single call) to enable the debugger. For exmple on the NetBurner the debugger can run over the serial port or Ethernet so the call has to specify which version you want to use. I know other platforms use JTAG debuggers etc, Typically a dev kit for the board comes with a manual that details how to get the debugger working. I doubt that you need to reinstall anything you just need to get the configuration set up correctly.