Wahoo Kickr Circuit Board Repair
10-31-23, 03:04 AM
#151
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
Hello,
I have J-link and i try copy firmware, i use command savebin, but i have problem. The following message appears: Reading 4096 bytes from addr 0x10001000 into file...Could not read memory. and Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
Any suggestions what I'm doing wrong?
Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 3.87ms
Found SW-DP with ID 0x2BA01477
DPv0 detected
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_firmware_1.bin 0x0 0x80000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_firmware_1.bin]
Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
I have J-link and i try copy firmware, i use command savebin, but i have problem. The following message appears: Reading 4096 bytes from addr 0x10001000 into file...Could not read memory. and Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
Any suggestions what I'm doing wrong?
Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 3.87ms
Found SW-DP with ID 0x2BA01477
DPv0 detected
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_firmware_1.bin 0x0 0x80000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_firmware_1.bin]
Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
Last edited by woodpecker3; 10-31-23 at 04:05 AM.
10-31-23, 08:06 AM
#152
Newbie
Join Date: Oct 2023
Posts: 36
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 13 Post(s)
Likes: 0
Liked 6 Times
in
6 Posts
Hello,
I have J-link and i try copy firmware, i use command savebin, but i have problem. The following message appears: Reading 4096 bytes from addr 0x10001000 into file...Could not read memory. and Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
Any suggestions what I'm doing wrong?
Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 3.87ms
Found SW-DP with ID 0x2BA01477
DPv0 detected
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_firmware_1.bin 0x0 0x80000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_firmware_1.bin]
Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
I have J-link and i try copy firmware, i use command savebin, but i have problem. The following message appears: Reading 4096 bytes from addr 0x10001000 into file...Could not read memory. and Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
Any suggestions what I'm doing wrong?
Connecting to target via SWD
InitTarget() start
InitTarget() end - Took 3.87ms
Found SW-DP with ID 0x2BA01477
DPv0 detected
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x02880000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FF000
CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
Found Cortex-M4 r0p1, Little endian.
FPUnit: 6 code (BP) slots and 2 literal slots
CoreSight components:
ROMTbl[0] @ E00FF000
[0][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[0][1]: E0001000 CID B105E00D PID 003BB002 DWT
[0][2]: E0002000 CID B105E00D PID 002BB003 FPB
[0][3]: E0000000 CID B105E00D PID 003BB001 ITM
[0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
[0][5]: E0041000 CID B105900D PID 000BB925 ETM
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_firmware_1.bin 0x0 0x80000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_firmware_1.bin]
Reading 524288 bytes from addr 0x00000000 into file...Could not read memory.
10-31-23, 08:13 AM
#153
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
No, the problem is the same:
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_UICR_1.bin 0x10001000 0x1000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_UICR_1.bin]
Reading 4096 bytes from addr 0x10001000 into file...Could not read memory.
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_UICR_1.bin 0x10001000 0x1000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_UICR_1.bin]
Reading 4096 bytes from addr 0x10001000 into file...Could not read memory.
10-31-23, 08:25 AM
#155
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
Yes.
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: NRF52832_XXAA
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF52832_XXAA" selected.
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: NRF52832_XXAA
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "NRF52832_XXAA" selected.
10-31-23, 11:10 AM
#158
Randomhead
Join Date: Aug 2008
Location: Happy Valley, Pennsylvania
Posts: 24,411
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked 3,714 Times
in
2,532 Posts
Which version kickr is this? I assume it has a Gem2 module?
11-04-23, 02:45 AM
#159
Newbie
Join Date: Oct 2023
Posts: 36
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 13 Post(s)
Likes: 0
Liked 6 Times
in
6 Posts
No, the problem is the same:
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_UICR_1.bin 0x10001000 0x1000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_UICR_1.bin]
Reading 4096 bytes from addr 0x10001000 into file...Could not read memory.
Memory zones:
Zone: "Default" Description: Default access mode
Cortex-M4 identified.
J-Link>savebin c:\users\Komputer\Desktop\binary_UICR_1.bin 0x10001000 0x1000
Opening binary file for writing... [c:\users\Komputer\Desktop\binary_UICR_1.bin]
Reading 4096 bytes from addr 0x10001000 into file...Could not read memory.
Every time after reboot the circuit board and reconnecting to J-link program it is able to access the memory but around 8 to 10 seconds later could not read memory again.
I copy the savebin command and paste immediate into J-link program after reconnecting the circuit board and finally manage to save the firmware (within 8 seconds). And repeat the same method to save the UICR.
I am using pogo pins to link the contact from the circuit board instead of soldering to prevent damaged in the Gem2.
Next step will be waiting for the microcontroller arrive to flash it and solder onto the circuit board.
woodpecker3 you might want to try out this method to see any luck.
11-06-23, 05:04 AM
#161
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
11-06-23, 05:32 AM
#162
Newbie
Join Date: Oct 2023
Posts: 36
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 13 Post(s)
Likes: 0
Liked 6 Times
in
6 Posts
Great!! Have you done the microcontroller solder and flash? Update if you successfully done up.
My V5 Kickr no power transmit and always drop out from Bluetooth connection.
Just received my microcontroller today. So will start soldering soon.
My V5 Kickr no power transmit and always drop out from Bluetooth connection.
Just received my microcontroller today. So will start soldering soon.
11-06-23, 06:00 AM
#163
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
I already have a microcontroler, but I haven't solder it yet. As soon as I mage to solder it, I will let you know if I upload the firmware.
11-10-23, 07:31 AM
#164
Newbie
Join Date: Oct 2023
Posts: 36
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
Quoted: 13 Post(s)
Likes: 0
Liked 6 Times
in
6 Posts
Micro controller soldered and firmware flashed. (My ANT+ and Bluetooth LED faulty therefore replaced with White & Green color LED)
All working fine now!!
Likes For ch99_lee:
11-10-23, 04:44 PM
#165
Randomhead
Join Date: Aug 2008
Location: Happy Valley, Pennsylvania
Posts: 24,411
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked 3,714 Times
in
2,532 Posts
Looks great.
So the small number of bytes was just a false alarm?
So the small number of bytes was just a false alarm?
11-11-23, 12:50 PM
#167
Newbie
Join Date: Nov 2023
Posts: 4
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Likes: 0
Liked 1 Time
in
1 Post
The recent activity on this thread is incredibly fascinating... I also own a KICRK V5 that recently stopped producing resistance (started noticing this in late September). Cadence and Power output read 0/0 and factory spindowns are impossible to complete.
11-11-23, 12:53 PM
#168
Newbie
Join Date: Nov 2023
Posts: 4
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Likes: 0
Liked 1 Time
in
1 Post
I keep trying to buy a broken unit so I can try to repair it. I think people prefer to throw them away or want too much money for them.
I have heard of this problem a couple of times, where it's still connecting but speed and power aren't working properly. I believe the cpu module is at fault, so replacing it will probably fix the issue.
I have heard of this problem a couple of times, where it's still connecting but speed and power aren't working properly. I believe the cpu module is at fault, so replacing it will probably fix the issue.
11-12-23, 07:13 AM
#169
Randomhead
Join Date: Aug 2008
Location: Happy Valley, Pennsylvania
Posts: 24,411
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked 3,714 Times
in
2,532 Posts
I'll put a message on your profile, unfortunately you can't get PM's until 10 posts.
11-13-23, 11:48 AM
#170
Newbie
Join Date: Nov 2023
Posts: 4
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 0 Post(s)
Likes: 0
Liked 1 Time
in
1 Post
Welp, I just posted a short novel but my login timed out so I'll just give everyone the TL;DR version instead:
- My 2022 KICKR v5 was purchased in November 2020
- I started having issues with it this year (2023), but increasingly in late Summer (Aug/Sept)
- I started a support ticket with Wahoo on October 19
- After several days of back and forth (14 total business days, to be exact), Wahoo is issuing a refurb as replacement
Likes For bravotwo:
11-14-23, 02:21 PM
#171
Newbie
Join Date: Nov 2023
Posts: 8
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 3 Post(s)
Likes: 0
Liked 1 Time
in
1 Post
2014 Kickr Dead - No Bluetooth/ANT - Repair?
Hi,
My 2014 Kickr seems to have died. I'd taken the flywheel off and looks like its getting 12v to the main PCB. What should I test next? Can anyone help with repairing the board and/or replacement?
Wahoo says to buy a new one, as they don't support this anymore.
Any help is greatly appreciated!
Best,
Matt, NJ, USA
My 2014 Kickr seems to have died. I'd taken the flywheel off and looks like its getting 12v to the main PCB. What should I test next? Can anyone help with repairing the board and/or replacement?
Wahoo says to buy a new one, as they don't support this anymore.
Any help is greatly appreciated!Best,
Matt, NJ, USA
11-15-23, 08:22 AM
#172
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
I just uploaded the software to a new microcontroller, everything go very vell. However, there was a problem. Kickr Core still not showing cadence and speed.I check the sensor, the outpus is correctly 3.3V, when I was approach the mirror closer the voltage decreases. On the old microcontroller the voltage was 0V. So the new microcontroller works. After assembling everything Kickr Core turn on but does not show cadence and speed. When i took the measurements again, I noticed one strange thing. When i touch the finger the plus on the meter durning measurements, the application shows speed and cadence. Anyone have any idea what happened?
11-15-23, 08:27 AM
#173
Randomhead
Join Date: Aug 2008
Location: Happy Valley, Pennsylvania
Posts: 24,411
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 4 Post(s)
Liked 3,714 Times
in
2,532 Posts
I wonder if a pullup resistor died. If I get a chance, I'm going to try to map out the circuit. I think possibly the failures have to do with them exceeding the limits of the microcontroller.
11-15-23, 08:40 AM
#174
Newbie
Join Date: Oct 2023
Posts: 11
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 8 Post(s)
Likes: 0
Liked 0 Times
in
0 Posts
11-15-23, 11:31 AM
#175
Newbie
Join Date: Nov 2023
Posts: 8
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Quoted: 3 Post(s)
Likes: 0
Liked 1 Time
in
1 Post
I don't think I have seen anyone fixing one that old. Can you take a picture of the controller board? You can't upload it to a post, but if you upload it to an album on your gallery, we can rescue it for you.
I wonder if a pullup resistor died. If I get a chance, I'm going to try to map out the circuit. I think possibly the failures have to do with them exceeding the limits of the microcontroller.
I wonder if a pullup resistor died. If I get a chance, I'm going to try to map out the circuit. I think possibly the failures have to do with them exceeding the limits of the microcontroller.
Likes For six0nine: