BIGTREETECH-SKR-V1.3
BIGTREETECH-SKR-V1.3 copied to clipboard
bigtreetech
skr 1.4 turbo bootloader
Hi! I have a skr 1.3 Board using the Flash Magic program and installing the boot jumper, I was able to flash the bootloader into the Board. There is also a scr 1.4 turbo Board , but there is no boot jumper on it and flash magic cannot load the Bootloader on it. How do I switch it to boot mode and how do I connect the rx tx on the Board, do I have a diagram, do I have any ideas?
See the 2 blue points above the CPU BTT SKR V1.4PIN.pdf that's the pins. Here is the file i uploaded ripped from a Skr 1.4 turbo https://github.com/Marsman1970/SKR-V1.3-Bootloader. The file seems a bit different from a Skr 1.3 but i.m gonna try it on a 1.3 & see what happens
See the 2 blue points above the CPU BTT SKR V1.4PIN.pdf that's the pins. Here is the file i uploaded ripped from a Skr 1.4 turbo https://github.com/Marsman1970/SKR-V1.3-Bootloader. The file seems a bit different from a Skr 1.3 but i.m gonna try it on a 1.3 & see what happens
Marsman1970, Thank! I used to connect the circuit from skr 1.3 instead of skr 1.4. I will, I hope did not hurt anything
I have the same problem with my skr 1.4 turbo. How do I connect it to load the bootloader? I am so frustrated
Сouldn't load the loader on the 1.4 Turbo Board.Power is available but there is no connection. I checked everything and connected it to the TFT screen. The power is on, the led lights up, but it doesn't load the bootloader. Who knows what the error might be?
@Marsman1970 So, is that actually a bootloader useful on the 1.4 or is that only for the 1.3?
https://github.com/Marsman1970/SKR-V1.3-Bootloader The lpc1769 is from a skr 1.4 turbo not sure if it will work on a standard 1.4 i think it should. The lpc1768 1.3 is from a skr 1.3 Michael
@Marsman1970 Turbo was what I was looking for thanks. Now just to figure out how to hook up this FTDI ..
@Anion-anion , @Marsman1970, I have a bricked skr 1.4. Please someone can help me. I have the btt writer and also a stlinkv2. Thanks
I have a modified bootloader for the SKR 1.3, 1.4 and a.4Turbo, currently tested on 1.4, will test it on 1.4T and 1.3 over the weekend. This one supports update from the internal SD card, from the SD card on the display board (RepRap, BTT TFT35 and may be others that are connected to SPI 0 as well) and from USB (when pressing the display button)
https://github.com/ardiehl/BTT_SKR_13_14_14T_SD-DFU-Bootloader
I used a stlink-v2 for the upload
If you are blind as myself: There is a compiled bin file: https://github.com/ardiehl/BTT_SKR_13_14_14T_SD-DFU-Bootloader/tree/main/bootloader_bin/DFU-Bootloader.bin And it works, thanks a lot @ardiehl!
If you are blind as myself: There is a compiled bin file: https://github.com/ardiehl/BTT_SKR_13_14_14T_SD-DFU-Bootloader/tree/main/bootloader_bin/DFU-Bootloader.bin And it works, thanks a lot @ardiehl!
Hi, please do you have a link to the stlink-V2 software you used to load the bootloader? I burned the processor and I need to replace it. Thank you.
Just for future reference: Flashed a SKR 1.4 Turbo with @ardiehl Bootloader, using a USB to TTL adapter:
Things needed:
- USB to TTL adapter, e.g. https://www.amazon.com/dp/B075N82CDL
- Some Jumper wires, e.g https://www.amazon.com/dp/B01EV70C78
- female to female for the USB to TTL
- female to male to conveniently contact the pin P2.10 to get the board into ISP mode
- @ardiehl bootloader hex (attached to this post, or build it your self)
- Flashmagic
Procedure:
- Power the board via USB or 12V / 24V
- Contact the USB TTL adapter as shown in the picture (cyan arrows)
- RX of the adapter to TX on the board
- TX of the adapter to RX on the board
- GND to GND
- Contact the SMD resistor (R28) to GND of the board (dark blue arrows), e.g. middle pin of an endstop (here the female to male jumper cable comes in handy). This will contact the ISP mode pin P2.10
- Reset the board while holding the contact (Nr. 3)
- Shortly after releasing the Reset button also remove the ISP connection (Nr. 3)
- Start Flashmagic
- Chose the @ardiehl hex file
- Set the correct COM port for your USB to TTL adapter (look it up in the windows device manager)
- Set the correct chip type (LPC1769 for SKR 1.4 Turbo)
- Set Erase to
Sectors used by file - Press start
- Wait until finished, then reset the board
- Flash new
firmware.bin, e.g. via SD card upload or using the new bootloader's direct flash capabilities
Flashing via STLink v2 did not work for me, neither from linux shell, nor via PlatformIO but the Flashmagic way was surprisingly painless.
Bootloader Hex (unzip to use): DFU-Bootloader.zip
Edit for SKR Board 1.3: For SKR 1.3 simply connect AUX-1 in Step 2 and use (read short) the BOOT Jumper pins to achieve the same as in Step 3 to 5.
Thank you very much As soon as a new processor arrives, I will try your guide.
Query 4. Reset the board while holding the contact (Nr. 3) Does the jumper in the picture mean blue?
- Reset the board while holding the contact (Nr. 3) Does the jumper in the picture mean blue?
Not sure that I understand the question:
- To get the chip into the ISP mode you need to pull the pin P2.10 to GND during reset
- The P2.10 is easily accessible via the bottom of the SMD resistor
- GND is easily accessible via, e.g. the middle endstop pin
So you need to make this contact between GND and P2.10 and hold it, reset the board and then quickly after releasing the reset button remove the contact.
BTW, I misplaced the arrow in the post above. Corrected now.
I have a modified bootloader for the SKR 1.3, 1.4 and a.4Turbo, currently tested on 1.4, will test it on 1.4T and 1.3 over the weekend. This one supports update from the internal SD card, from the SD card on the display board (RepRap, BTT TFT35 and may be others that are connected to SPI 0 as well) and from USB (when pressing the display button)
https://github.com/ardiehl/BTT_SKR_13_14_14T_SD-DFU-Bootloader
I used a stlink-v2 for the upload
How do you build the project? I have an SKR E3 Turbo I would like to try your bootloader on with modifications to the BTN_EN pin and the BEEPER_PIN but when I try to use MAKE on the project I get:
PS C:\Repo\BTT_SKR_13_14_14T_SD-DFU-Bootloader> make
FIND: Parameter format not correct
FIND: Parameter format not correct
FIND: Parameter format not correct
FIND: Parameter format not correct
make: *** No rule to make target 'build/system_LPC17xx.o', needed by 'build/nxp.ar'. Stop.
PS C:\Repo\BTT_SKR_13_14_14T_SD-DFU-Bootloader>
Can you help me?
How do you build the project?
Didn't try under Windows but in Linux it builds nicely. Probably you could use the Ubuntu that can be integrated into Windows 10 via the MS Store if you do not have a native Linux box.
Edit: I'm not sure that the bootloader will work for a SKR E3 Turbo (although the same chip). Be sure to have a backup of your original bootloader.
@Sineos Hey, after a couple of hours of working on this I figured out I needed to build the project on Linux. I have a laptop that runs a Linux OS. I will try using make on my Linux laptop.
I already backed up the bootloader from the SKR E3 TURBO board. I just now need to compile the change for holding the beeper pin low for the SKR E3 Turbo board.
I am confident this bootloader will work on the SKR E3 TURBO but like you said need to back up the original bootloader which I have done just incase I end up bricking the SKR E3 TURBO.
When I am done I will have a manual on how to do backup and restore the bootloader and a github repository for backed up bootloaders for the following boards (I plan to save the bootloader for each of these boards):
SKR V1.3 SKR V1.4 SKR V1.4 TURBO SKR PRO V1.1 SKR PRO V1.2 GTR V1.0 SKR mini E3 V2.0 SKR E3 TURBO BT002 V1.0
If you build on Debian / Ubuntu on a x86 architecture you will need:
apt install build-essential gcc-arm-none-eabi
You need to x-compile for arm.
@Sineos I must of had a tab in the wrong spot and in a script file those are very hard to find and can do funny things. So I started from scratch with the clone repository from @ardiehl repository. The apt install build-essential gcc-arm-none-eabi tip I do appreciate. But I am running not on BUSTER but Linux Mint 19.3. I already had done the apt install gcc-arm-none-eabi with out the build-essential and I was able to compile. I went ahead and add build-essential to my Linux Mint OS and redownloaded the clone repository. This time with every change I recompiled to see where my error was. I never found it. I did do a reboot maybe that is what fixed the issue.
anyways, I have the recompiled .bin and .hex file for SKR E3 Turbo. I need to first upload the saved backup copy of the original bootloader then I will try to load this new one and see if it will work on the SKR E3 Turbo board. I will let you know if it works or not. Thanks for the help, it is very much appreciated.
@Sineos IT WORKS!! The beeper going off continuously is solved and the bootloader still uploads the firmware with my ONBOARD SD card reader for the SKR E3 Turbo.
Thanks for all your help.
If anyone else is trying to solve the issue with the SKR E3 TURBO making noise upon boot from your display screen speaker please look to this github repository for the modified bootloader done by @ardiehl & @triffid & @GadgetAngel
This repository will also have a manual on how to do this and a copy of original bootloaders for the BTT SKR boards
https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader
I have had problems flashing via SD, so I discovered how to flash via SWD with an ST-link. I have put my comments here.
I have had problems flashing via SD, so I discovered how to flash via SWD with an ST-link. I have put my comments here.
I noticed if I push the microcard in just a bit, it would be recognized. Easy to do when updating firmware, but obliviously not for printing files (since it would then eject when I let loose). Board (Mini E3 V2) was new, so I contacted BTT. Connector must have a pin bent (despite me being very careful w/it).
I have had problems flashing via SD, so I discovered how to flash via SWD with an ST-link. I have put my comments here.
I noticed if I push the microcard in just a bit, it would be recognized. Easy to do when updating firmware, but obliviously not for printing files (since it would then eject when I let loose). Board (Mini E3 V2) was new, so I contacted BTT. Connector must have a pin bent (despite me being very careful w/it).
Also should have said, I figured out the bootloader on the board will go into DFU (flashing via USB) mode when you hold the rotary encoder button of the screen down while resetting. Then you can do dfu-util -D <firmware.bin>. That way you don't have to fidget with the SD card (for mine the SD card is inaccessible and the plan was to use an extender, not feasible if I have to hold it in).
I have had problems flashing via SD, so I discovered how to flash via SWD with an ST-link. I have put my comments here.
I noticed if I push the microcard in just a bit, it would be recognized. Easy to do when updating firmware, but obliviously not for printing files (since it would then eject when I let loose). Board (Mini E3 V2) was new, so I contacted BTT. Connector must have a pin bent (despite me being very careful w/it).
Also should have said, I figured out the bootloader on the board will go into DFU mode when you hold the rotary encoder button of the screen down while resetting. Then you can do
dfu-util -D <firmware.bin>. That way you don't have to fidget with the SD card (for mine the SD card is inaccessible and the plan was to use an extender, not feasible if I have to hold it in).
I had read the SD microcard connector had some issues, so from day one I used an extender (board is only 1 month old, if that). But I was doing some updating and inserted a SD microcard in the actual connector...very gently, I might add. But that was all she wrote. So rather than ripping out the the motherboard, I got the TFT35 display and just print from that.
I figured if I got a replacement SKR Mini E3 again, I'd just have the same issue. So now I print using the TFT thumb drive connector. Going to order an extender for that.
I do have Pi2 setting around unused, I may eventually play around with adding that, but for now, I'll just tinker getting to know the BTT/BLtouch setup.
I used Sineos' method successfully to flash a new bootloader on to my SKR 1.4 Turbo. A stumbling point for future readers is that you really do have to poke that resistor fairly hard to get a good contact, and you might have to install the VCP (Virtual COM Port) drivers for your FTDI board manually. Big thanks to @Sineos for this guide.
@Sineos Thank-you! I did exactly as your guide instructed for my SKR 1.4 Turbo and it works!
Here is a repository for all bootloaders for BIGTREETECH boards, including SKR V1.4 TURBO. This repository also has manuals to explain how to backup or restore your bootloader to the BIGTREETECH board. All the original bootloaders that were shipped with the BIGTREETECH boards are saved in this repository(https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader/tree/main/bootloader_bin/backed_up_original_bootloaders). The manuals are for Windows 10 users and Linux users. A manual explaining @Sineos method is even provided. https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader
Guys, you have done such a good job by explaining so many totally new things to me - thank you for that. In my case, it still does not work to update the firmware. Do I get it right - to have it run like described above one of the two conditions has to be fulfilled?
- the SD Card Slot on the board is not broken and is able to read the SD Card OR
- a display with the "rotary button" needs to be connected to be able to jump into the DFU Mode to be able to flash via USB. is that right? Since I don't have the display available that I can't push any buttons - is it somehow possible to "fake" the "button press" directly on the board?
Would be super happy to get a answer even if it is not possible.
Thank you.
PS. I am old but very new to that topic I purchased the board some months ago and started to work with it way too late to be able to get it back. I just want to get it run and somehow I am tired of buying all the additional things like jumpers, stepper drivers, cables, and more cables and USB convertors ( things I never had before at home) just to figure out one day that the board is just broken. :)
Guys, you have done such a good job by explaining so many totally new things to me - thank you for that. In my case, it still does not work to update the firmware. Do I get it right - to have it run like described above one of the two conditions has to be fulfilled?
- the SD Card Slot on the board is not broken and is able to read the SD Card OR
- a display with the "rotary button" needs to be connected to be able to jump into the DFU Mode to be able to flash via USB. is that right? Since I don't have the display available that I can't push any buttons - is it somehow possible to "fake" the "button press" directly on the board?
Would be super happy to get a answer even if it is not possible.
Thank you.
PS. I am old but very new to that topic I purchased the board some months ago and started to work with it way too late to be able to get it back. I just want to get it run and somehow I am tired of buying all the additional things like jumpers, stepper drivers, cables, and more cables and USB convertors ( things I never had before at home) just to figure out one day that the board is just broken. :)
Try to reload the bootloader for the SKR V1.4 Turbo board. Follow this guide: https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader/blob/main/bootloader_bin/backed_up_original_bootloaders/SKR%20V1.4%20Turbo/Guide%20UART%20Flash%20SKR%20V1.3%20or%20SKR%20V1.4%20or%20SKR%20V1.4%20TURBO%20using%20Windows%2010.pdf
The original bootloader and firmware file can be found here: https://github.com/GadgetAngel/BTT_SKR_13_14_14T_SD-DFU-Bootloader/tree/main/bootloader_bin/backed_up_original_bootloaders/SKR%20V1.4%20Turbo/Bootloader_and_Firmware
Once the bootloader and firmware original files have been loaded to the board, you will have to reconfigure Marlin to meet your printer's configuration. The firmware that is loaded from the original files is the one that is shipped with the board when you bought it.
I hope this helps.
* a display with the "rotary button" needs to be connected to be able to jump into the DFU Mode to be able to flash via USB. is that right? Since I don't have the display available that I can't push any buttons - is it somehow possible to "fake" the "button press" directly on the board?
Yes, it is :) See below, but in short, you need to connect pin 0.28 to ground and reset the board, it should enter DFU mode and then you can flash it via USB.
PS. I am old but very new to that topic I purchased the board some months ago and started to work with it way too late to be able to get it back. I just want to get it run and somehow I am tired of buying all the additional things like jumpers, stepper drivers, cables, and more cables and USB convertors ( things I never had before at home) just to figure out one day that the board is just broken. :)
My approach just requires a USB cable, and lacking the screen, something to connect the two pins the button would do.
So when starting the board, the bootloader checks if a given button is pressed (dfu button check), and if so, starts the board in DFU mode (enter dfu mode), where you can flash firmware in linux using dfu-util (no idea about Windows, sorry). This button is pin 0.28 (bootloader dfu pin), which is set to pull-up so you need to connect it to ground (dfu is pullup). Location of pin 0.28 on the SRK 1.3 board on EXP1 SKR 1.3 pinout (and 1.4 uses the same wiring for EXP1 and 2 of course).
* a display with the "rotary button" needs to be connected to be able to jump into the DFU Mode to be able to flash via USB. is that right? Since I don't have the display available that I can't push any buttons - is it somehow possible to "fake" the "button press" directly on the board?Yes, it is :) See below, but in short, you need to connect pin 0.28 to ground and reset the board, it should enter DFU mode and then you can flash it via USB.
PS. I am old but very new to that topic I purchased the board some months ago and started to work with it way too late to be able to get it back. I just want to get it run and somehow I am tired of buying all the additional things like jumpers, stepper drivers, cables, and more cables and USB convertors ( things I never had before at home) just to figure out one day that the board is just broken. :)
My approach just requires a USB cable, and lacking the screen, something to connect the two pins the button would do.
So when starting the board, the bootloader checks if a given button is pressed (dfu button check), and if so, starts the board in DFU mode (enter dfu mode), where you can flash firmware in linux using dfu-util (no idea about Windows, sorry). This button is pin 0.28 (bootloader dfu pin), which is set to pull-up so you need to connect it to ground (dfu is pullup). Location of pin 0.28 on the SRK 1.3 board on EXP1 SKR 1.3 pinout (and 1.4 uses the same wiring for EXP1 and 2 of course).
Which motherboard are you working with (SKR V1.3 or SKR v1.4 or SKR v1.4 Turbo)? What Operating System are you using (Windows 10 or LINUX)?
If you are using the SKR V1.3 board the board has a BOOT header that you use to ground the ISP_BOOT pin (P2.10). No need to use DFU_BTN since the SKR V1.3 board provides you access to the ISP_BOOT pin directly from the BOOT header.
To reload the "bootloader and firmware" file you must use "Flashmagic" software on Windows 10 machine OR use dfu-util -D <firmware.bin> command line on a LINUX machine.
The order to do things:
A. Attach your "BTT Writer" or "USB to TTL adapter" to the SKR V1.3 board":
- the TX ("BTT Writer" or "USB to TTL Adapter") ->RX (SKR - "TFT header")
- the RX ("BTT Writer" or "USB to TTL Adapter")-> TX (SKR - "TFT header")
- the GND ("BTT Writer" or "USB to TTL Adapter") -> GND (SKR - "TFT header")
- the 5V ("BTT Writer" or "USB to TTL Adapter") -> 5V (SKR - "TFT header")
B. If using Windows 10 start up the "Flashmagic" software, If using Linux skip this step
C. Now you want to place the SKR board into the proper state so you can load the "bootloader and firmware" file to do this you need to take the ISP_BOOT pin and temporality tie it to ground (GND). On the SKR V1.3 board you will use the BOOT header. On the SKR V1.4 or SKR V1.4 Turbo you will have to use the R28 resistor and touch the bottom pad of the R28 resistor to GND (use one of the endstop pins) temporarily. This momentarily jump to ground (GND) on the proper location will force the board into the correct state.
D. Now on Windows 10 using the Flashmagic Software try to access the memory, OR on Linux try using dfu-util -D <firmware.bin> command line. If it does not work, then the SKR board did not recognize the momentary jump to ground (GND) on the ISP_BOOT pin. So try again, but this time hold the ISP_BOOT pin to ground (GND) a smig longer.
Since I don't have the display available that I can't push any buttons - is it somehow possible to "fake" the "button press" directly on the board? Answer: There is no need to 'fake' the button press on the screen because you do not need the screen to get the board into the correct state. YOU NEED access to the ISP_BOOT signal pin. By temporality connecting the ISP_BOOT pin to ground (GND) you are basically "faking" the "button press". I hope this is clear.
Please access the whole page on github to see my reply: https://github.com/bigtreetech/BIGTREETECH-SKR-V1.3/issues/346#issuecomment-880015329
On Wed, Jul 14, 2021 at 12:00 PM yeahwgeni @.***> wrote:
I tried that couple of times. But also always trying to check to update the firmware via SD card which does not work AND/OR trying to update the firmware directly via VS Studio connected with USB to the board.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bigtreetech/BIGTREETECH-SKR-V1.3/issues/346#issuecomment-880015329, or unsubscribe https://github.com/notifications/unsubscribe-auth/AH7LC2KZ2NQMYC3HIGR2NM3TXWYA7ANCNFSM4N4MNDUA .
@GadgetAngel so something you could perhaps clear up for me, I thought the ISP programming was different from the DFU programming, i.e. the ISP makes the LPC1768 enter into the on-chip bootloader https://www.waveshare.com/wiki/LPC_ISP_Programming_1, and the DFU programming (the center button on screen while booting) makes the device go into a software bootloader by using the existing software bootloader https://github.com/ardiehl/BTT_SKR_13_14_14T_SD-DFU-Bootloader, and only allows you to overwrite the firmware
Edit: I've never done the ISP bootloader bit, only the DFU bootloader one. But I think the ISP programmer does https://www.nxp.com/docs/en/user-guide/UM10360.pdf chapter 32
@GadgetAngel so something you could perhaps clear up for me, I thought the ISP programming was different from the DFU programming, i.e. the ISP makes the LPC1768 enter into the on-chip bootloader https://www.waveshare.com/wiki/LPC_ISP_Programming_1, and the DFU programming (the center button on screen while booting) makes the device go into a software bootloader by using the existing software bootloader https://github.com/ardiehl/BTT_SKR_13_14_14T_SD-DFU-Bootloader, and only allows you to overwrite the firmware
Edit: I've never done the ISP bootloader bit, only the DFU bootloader one. But I think the ISP programmer does https://www.nxp.com/docs/en/user-guide/UM10360.pdf chapter 32
Please see: https://community.st.com/s/question/0D53W00000cSDz7/the-difference-between-boot-loader-and-dfu-mode