Telecharger Ru Board Dongle Emulator
Raingarda Krzynowek
If you are looking for a way to use a ru-board dongle emulator on your computer, you may need to download and install a telecharger driver first. A ru-board dongle emulator is a device that allows you to run software that requires a hardware dongle without having the actual dongle. A telecharger driver is a software that enables your computer to communicate with the dongle emulator.
In this article, we will show you how to download and install telecharger driver ru board dongle emulator on your Windows system. We will also provide some tips and troubleshooting steps in case you encounter any problems.
If you have followed the steps above correctly, you should be able to use your ru-board dongle emulator with any software that requires a hardware dongle. However, if you encounter any problems, here are some tips and troubleshooting steps that may help:
The nRF52840 Dongle is a small, low-cost USB dongle that supports Bluetooth 5.4, Bluetooth mesh, Thread, Zigbee, 802.15.4, ANT and 2.4 GHz proprietary protocols. The Dongle is the perfect target hardware for use with nRF Connect for Desktop as it is low-cost but still support all the short range wireless standards used with Nordic devices. The dongle has been designed to be used as a wireless HW device together with nRF Connect for Desktop. For other use cases please do note that there is no debug support on the Dongle, only support for programming the device and communicating through USB.
It is supported by most of the nRF Connect for Desktop apps and will automatically be programmed if needed. In addition custom applications can be compiled and downloaded to the Dongle. It has a user programmable RGB LED, a green LED, a user programmable button as well as 15 GPIO accessible from castellated solder points along the edge. Example applications are available in the nRF5 SDK under the board name PCA10059.
The nRF52840 Dongle is supported by nRF Connect for Desktop as well as programming through nRFUtil.
I have a P-Nucleo-WB55 and am trying to develop a project with it. I ran the "Getting Started" demo on the back of the pack and it worked brilliantly, so I got in with my project development. This started with a simple project to run a sensor using the SPI interface which worked fine. I then went to try some BLE development which is why I got this board.
Unfortunately, this is where my problems start. I was trying the BLE HeartRate demo and no matter what i did I couldn't get it to work. I followed the instructions for the FUS and BLE stack update and spent the next 24 hours thinking I had bricked the board as it would no longer do anything (I followed the ST instructions verbatim). I finally managed to get the update to work by using a mix of instructions from here and reddit on top of the ST release notes.
Anyway, I now have the most rect FUS from STM32Cube_FW_WB_V1.5.0 installed, as well as the full BLE stack, but still I can not get anything bluetoothy to work. At this point I decided the most sensible thing would be to try and get it back into its delivery state. I believe the firmware that should be in the main board (I haven't touched the dongle) is the BLE_p2pServer_ota, correct? I have opened this in STM32CubeIDE and itseems to program correctly if I tie the boot0 pin high (pins 5 & 7 or CN7), but it still doesn't seem to work at all. It also won't let me debug it, but I gather that is because the project doesn't enable the debug pins or something.
I am not too familiar with the STM32CubeIDE and have a had a lot of trouble getting anything going. The various application and release notes for the WB 55 seem to be inconsistent with each other and out of date.
If you are confident enough that you managed to update your board with the latest FUS V1.10 version and the Full BLE stack from the CubeWB FW package V1.5.0, the quickest thing to do would be to load the hex file located under STM32Cube_FW_WB_V1.5.0\Projects\P-NUCLEO-WB55.Nucleo\Applications\BLE\BLE_p2pServer\Binary at address 0x08000000.
Thank you for the detailed answer. I have downloaded the hex file in the location you gave into the board and it still doesn't work I'm afraid. The green LED (LD2) comes on, but it just stays on. I have used STM32CubeProgrammer and tried downloading it with both the on-board ST-LINK (with and without BOOT0 tied high), and the USB_USER connector, and they all give the same result. I also had a friend who has the same board upload the memory content from his board (which works correctly, LD2 flashing on startup), and while the uploaded binary is different from the binaries i have looked at, it does the exact same thing. Have I put the right BLE firmware in? Should I try different ones? I notice the documentation doesn't mention the full and light versions, so I assume this is a recent thing?
One trick before upgrading the board is to start from a clean user area. this can be achieved by setting the RDP option byte to 0xBB (level 1) and then back to 0xAA (level 0). This will trigger a mass erase of the user area of the main flash memory. Then download the hex file again at address 0x08000000.
In terms of changing the RDP option, I had to do this in order to the get the FUS and BLE FW update to work, otherwise I got "firmware is not authentic" errors, and the FUS version never changed. from the 0.5.0.2. One thing I did notice was that in order to set the RDP back to 0xAA, I had to power cycle the board. Is this correct?
No as the FUS and BLE FW are protected by the secure area. This area (starting at the location pointed by the SFSA option byte) is NOT impacted by the masse erase triggered by the change of RDP level. The mass erase only impacts the user (non-protected) area.
I just went to set and reset the write protection and the process reminded me of something I had to do last time. When I try and set the RDP back to 0xAA, i get a message telling me the RDP is set, so I should use the -rdu command to unprotect. This is what i had to do last time as well (I had forgotten). This time, I tried before unplugging and replugging the USB with no success. When I plugged the USB back in, it failed again, the first time, but the second time it worked. Command prompt dump below.
If I wanted to download the p2pserver application using the CLI executable, are there any special flags I should use? I am not really clear on the firstinstall flag. My guess at the correct command is:
I have the same problem. In my case the serial number is E and the trick with Shared enable does not work. Installing the old programmer STM32 ST-LINK Utility helped me. Also using this program the full serial number is visible.
You can try the following suggestions. Some ST devices are a lot more sensitive than others when it comes to programming. I have had some ST devices programming without issues and then using practically the same setup on other devices it just won't work.
(This one I must stress as being important) Make sure that your processor's ground pins are all connected very closely together (i.e. the tracks between them are as short as possible) and that very importantly your programmer ground is also connected to the same ground pins very closely.- At high programming speeds a thin or long unbalanced (different length) ground track to the processor can cause a problem with some devices.
Whatever you are using to supply power to the processor must have a supply with a similar voltage as the ST-LINK (mine is 3V) - (although I have found that if the processor supply is 3.3V programming seems to still work most of the time.) (Remember the original ST-Link does not supply power only reads the power level.)
Prior to changing / erasing a device that had been programmed to LEVEL 1, you might need to first enable the PCROP_RDP option byte. - Once enabled, you should be able to change from LEVEL 1 to LEVEL 0 that will automatically erase the device.
I just wanted to chime in for the next person who comes along with this problem. @Jarek's solution is what worked for me. In my case, I have two St-Link V2 USB dongles, and both have a Geehly chip instead of an ST chip inside. I updated the firmware on both using ST's Firmware upgrade utility and tried every possible combination of settings in STM32CubeProgrammer but was unable to get anything to happen upon clicking 'Connect'. This includes not getting any error messages. The serial number for both of my dongles was a single letter ("A" and "D"). I never managed to get them working with STM32CubeProgrammer, but was able to use them with the deprecated STM32 ST-LINK Utility as well as using them as a debugger with IAR.
I had no luck in programming while using Type-C cable to power the board. I got it to work when I connected the 3.3V pin from the ST-Link V2 to a 3V3 pin in the board. Don't power the board using Type-C while using the 3V3 pin.
Like you, I couldn't find a proper solution online. I created a somewhat detailed notes, but couldn't make a post on ST Community, Seeed Studio forum or here. Since I'm a new user, I don't have much reputation to embed links or add multiple images. It also finds it as a spam. Hoping I get enough upvotes to make a simple post for future users.
The basic issue is that without something being plugged into a video port, the on board GPU gets shut down. Since the GPU is not displaying anything, all you get is a blank screen. You can use a display port or HDMI display emulator to resolve the issue you are seeing.
I have Fuel OpenStack running with nodes. When I connect to AMT Remote Desktop, I get a black screen, as soon as I connect a physical monitor, I can see the screen (both on the physical screen as well as on the vnc viewer). As soon as I disconnect the physical cable I lose the vnc viewer screen as well.
The catches are: I can't install the tools to run update-grub on the node, so changing the kernel boot is not an option for ubuntu. The fuel server is running centos and the nodes are running ubuntu, I get the same results from either.
b1e95dc632