Jump to content
Flirc Forums

Dave Starkey

Members
  • Posts

    10
  • Joined

  • Last visited

Dave Starkey's Achievements

Rookie

Rookie (2/14)

  • Week One Done Rare
  • Collaborator Rare
  • First Post Rare

Recent Badges

0

Reputation

  1. Thanks, good to know I was barking up the wrong tree. For years I have been debugging using JTAG probes. Usually on Kinetis parts using their own hacked up version of eclipse. I am new to the openDCD and raw GDB debugging. But all the documentation makes it look easy once i get the JTAG thing up and going. Tomorrow I will have an new tree to bark at. Thanks for your help Dave
  2. HI Jason, I have flashed both of my devices to: Black Magic Probe (SAMD2), (Firmware v1.6.2-5-gca7bf01) I still see 2 serial ports at 6018 none at 6017. When I hold the switch down to put it in bootloader mode, I see a single device at 6017, but that is useless for debugging. Is this the correct firmware now? Am I misunderstanding how this thing is supposed to work? Thanks Dave
  3. I just got my second one in. As expected it has the same problem. One difference was when I first plugged it in to the Windows 10 machine it did a little dance and acted like it might have updated the firmware but no, It has the same problem. It's been a while since i did an substantial Linux stuff. the only operating Linux machine I have is a raspberry pi. I tried but for me that is a giant pain. How about I mail you both of the devices and you can update them for me? Hopefully Dave
  4. Everything works better in the morning. Ill try again then. You have been awesome!
  5. Ok i have it up in DFU Demo mode. It does show a PID of 1d50:6017, But alas :: Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! Cannot open DFU device 1d50:6017 No DFU capable USB device available
  6. i dont understand (just to be clear).. Unplug the device, Push the button, Plug it in while holding the button. continue holding the button while executing the command?
  7. I just ordered another one from amazon. Delivery tomorrow.
  8. PS C:\Esp\frameworks\esp-idf-v4.4.1> dfu-util --device ,1d50:6017 -s 0x00002000:leave -D C:\Users\dave\Downloads\blackmagic-master\blackmagic-master\src\blackmagic.bin dfu-util 0.9 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! No DFU capable USB device available I don't think it likes me anymore. I get the same response if I try the 6018 PID. If I've popped it I dont mind buying another one. Thanks for getting back to me!!
  9. I realized I never formally downloaded the Blackmagic-master. so I just ran the script and this happened: PS C:\Esp\frameworks\esp-idf-v4.4.1> dfu-util -d 1d50:6018,1d50:6017 -s0x02000:leave -D C:\Users\dave\Downloads\blackmagic-master\blackmagic-master\src\blackmagic.bin dfu-util 0.9 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2016 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Invalid DFU suffix signature A valid DFU suffix will be required in a future dfu-util release!!! Opening DFU capable USB device... ID 1d50:6018 Run-time device DFU version 011a Claiming USB DFU Runtime Interface... Determining device status: state = appIDLE, status = 0 Device really in Runtime Mode, send DFU detach request... Device will detach and reattach... Cannot open DFU device 1d50:6017 Lost device after RESET? PS C:\Esp\frameworks\esp-idf-v4.4.1> It did something but still both PIDs are 6018 and version v1.6.2
  10. Hi Jason, I got one of these jeff probe blackmagic JTAG clone from Amazon. I intend to use it on the ESP32-s2 chip using eclipse. I am running windows 11. When i look at it in the device manager it looks like two com ports. They both have the same PID 6018. I think when it is working correctly it should show 6017 (for the JTAG side) and 6018 for the UART side. The second port does not seem to work as a UART and of course the JTAG is a non starter. So I suspect I need to flash it with some new firmware. I tried the sketchy and scary Zadig jive it times out on both the Win11 and Win10. I have So after too much (but likely not enough info).. How do I flash the part? or should I just pack it in and go another route?
×
×
  • Create New...