Help!! FOCBOX Unity / Xenith cant connect after firmware update

Esk8 Electronics
1

I was updating my xenith firmware from my phone app and my flipsky anti-spark auto turned off JUST AS it finished updating. To my understanding thats extremely fugged. Now it wont connect to my computer or my phone, of which it gives me a prompt saying “could not read firmware version” on vesc mobile. On PC it simply doesnt show up. Im quite sure ive bricked it in the dumbest most avoidable way possible. There is a single LED on when i power it up, and no magic smoke smells if that help for additional info.

unnamed (3)
unnamed (3)1920×2560 437 KB

I have tried looking up on the forum for how to fix this but i cant really seem to find any info. Was hoping yall might be able to help. Such a shame, i was planning to upload this new build of mine here for the first time but fate had other ideas i guess. Please help me!!!

3 Likes
2

Not that it helps now, but why are you using a flipsky antispark instead of just using the unity switch? You can be pretty much guaranteed that any flipsky product you use is gonna end in you having a bad day one day.

If you have another vesc laying around, you can use it to try and reflash the bricked esc…

3 Likes
3

He’s using the smart enhanced antispark switch, the good one designed by @gamer43

It has a 10 min self turn off, like the unity button also, but yea he opted to use the flipsky antispark and bridged the MOM terminals for the stock unity button

1 Like
4

Tbf, the timeout on the unity button is set within vesc tool and it would not have turned itself off mid-update.

In my experience, if it’s sold by flipsky, its gonna fuck you up one day :joy:

3 Likes
5

What @glyphiks said it sounds like it’s bricked so you’ll need either another VESC or an ST-Link V2 to reflash the board with a new bootloader and firmware.

6

Do I have to use another Unity to reflash? Since Unity runs on VESC 4. I have a couple Focbox singles and a few 4.12

7

You can use any VESC. Here’s the guide:

8

I really appreciate all the help. I still cant seem to figure the pinout equivalents though. At this point ive just been trying different combinations. This shit is really hard to understand haha

9

There should be a diagram somewhere here for the unity & stormcore pinout (they’re the same design)

10

Just in case

focbox-unity-pin-layout
focbox-unity-pin-layout1092×1529 129 KB

11e5ca2c0f175544d5710b1051da57e4ef53ff47_2_419x500

5 Likes
11

you can see the clk,io etc pins in this picture
you will have to open the focbox single too

12

Sorry this might sound stupid, but which are the CLK and IO pins? I saw the diagrams that were sent but i dont see any of those exact letters in any of the pin outs. Are they in short form in the diagram?

13

For the focbox singles:

a234e42874278cdb9a9c53f3d80d978b9730081c_2_976x1000
a234e42874278cdb9a9c53f3d80d978b9730081c_2_976x1000976×1000 262 KB

e4cbba99d41c0113173903ca6fd526dd5b7e27e2_2_902x1000
e4cbba99d41c0113173903ca6fd526dd5b7e27e2_2_902x1000902×1000 317 KB

For the unity: the black connector where the bluetooth modules is installed, see below.

4 Likes
14

This is really helpful. Before i go ahead and blow something up, just to confirm, SWDIO= IO , SWCLK = CLK , and gnd well = gnd yes? As for the Vesc tool version ill just use the one Veddder used in his video.

Btw this is Linny’s Focbox (if it doesnt work ill owe him money) Wish me luck guys :smiling_face_with_tear:

2 Likes
15

Thanks everyone!!! You guys just fucking saved me. Got the focbox single to flash over the firmware via swd port. Seriously, you guys saved me so much money and heartbreak. Thanks again!!!

IMG_8808
IMG_88081920×2560 439 KB

IMG_8809
IMG_88091920×2560 376 KB

5 Likes
16

now make your god damn build post thats 4 years delayed

6 Likes
17

Hell yeah, nice work. Big ups to @xsynatic for keeping all those receipts :grin:

4 Likes
18

One of my Unity Focbox got bricked when I updated to vesc 6.00 and recovered it by reflashing the original Unity firmware using ST link then updated again, and it got bricked again. At that point, I was sure it was an issue with the vesc update, so I contacted Vedder on Discord, and he fixed the bugs. Now I’ve been running 6.02 since it came out and have had zero issues.

1 Like