-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BTT SKR 1.4 Turbo - #149
Comments
I have the same issue.
I was wondering if this was a permission issue, but I have it wide open and I assume that OFU would complain it cannot write if that were the case. |
what method are you using for flashing it? I see that LPC1768 is available but not LPT1769 which the BTT 1.4 Turbo is based on |
Hello, |
any news on this Board?? |
Unless someone with the board can contribute code or documentation (I'm not sure what is required) there's not a lot I can do... |
i have this board how can i help?? |
Can you describe how you manually flash the board and explain what would be needed in the plugin to be able to do the same? I'm not sure I understand why this board is very different to flashing an lpc1768 board. Also, I just added support for running pre-flash gcode commands. Would running |
Manual update: just inserting the microsd on the board and then power off power on and the new firmware is loading. |
Well, unless someone with a board can figure it out and provide me the details (or someone provides me a board) there's not a lot I can do. |
Manual update process via PC involves connecting the device via USB, the SD
card on the skr 1.4turbo will then appear in the list of drives, you then
upload the firmware file and then power cycle the controller.
I'll see if I can get the exact step by step and filename/format later
today.
…On Fri, Nov 27, 2020, 12:26 PM Ben Lye ***@***.***> wrote:
Well, unless someone with a board can figure it out and provide me the
details (or someone provides me a board) there's not a lot I can do.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMP7SJE2L26CC7HW4YDBBB3SSADQFANCNFSM4RUUYL6A>
.
|
It's the power-cycle of the controller which presents the problem. It's easy enough to copy the file to the SD card, but if a software reset doesn't trigger the update we're a bit stuck. Can you find out if there's another way to trigger the firmware upgrade once the file is copied? |
I'm guessing that the vendor of this board may have done something in the bootloader so that it only updates after a power cycle. In that case you might need to look at hooking up a GPIO pin to reset the board (if there is a reset pin you can connect to). Again, without access to the board, all I can do is guess... |
I have copy manual the bin in to the sdcard then i have execute the M997 printer reboot but no new firmware. then i take the sdcard and i check on my pc the bin file was still there.Next step was again the sdcard on the board power cycling the board and the firmware was there. so it mean board must be power cycle to take effect. :-( |
Being able to upload it directly to the board without having to connect it
directly to a PC would be helpful. I'll tinker around and see if the RPI
auto mounts the sd media to a path. (i'm also wondering if it's possible to
transfer the firmware file via winscp)
…On Fri, Nov 27, 2020, 12:44 PM nikos1671 ***@***.***> wrote:
I have copy manual the bin in to the sdcard then i have execute the M997
printer reboot but no new firmware. then i take the sdcard and i check on
my pc the bin file was still there.Next step was again the sdcard on the
board power cycling the board and the firmware was there. so it mean board
must be power cycle to take effect. :-(
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMP7SJCVUABZ7LRK2SC72DDSSAFSNANCNFSM4RUUYL6A>
.
|
The only work around will be something like this https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwjgrLmd06PtAhWNuHcKHbLbASkYABAHGgJlZg&ohost=www.google.com&cid=CAESPuD2wsPVjYuhZdAKiXzH1-1UTv7CwtLbcIhOs0jvjuhvPEQ1mDCq9I-vGyQKNgVTpbFj6IGiLr5m7sWzhSzY&sig=AOD64_2I8iWULDR3tBNNkmthJ9YnXAXQLA&ctype=5&q=&ved=2ahUKEwieqq6d06PtAhVDsaQKHZ8XBa4Q9aACegQIBRBK&adurl= or just a wifi plug and openhab it would work :-) just sent a command from the plugin to close and open the plug. |
Link doesn't work for me, is it some sort of relay?
…On Fri, Nov 27, 2020, 1:15 PM nikos1671 ***@***.***> wrote:
The only work around will be something like this
https://de.aliexpress.com/item/32972603577.html?spm=a2g0o.cart.0.0.18863c00jzMckn&mp=1
<http://url> or just a wifi plug and openhab it would work :-) just sent
a command from the plugin to close and open the plug.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMP7SJC3OK44K7MEH5YCYRDSSAJG3ANCNFSM4RUUYL6A>
.
|
Try now |
I'm thinking about adding a 'custom' flash method which would let you configure any arbitrary command or script to run as the flash method. With something like that you could write a bash script which copied firmware file wherever it needed to go, and then control your relay (or smart plug), or even GPIO pins if that were an option to trigger the reset. That's about all I can think of doing in the plugin for now for this board. |
Thats sound good.. |
There's nothing special about the bootloader on these boards. Updating the SKR 1.4 Turbo (LPC1769) is no different than the SKR 1.4 (LPC1768). I've also used this plugin on the SKR E3 Turbo (LPC1769) and it works. I have found that BigTreeTech's TFTs can interfere with updating the motherboard firmware when in "Touch Mode" in case anyone is running that combination. |
That's not exactly what others are saying. The posts above say that this board does not initiate a firmware update after a simple reset via If you know differently and want to write some documentation, that would be great. |
Like I said, I've tested it on the LPC1769-based boards from BigTreeTech and it works, so I don't know why it doesn't work for others. I just tested the latest Marlin This works identically to LPC1768-based boards like the SKR 1.3 and 1.4. I'd need more details, preferably zipped copies of It'd also help to try the following:
|
So there are no changes required to the documentation at all? I can just close this and the other open issues for SKR boards? That would be nice. |
that could explain a lot then @thisiskeithb I can not even get the pi to see the sd card in tft mode. will try in marlin mode later if this slow print ever finishes. My board in under the printer out of the way and is a real pain to get to when updating firmware. I was really hoping this plugin would make my life a little easier and you may well have just cracked the nut for me . I keep forgetting tft mode is emulating a controller and is still very buggy. |
Shouldn't be, no. I'm pinging some other folks with SKR 1.4 Turbos to see if they can reproduce the issue.
I took a quick glance at the issues list and the other open SKR issue I see is for an SKR Pro (#114) which is STM32F4/a different MCU. Oh! I just remembered this "Toggle for SD mount on boot" PR MarlinFirmware/Marlin#20099 which gives you a new
|
I can easily reproduce lockups/weird behavior when trying to update the motherboard firmware when in "Touch Mode" every time I try it, so I tend to stick with "Marlin Mode". It may not be as pretty, but you can access most of Marlin's settings 🙂 |
Oh! I just remembered this "Toggle for SD mount on boot" PR MarlinFirmware/Marlin#20099 which gives you a new SD_IGNORE_AT_STARTUP option. I wondered what it was referencing as it was not in marlin from my last build at the start of november. |
You need to be running the latest |
I have just downloaded the latest bugfix an hour or so ago and noticed quite a few changes. I normally just file compaire and change without reading. I take it need to change line 1366 #define SDCARD_CONNECTION LCD to #define SDCARD_CONNECTION ONBOARD and enable 1184 #define SD_IGNORE_AT_STARTUP I have been struggling to get this working and today after upgrading the pi with sudo apt-get update then sudo apt-get upgrade & a reboot it`s now working fine. Maybe an underlying file system change was needed for me but I am positive I done the update & upgrade before I installed usbmount. maybe add the info to the instructions "sudo apt-get update then sudo apt-get upgrade & a reboot" before the sudo apt-get install usbmount ? just to make sure the pi is up to date file system side wise ? but warn users it may go tits up to cover ones backside. |
I would like to mention that I have been having this issue as well. Identical. Can't flash. The test button works to find /media/usb0, so I was able to get that part working. But, I am having an issue of not being able to "unmount the SD card". I have gone through this thread above, I've changed permissions to usb0, commented out "SD_IGNORE_AT_STARTUP", but I still can't get it working. I have a homemade printer I'm converting from a Mega/Ramps setup (printed beautifully yesterday before this). I am upgrading to the identical drivers and setup to baseline, but with the SKR1.4Turbo. So far, everything else seems to be working like the RAMPS. But, I make a LOT of firmware changes, and this add-on has been wonderful with the previous setup. I imagine it is something simple. I'm sorry, I want to add more, but it's very late and I'm tired. If anyone has any suggestions for me to try in the morning, please advise. My point of posting is to note that with this board, there is more that needs to be done to get this working, I think. I hope I'm wrong and I'm just tired. |
You don't have the same issue. You most likely need to fix your sudo rights, as explained in the documentation, and in #172. If that doesn't help:
|
This issue has been automatically marked as stale because it has not had any recent activity. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 7 days. |
I've updated the documentation and tested the described process on an SKR 1.4 Turbo board. It works exactly as described/expected when properly configured. |
This issue has been automatically locked because there was no further activity after it was closed. Please open a new issue for any related problems. |
Hardware Setup
BTT SKR 1.4 Turbo
Describe the problem
Unable to upload firmware.
Log Files
pi@raspberrypi:~ $ ls /media/usb
firmware.bin
pi@raspberrypi:~ $ ls /media/usb0
firmware.bin
pi@raspberrypi:~ $
The message Flashing successful appear, but it doesn't flash the firmware.
the /media/USB it always available, even if i detached the serial connection, it should be the onboard sd card content?
The text was updated successfully, but these errors were encountered: