STM32F105RCT6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 06:07 AM
in the process of or at least i want to backup the mcu data and transfer it over to another mcu, i can connect and see the mcu with my pe cyclone fx but when i read and dump the data i get a empty file 768kb.
S3150800000000000000000000000000000000000000E2
S3150800001000000000000000000000000000000000D2
S3150800002000000000000000000000000000000000C2
S3150800003000000000000000000000000000000000B2
S3150800004000000000000000000000000000000000A2
S315080000500000000000000000000000000000000092
S315080000600000000000000000000000000000000082
S315080000700000000000000000000000000000000072
S315080000800000000000000000000000000000000062
S315080000900000000000000000000000000000000052
S315080000A00000000000000000000000000000000042
S315080000B00000000000000000000000000000000032
S315080000C00000000000000000000000000000000022
S315080000D00000000000000000000000000000000012
S315080000E00000000000000000000000000000000002
Solved! Go to Solution.
- Labels:
-
EEPROM devices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 08:44 AM
this is the data i pulled from it with my pe cyclone fx would love to just read it with the stlink but if i dont unlock the option bytes before the dump i get all 00 if i unlock it and read it this is what i got.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 08:47 AM
no i have not removed it, I thought I got a bad st link and did not want to damage it further, this is the data i got from the full dump a bunch of nothing..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 08:51 AM
Disconnect both jumpers on CN2. Connect GND/SWDIO/SWCLK between CN4 and your target board. Ensure target board has power. Optionally, also connect VCC and NRST. See nucleo user manual for CN4 pinout.
- Pin 1: Target VCC
- Pin 2: SWCLK
- Pin 3: GND
- Pin 4: SWDIO
- Pin 5: NRST
- Pin 6: SWO
After that connect with STM32CubeProgrammer and observe flash data.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 08:58 AM
so i have both options to power the mcu via the st-link completely via pins 1-6 or externally using the pins for data
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 09:10 AM
You cannot power the board with pin 1 of CN4. It is an input to the st-link.
You must power the board some other way.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 10:32 AM
Wired it up as suggested I think it’s locked , I try a virgin mcu and I can connect and no errors .
 
 
 
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 10:43 AM
Voltage: 0.01 V suggests it isn't powered, or that you don't have power hooked up. It looks hooked up in your pictures.
Is RDP set? Check option bytes in OB tab on left.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 10:58 AM
This is the target board the one that new unlocks
  I went ahead and activated the RDP on this teta board just to see and am getting the same message from the other one so am to assume I just locked the test board , how do I unlock it again ??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 11:57 AM
Go to option bytes and change RDP to level 0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-09-07 12:24 PM
did that minutes after the last post and it erased the entire chip and i gained access again on the test board , if i do this it will also mass erase the mcu i wanted to read initially, i guess they locked it and want no one looking inside.