I have 2 mods that does not enter DFU@USB with BOOT0 pull-up: Hotcig RSQ and Vandy Vape Pulse 80W. I suspect some activity on other peripherals (USART/I2C) that override DFU over USB. I don't remember if there is SWD pads somewhere under display, if so, you can try to connect ST-Link and flash bootloader with it (pin 34 is SWDIO & pin 37 is SWCLK). But I'm still suspect USB hardware issue I haven't bought it yet. Probably, it will Yep, it is unofficial, just for fun. https://nfeteam.org/forum/threads/vaporesso-swag-armour-pro-hotcig-rsq-vandy-vape-pulse-80w.2289/ No way.
No chance I guess Spoiler: PCB-Top Spoiler: PCB-Bottom I will try on an other PC (at work), the cables should be okay because they worked fine with URSA.
Thank you for the answers! So... can I have a look at the source? Actually, I'd still like to write something for Linux, at least the configurator (which I suppose is the most often used of the tools). Can we talk about this?
You are really fast!!! With URSA yes with GRUS no. Update: F..k, I have got it!!! I was wrong to assume the cable insert direction URSA and Grus is the same, but the guy's inverted it. So at the end you are completely correct: it was a problem with the USB connection Code: Bus 001 Device 014: ID 0483:df11 STMicroelectronics STM Device in DFU Mode Many thanks for support and patience. Hans
https://nfeteam.org/forum/threads/p11-arcticfox-config-v11-0-0-for-macos-and-linux.937/ The current protocols are AF-12/RP-2, if need, I can provide actual data exchange structure for them. Also, STM32 branch can be implemented as well.
Thank you! I'm glad to hear that you are OK with this and would provide the needed info when needed (when newer firmware needs changed protocol for instance). I couldn't get the mentioned app running. Main problem seems to be node-hid, which is pretty out-of-date. I'll use https://github.com/TBXin/NFirmwareEditor as base and let you know when I have something. Best regards!
@maelstrom2001 as it turned out, the node/electron app does run, I just had to update the dependencies' versions (it's been some time since I last worked with nodejs). So it's probably easier to start from there, rather than from your github C# sources, which were kind of difficult for me to grasp at a first (and second ) glance. Unfortunately, I have no way to test it with my Grus. I ordered a Ravage 230 and should be getting it tomorrow, but that is RP and the app doesn't mention "panda" anywhere, just AF... not sure how they differ (except screen color or not, and I'm not even sure about this). I considered buying an older-generation device, but couldn't find anything cheaper than ~30 euro used / 40 euro new (RX Gen3 dual - 50 euro new, same as I payed for the Ravage :/ ). Pretty expensive for something I would use only for testing... Any suggestions?
At least, Device Monitor should work. Change VID to 0x0483, PID to 0x5750 and HID signature to 0x7537CA5C.
I send this to Grus (0483:5750) Code: 0x60 0xe 0x0 0x0 0x0 0x0 0x40 0x4 0x0 0x0 0x75 0x37 0xca 0x5c 0x84 0x2 and get no answer (I increased the timeout on hid from 1 to 5 seconds) I can talk to the Ravage230; sending Code: 0x60 0xe 0x0 0x0 0x0 0x0 0x40 0x4 0x0 0x0 0x48 0x49 0x44 0x43 0xca 0x1 it answers with Code: DisplaySize: 200 FirmwareBuild: 1342178024 FirmwareVersion: 2684354560 HardwareVersion: '1.01' ... ProductId: 'J056' SettingsVersion: '2'
Yep.. had that thought and then it somehow slipped my mind (possibly because I got excited about getting the Ravage ) So I can communicate with both. What do I do now? Can I just ignore the versions (in code vs. on device) and "everything should work", or will you give me stuff to update the code?
Here is the actual data structures. Sorry for some comments in Russian, I'm too lazy to translate it right now )
Hi, I'm reading indeed 1088 bytes from RP, as stated at the beginning of the header file. But it doesn't sum up: dSettings: 1011 because colorScheme (74) is commented out from sUI - would be missing 3 bytes anyway There is a colorTheme at the end of the file, but that's 84, too big to fit.
Hello! Never mind. Some comments on data size are outdated due to modifications. Better calculate the sizes of structures yourself, and read/write as much as you need. P. S. Total data size must be a multiple of 64 bytes.
I'm not reading 1088 on purpose, I get this much and then it stops sending. But now I remember, HID sends a fixed size (in this case 64, I had some keyboard with 32, whatever). So... 1024 < payload size <= 1088 Means colorScheme shouldn't be commented out and there is no colorTheme?
Yep, theme data is not present in the settings structure. It was there for some time (that's why you see commented "74 bytes"), but then it was modified, expanded to 84 bytes and moved in independent section. dSettings is exchanged with commands 0x60 (read from device) and 0x61 (write to device). sColorTheme is exchanged with commands 0x90 (read from device) and 0x91 (write to device), 84 (2 * 64 =128 actually) bytes.
Hey guys, I bought a GRUS about 2 weeks ago, it's the new design. I'm trying everything I can but I just can't get it into DFU mode, I have a usb c breakout board like in post #256, soldered all the vcc and gnd pins together like someone suggested. When I short the pins and connect it, windows does make the usb connected sound, it does this on both ways connected. When I don't short the pin and connect it, the screen starts showing the charging animation. Edit: I tried it on my pc and my laptop, didn't work on either of them. It has PCB version YK-5172-V1.3, like the one in #38 Does anyone know what I can do?
