How to flash your Ninebot Scooter

Vince
Posts: 3
Joined: Tue Jun 04, 2019 6:25 pm

Re: How to flash your Ninebot Scooter

Postby Vince Thu Jun 06, 2019 3:33 pm

Image
I followed the guide exactly and im getting this error. Connections and soldering are good
Hello,
I have exactly the same problem when flashing a dash from Aliexpress. I need to flash this dash because it does not allow to use EsdownG (flashing does not work). I checked several times the connections, no problem. This dash does not have C15 capacitor. I also flashed another original dash successfully, so I am confident that the softwares are well installed and I run the procedure correctly. Any help?
This happened to me when I tried flashing a clone dashboard. It didn't come with a C15 capacitor, so I thought it would work, but I got the same error and the dashboard is now bricked. Which is weird, because it says programming failed, which would imply that no changes were made to the flash. ¯\_(ツ)_/¯ Oh well.
I checked and I confirm that my dash is also bricked. Indeed very strange
ca2014mp2
Posts: 15
Joined: Thu Jun 06, 2019 9:17 pm

Re: How to flash your Ninebot Scooter

Postby ca2014mp2 Thu Jun 06, 2019 10:24 pm

So I connected up and flashed my head unit with errors on the programming side. See actual programming:

Head unit one:
> program full_BLE.bin
target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0x000006d0 msp: 0x000007c0
** Programming Started **
auto erase enabled
Unknown device (HWID 0x000000d2)
using fast async flash loader. This is currently supported
only with ST-Link and CMSIS-DAP. If you have issues, add
"set WORKAREASIZE 0" before sourcing nrf51.cfg to disable it
flash write algorithm aborted by target
timed out while waiting for target halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x41000003 pc: 0xfffffffe msp: 0x000007a0
error waiting for target flash write algorithm
Failed to write to nrf51 flash
error writing to flash at address 0x00000000 at offset 0x00000000
embedded:startup.tcl:476: Error: ** Programming Failed **
in procedure 'program'
in procedure 'program_error' called at file "embedded:startup.tcl", line 532
at file "embedded:startup.tcl", line 476


Head unit two:
auto erase enabled
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : "set WORKAREASIZE 0" before sourcing nrf51.cfg to disable it
Error: flash write algorithm aborted by target
Error: timed out while waiting for target halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x41000003 pc: 0xfffffffe msp: 0xffffffd8
Error: error waiting for target flash write algorithm
Error: Failed to write to nrf51 flash
Error: error writing to flash at address 0x00000000 at offset 0x00000000
embedded:startup.tcl:476: Error: ** Programming Failed **
in procedure 'program'
in procedure 'program_error' called at file "embedded:startup.tcl", line 532
at file "embedded:startup.tcl", line 476
target halted due to debug-request, current mode: Thread
xPSR: 0xc1000000 pc: 0xfffffffe msp: 0xfffffffc
** Programming Started **
auto erase enabled
Warn : using fast async flash loader. This is currently supported
Warn : only with ST-Link and CMSIS-DAP. If you have issues, add
Warn : "set WORKAREASIZE 0" before sourcing nrf51.cfg to disable it
Error: flash write algorithm aborted by target
Error: timed out while waiting for target halted
target halted due to debug-request, current mode: Handler HardFault
xPSR: 0x41000003 pc: 0xfffffffe msp: 0xffffffd8
Error: error waiting for target flash write algorithm
Error: Failed to write to nrf51 flash
Error: error writing to flash at address 0x00000000 at offset 0x00000000
embedded:startup.tcl:476: Error: ** Programming Failed **
in procedure 'program'
in procedure 'program_error' called at file "embedded:startup.tcl", line 532
at file "embedded:startup.tcl", line 476
invalid command name "quit"
Info : dropped 'telnet' connection

Since both ended with error I then tried to put the head unit back together and the head unit will not turn on. No lights no beeps but the brake lights flash a one code.. on off,,,, on off,,, repeatedly. Tried to do a brake power toggle on at the same time power the unit but all I have is the steady one flash on the tail light.

Is this matching everyone's eles what do you make of the flashing process.?
ultrasnit
Posts: 6
Joined: Thu Jun 06, 2019 11:47 pm

I have problems with OpenOCD!

Postby ultrasnit Thu Jun 06, 2019 11:50 pm

I got this error: Error: Init mode failed (unable to connect to target)

All soldering is fine, and I try with 3 Dashboards..

Can anyone help me?
ca2014mp2
Posts: 15
Joined: Thu Jun 06, 2019 9:17 pm

