My Device Find
Osoulo Lejeune
You can use Find Devices on iCloud.com to find the approximate location of your iPhone, iPad, iPod touch, Mac, Apple Watch, AirPods, and Beats product if Find My is set up on the device and the device is online.
Each family member must set up their devices to share their locations with other family members. See the Apple Support article Share your location with your family. Once they set up location sharing, you can locate their devices using the instructions above.
Change the map view: The button at the top right of the map indicates if the current map is a standard view , a hybrid view , or a satellite view . To choose a different map, click the button, then click the view you want.
When you mark your accessory as lost, you can leave a phone number, email address, and a message on the lock screen. Your contact information can also be accessed by someone else who identifies your accessory as lost so they can return your device to you.
A physical security key is one of the strongest methods to protect your account. Keep your physical security key in a safe location. If your primary Android device is lost or stolen, you can use the physical key to sign in to Learn more about security key options.
Find My can even let you know if you leave your devices in an unfamiliar location. Just turn on Notify When Left Behind on your iPhone, Apple Watch, or iPad. Want to leave your MacBook at the studio? Easy. You can fine tune your notifications by device and location.
Worried that your device has fallen into the wrong hands? You may want to erase it remotely to delete your personal data and reset your iPhone, iPad, iPod touch, Apple Watch, or Mac. If you retrieve it, you can restore your data from your iCloud backup.
I upgraded STM32CubeIDE to version 1.14.1 today and can no longer connect with my target. The process of updating CubeIDE also updated my STLink-V3PWR debugger to V3PWR V4.J3.B1.P4. Now, programs that downloaded and ran just fine yesterday won't download with the "Target no device found" error.
The STMCubeMonitor-Power (version 1.2.1) software can take control, power on the target, get the temperature, reset my target board and can run the ULP Bench Test and report a ULPMark Score. That leads me to believe STMCubeMonitor-Power can download and run a program and my target board is still working. I don't have any other target boards available to try right now.
Thanks for the quick response. I should have mentioned I'm working on a new board we designed using a STM32H7A3LI MCU. Our board does have a jumper that does that same thing as SW1 on the H7B3I-DK board. Good news: I was able to complete steps 1, 2 and 3 and was able to connect with STMCubeProgrammer, which I was not able to do before. However, when I click the "Full chip erase" button, I get a Error: Mass erase operation failed. Please verify flash protection". Section 4.5.1 in the RM0455 Reference Manual talks about FLASH configuration protection but it's a little complicated and I don't want to make anything worse. Is there a setting or button in STMCubeProgrammer that will disable flash protection safely?
I think I figured it out. I had to uncheck nWRP0 in the Write Protection section of the Option Bytes. Then click the "Full Chip Erase" button, then check nWRP0 again. Now it looks like I'm back to being able to download, program and debug programs again.
For my information, can you tell what I did wrong? How will I know in the future if I have to go through this full chip erase process? Or is this just a more dramatic version of hitting the reset button when all else fails?
I need to investigate with a board to be able answer your question: (For my information, can you tell what I did wrong? How will I know in the future if I have to go through this full chip erase process? Or is this just a more dramatic version of hitting the reset button when all else fails?)
I spoke too fast. I was able to download and debug one program one time. I reset the board and I'm back to square one, CubeIDE can't find the device. I went back to your step by step and I can connect to my board with BOOT0 connected to 3.3V. However, when I uncheck nWRP0, I get this: "Error: Option Byte Programming failed Or modified by application after OB-Launch". Is there a better way to force a "Full chip erase"?
I still can't just clear all the flash. Here's a screen shot of what happens. I've tried checking and unchecking the nWRPx boxes and CubeProgrammer just sets them back to their default setting: nWRP0, 1 and 2 are checked. nWRP3-34 are unchecked and nWRP35-63 are checked. .
At one point after fumbling around reinstalling software and trying to clear at least some of the flash with CubeProgrammer, I was able to build a new Blinky program, load it with CubeProgrammer and it ran. I wish I could tell you what I did to get this little bit to work but it was kind a random process. Unfortunately, when I try to load the program that I've been working on, I get the errors at the bottom of these messages. This program is much larger than the Blinky program I mentioned above, it's something like 360 kBytes if that matters.
FWIW, it does seem possible that my current issue has to do with not being able to write to certain parts of memory. The Blinky program that does run is 4.8 kB, the larger program that doesn't run is 360 kB and another program I tried that doesn't run is 216 kB.
I was finally able to clear all the flash on my MCU. I had to connect BOOT0 to ground (not 3.3VDC). This seems incorrect but it did work. I've started and stopped the program, the IDE, the STLink-V3PWR several times and shut everything down and rebooted the computer a couple of times and I can still download, run and debug my main program. So that's good. Hopefully, it will last for a little longer this time.
I have just installed Quartus 20.1.0 (it's the latest my company is allowing). In attempting to create a new project, Quartus says I must install device support files (Quartus Device Files, or .qdz ???). Anyway, I can't find any "device files" or "qdz" files on the Intel site. Where can I find these? I'm looking specifically for the MAX10 10M16SA device. Thanks for any feedback.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
Please pay attention to the following 4 models of cable modem that have some special condition. The real hardware version can be found on the left part of the label. But there is another version which is higher than it marked on the right part, which is the version that stands for the new Visual Interface.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
2. What I was trying to ask is, what does 'xdsdfu -c' command really do to my XDS110 Debug Probe
because it doesn't say in 'xdsdfu -?' help command.
And, I think because of this 'xdsdfu -c' command, my XDS110 Debug Probe seems dead with '-260' error code.
3. Since I just bought this for about a week, I dont' really think it's USB cable's problem and I dont' have extra one with me now to try.
Is there anything I can try to recover this device (based on '-260' error code and 'xdsdfu -c' unknown command input)?
Or is there any compensation for this from TI?
The TI store has a "Help" link that you can use to communicate with them regarding returns. They would be able to provide you with additional details on how to proceed. You can link this thread in communications with them.
Sorry I wasn't clear. I meant that any debug probe will be logically and electrically suitable to perform this programming - however, you would still need a pin converter from 14 to 10 pin. If you can find a debug probe that has a TI 20-pin connector such as the XDS200, the XDS100v2 or even another XDS110 you can use the existing 20-14 pin adapter supplied with your original XDS110.
Sorry again. The LM Flash is mentioned because it is compatible with the device that is built into the XDS110 debug probe (TM4C1294). However, the debug probes supported by this utility to program the TM4C1294 device do not include the XDS110.
Like you said, LM Flash does not support XDS110 debug probe, so I tried the UniFlash that you suggested, and successfully loaded 'boot_loader.bin' into my XDS110 debug probe. After that, I can use 'xdsdfu -m' and 'xdsdfu -f firmware.bin -r' commands to flash itself's firmware.bin file. So, now my XDS110 debug probe is back to normal!
I have TMDSHVMTRPFCKIT's Isolated XDS100 USB JTAG Emulator connected for the board's M3 section's power source, and the Input for 15VDC power adapter connected to power up the TMS320F28035 ControlCard.See attached picture:
The issue you are seeing now can be caused by the many jumper configurations on your development kit. In the kit I have here (similar to yours but probably an older version) I have to set up jumpers on the M3 module to properly connect using an external JTAG debug probe instead of the built-in XDS100.
@MarxoBazz - The IP Information of your device is always up to date if the device has been found and accessed and used, but we are not tracking location more closely than that.
What kind of device was it?