Jump to content
Flirc Forums

jason

Administrators
  • Posts

    2,734
  • Joined

  • Last visited

  • Days Won

    117

jason last won the day on April 15

jason had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    Santa Clara
  • Interests
    flirc, that's all I have time for.

Recent Profile Visitors

17,611 profile views

jason's Achievements

Contributor

Contributor (5/14)

  • Well Followed Rare
  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare

Recent Badges

169

Reputation

  1. 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.
  2. 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.
  3. 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.
  4. No you can't pop it. maybe it's not in the bootloader. Hold down the button when you plug it in.
  5. dfu-util --device ,1d50:6017 -s 0x00002000:leave -D src/blackmagic.bin try this
  6. 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
  7. @bm16ton So so so sorry. Yes, PM me your address, going to replace it with A05 that has this addressed.
  8. 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.
  9. I'm sorry, I got sick. will return to this tomorrow.
  10. 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.
  11. Make sure ADB debugging is off. You turn this on to side load but it disables USB.
  12. Is that the only button that doesn’t work with the Nvidia box and this remote?
  13. Let's make sure it's nothing wrong with the remote. Can you try recording it again and seeing what happens? Does it let you or does it say that the button has already been recorded.
  14. Can you describe this a bit more. Do you mean you recorded the command with flirc and my software?
×
×
  • Create New...