Re: I have problems with OpenOCD!

Postby ca2014mp2 Fri Jun 07, 2019 12:35 am

I got this error: Error: Init mode failed (unable to connect to target)

All soldering is fine, and I try with 3 Dashboards..

Can anyone help me?
usb adapter is not good? If you want my eyes on it, send pict of your usb and picture of head unit where it's soldered.
ca2014mp2
Posts: 15
Joined: Thu Jun 06, 2019 9:17 pm

Re: I have problems with OpenOCD!

Postby ca2014mp2 Fri Jun 07, 2019 12:36 am

I got this error: Error: Init mode failed (unable to connect to target)

All soldering is fine, and I try with 3 Dashboards..

Can anyone help me?
are you able to see the telnet connection? any errors?

in telnet type "usage" without the " and see if you get a response
ultrasnit
Posts: 6
Joined: Thu Jun 06, 2019 11:47 pm

Re: I have problems with OpenOCD!

Postby ultrasnit Fri Jun 07, 2019 1:14 am

I got this error: Error: Init mode failed (unable to connect to target)

All soldering is fine, and I try with 3 Dashboards..

Can anyone help me?
are you able to see the telnet connection? any errors?

in telnet type "usage" without the " and see if you get a response
I got this message:

C:\Users\Badabing DMX>telnet 127.0.0.1 4444
Connecting To 127.0.0.1...Could not open connection to the host, on port 4444: Connect failed
ca2014mp2
Posts: 15
Joined: Thu Jun 06, 2019 9:17 pm

Re: I have problems with OpenOCD!

Postby ca2014mp2 Fri Jun 07, 2019 1:27 am

I got this error: Error: Init mode failed (unable to connect to target)

All soldering is fine, and I try with 3 Dashboards..

Can anyone help me?
are you able to see the telnet connection? any errors?

in telnet type "usage" without the " and see if you get a response
I got this message:

C:\Users\Badabing DMX>telnet 127.0.0.1 4444
Connecting To 127.0.0.1...Could not open connection to the host, on port 4444: Connect failed

alright, so you have a layer 1 issues, send picts on wiring.. do you have lights on your st-link and are you sure you loaded all the drivers to the stick.. can you computer see the stick?
ca2014mp2
Posts: 15
Joined: Thu Jun 06, 2019 9:17 pm

Re: I have problems with OpenOCD!

Postby ca2014mp2 Fri Jun 07, 2019 1:28 am



are you able to see the telnet connection? any errors?

in telnet type "usage" without the " and see if you get a response
I got this message:

C:\Users\Badabing DMX>telnet 127.0.0.1 4444
Connecting To 127.0.0.1...Could not open connection to the host, on port 4444: Connect failed

alright, so you have a layer 1 issues, send picts on wiring.. do you have lights on your st-link and are you sure you loaded all the drivers to the stick.. can you computer see the stick?
also did you get a pop up for port 4444 to be opened and did you in fact allow it to be opened?
ultrasnit
Posts: 6
Joined: Thu Jun 06, 2019 11:47 pm

Re: I have problems with OpenOCD!

Postby ultrasnit Fri Jun 07, 2019 1:42 am



are you able to see the telnet connection? any errors?

in telnet type "usage" without the " and see if you get a response
I got this message:

C:\Users\Badabing DMX>telnet 127.0.0.1 4444
Connecting To 127.0.0.1...Could not open connection to the host, on port 4444: Connect failed

alright, so you have a layer 1 issues, send picts on wiring.. do you have lights on your st-link and are you sure you loaded all the drivers to the stick.. can you computer see the stick?
Look here, and thanks for your help :)

https://imgur.com/a/eyxj9c6
ultrasnit
Posts: 6
Joined: Thu Jun 06, 2019 11:47 pm

Re: I have problems with OpenOCD!

Postby ultrasnit Fri Jun 07, 2019 1:48 am



are you able to see the telnet connection? any errors?

in telnet type "usage" without the " and see if you get a response
I got this message:

C:\Users\Badabing DMX>telnet 127.0.0.1 4444
Connecting To 127.0.0.1...Could not open connection to the host, on port 4444: Connect failed

alright, so you have a layer 1 issues, send picts on wiring.. do you have lights on your st-link and are you sure you loaded all the drivers to the stick.. can you computer see the stick?
There is no light in the dashboard, but the st link diode lights up. The pc can see the stick and the terminal kan see the stick to

Return to “Ninebot ES and E-series”

Who is online

Users browsing this forum: No registered users and 2 guests