I just unboxed by iStick Rim C I purchased from Divine Tribe along with the V4 atomizer. I downloaded the latest tools and firmware and connected the iStick Rim C with 2 different USB cables. It is recognized by my PC as an HID compliant device. I launch the "NToolbox.exe" file (also tried to "Run as Administrator") and select firmware updater but it never gets beyond "Waiting for Device" (I've tried three different computers; my home PC and laptop both with Win 10 and another laptop with Win 7; I've also used 2 different USB cables) . I've tried turning the battery off and on and plugging the battery in with the firmware updater already running but the battery is never found. There are no error codes, it just never proceeds past "Waiting for Device". I've tried both USB 2 & USB 3 ports on the PC's, the previous version of tools and also connected it in safe mode from page 17 of your manual with no luck. The battery is still detected as an "HID Compliant Device" but still isn't found by the firmware updater. I'm not sure what else to try so any help would be greatly appreciated.
Hello! You have to use NToolbox and firmware from this thread: https://nfeteam.org/forum/threads/public-beta-stm32-branch.4654/
Hello, I figured I would comment on this post because I'm having the same exact issue but I think I used the correct toolbox and firmware, see attached image. Unfortunately, when I use the firmware updater it just says, "waiting for device". I've switched the cable 4 times and this hasn't changed anything. I've restarted and connected the mod in safe mode as suggested in 7.3 of user manual. None of this worked. Can anyone help me? Please
I'm having the same issue and haven't found much help online. I've tried 2 different computers and 5 different cords to update. The firmware update thing still doesn't recognize my device. I decided to email eleaf. Not sure what else I can do.
Is there a work around for this - PC recognizes a device being plugged in but gets recognized as a USB input device as well as a HID-compliant vendor defined device but AF cannot find it. I'm assuming it needs to come up in com port? any way to change that or is Rim C just not compatible at all anymore?
am already using the stm32 version of the nfe toolbox; just assumed it couldn't find it. is there a further update than v190718-01.01?
Guess I should've quoted this the first time but I almost never actively participate on forums and forgot I even could. That post was what I was asking if there was a work around for. Figured if the PC recognizes it as a USB input their may be a way to switch the driver to read it as a COM port guess not, thanks anyways. Sorry for not being super well versed at forums, you definitely seem tired of repetitiously answering the same questions and I can't blame you so thank you for all you do and have done.
I wouldn't believe Eleaf support. They just keep throwing semi-random answers till you give up and stop asking questions. They told me it's not upgradable, yet sent me firmware upgrade software in the next reply. New devices (Pico X USB-C and Rim C) are detected as HID vendor-defined devices. AFAIK this is an STM HID upload protocol. This is a Pico X board. Maybe it's a matter of changing bootloader, using custom USB cable, like in some other ST devices? I have ST-Link available, if that helps, just need some guidance from someone more knowledgeable to tell me where to start.
Hello! Well, you may connect to CLK1 (SWCLK) and DAT1 (SWDIO) testpoints and see what happens with STM32CubeProgrammer. At least, MCU type should be detected, maybe (unlikely) MCU will have no readout protection and you'll be able to dump it. There is no guarantee that this is genuine STM32, IMHO. Anyway, it's worth a shot
Chip not detected, nothing, even on lowest frequency, software and hardware reset. Those new versions of Eleaf devices seem almost like a fake. The temperature control is complete garbage. I was tempted by USB-C, but it is nothing like an old Pico, even on stock firmware.
