jason

Thanks for the log, that was helpful. Can you attach your config? ** EDIT ** - To clarify, the configuration from Flirc

Marco at welectron created one for the flirc pi case. Please reach out to him.

What happens when you unplug it when it is in this state?

@GregO @Dave Starkey I've updated our firmware to be the same as the public black magic probe firmware, cherry picked rtt support as well, and released binaries: https://github.com/flirc/blackmagic/releases/tag/v1.8.4

To add on to Nate's response, it's a commercial licensed database. It's updated frequently, and well done. We will have in an update a mode, similar to how flirc works, where you can learn buttons into the remote. Flirc has it's own protocol, and if you need a code, there will be a ton of extra named, 'custom1, custom200, etc. You can use those to repurpose whether it's through flirc, or another device. I'll publish the IR spec as well.

Nice job. I'm going to get back to flirc when the remote is out.

Try the file here Let me know if it's okay.

Thank you so much for the feedback. Yes, there is a lot that we didn't include on the 1s. But we have a lot of plans, and it was really important for us to start from scratch. Too many companies try to throw everything in the remote and fuck it all up, it's complicated. So we started with the basic, want to nail it, and then we'll be rolling out additional technologies. Not to mention the chip shortage really screwed everything up. But one of the best things we did, was do everything in react native desktop. This is not a webapp, this was a massive effort. And that was specifically so we can leverage a lot of our work back to tablet/mobile. I could say for certain, I do not want to do a hub. I don't like those things. No reason why everything can't be on the remote.

His branch is the same as mine, he just added the binary, which I have now. To rebase onto the main tree, is no days work. I'll get to it when this ships: https://flirc.tv/products/skip1s-remote?variant=43489094729960

How did you setup the harmony?

I don't support pronto codes. I support raw timings with Flirc. You can convert these to raw timings, a comma delimited file that represent on and off times for the IR led. This is the best I have for now. I'm not going to be working on Flirc until our remote is released, which will benefit from a lot of the work I have done.

flirc_util Try the attached.

Going to put an update together soon.

Yes, the two serial ports are correct. Yes, this is most likely the issue. You need an ELF file. Then you can start up gdb and point to the elf file: You start gdb and point to the elf file: arm-none-eabi-gdb 'elf file you want to flash' Now from GDB, you can connect to an attached device. Attach the JTAG cable to the target. But you need to tell GDB where to go, so let's point it to the serial port: target extended-remote /dev/cu.usbmodemJEFF1 (I'm not sure what the destination is on windows, but replace /dev/cu....) Then tell the probe what kind of JTAG you want to use, probably 2 wire serial: monitor swdp_scan Assuming you see the target, you can attach to it: attach 1 Then you can load the file: load You can now walk through and step through various aspects of code, assuming the elf file has debug symbols in it. We're going to start diving into advanced firmware topics, and I'm not sure your experience. Here is the documentation, for the same product the firmware is derived from: https://github.com/blackmagic-debug/blackmagic They have a lot of documentation, and a wiki to get started.

I think it's because you need to have the windows driver installed. Or re-run as an administrator. Windows is a piece of dog shit for stuff like this. This is why all my products use HID and all my apps can talk to them driverless. Because I'm 100% done with drivers in windows. I've spent enough time on the phone helping people with 'unknown device' in device manager trying to force install my own drivers.

You can let go of the button after you plug it in after waiting a second or two. You should see a different usb product ID show up. PID_6018 for the main app PID_6017 for the DFU I think you need the driver installed for both in windows. If you have linux, you might have an easier time.

No you can't pop it. maybe it's not in the bootloader. Hold down the button when you plug it in.

dfu-util --device ,1d50:6017 -s 0x00002000:leave -D src/blackmagic.bin try this

oh yeah, 15 hour days, 7 days a week. We're going to announce and release it soon. It's this: https://flirc.tv/pages/teaser1140

@bm16ton So so so sorry. Yes, PM me your address, going to replace it with A05 that has this addressed.

I'm sorry, there isn't unfortunately. But if you buy a license to remote buddy, I'm practically giving them away. You should have gotten a discount code. Please let me know.

I'm sorry, I got sick. will return to this tomorrow.

As long as they are common ground, you don't need to, I think I had a bug on the first version, which this may be. What version shows on the board? I'll swap it out if it's an old one.

Make sure ADB debugging is off. You turn this on to side load but it disables USB.

Is that the only button that doesn’t work with the Nvidia box and this remote?