Show all posts by user
@DrDitto I think that what you want to do could be made to work, but it is not something I have ever done. I'm not sure what firmware you will need for the WiFi board but it is definitely not the Duet WiFi Server Software as that is intended to be connected via SPI and can not be used at the same time as a dumb ST7920 type display. So I can't really help you much with what you are trying to do.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@PCR What version does the WiFi Socket server you are using report? You can find this by running M122 when WiFi is active.
To update the WiFi firmware via DWC you would need to have a UART connection to your WiFi board as well as SPI (and RRF that is setup to use it). Although this is possible I've never bothered (as the WiFi software is not updated very often).
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@DrDitto I think you need to take a step back and describe exactly what it is you are trying to do and how you think it will work. There are lots of possible options for using RRF with different displays (or none at all) and network connections. You should probably provide links to the actual hardware you are trying to use (the display, the esp12s module etc.).
I am not sure what you mean by "B
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Are you using the LPC specific DuteWifiServer.bin (the one linked from the Wiki)? I'm also not at all sure if the mkstft35 boot loader will be uploading the ESP8266 software correctly, what makes you think that it will? As Jay said you can't just connect that module to the aux port you need to connect it via SPI.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
Using and ESP12S as a serial device connected to RRF is probably possible (it just looks like another terminal/UART session to RRF), but I'm not aware of anyone doing it. The downsides are that you don't get any of the RRF DWC interface and any sort of file upload will be limited by the speed of the UART connection (so will be slowish). You can probably use it at the same time as a ST9720 display
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@DrDitto try the following as board.txt file, delete the existing content and copy and paste the following, reboot the firmware...
lpc.board = biquskr_1.3;
//LED blinks to indicate Platform is spinning or other diagnostic
//Comment out or set to NoPin if not wanted.
leds.diagnostic = NoPin;
//Only supports 1 External SDCard
sdCard.external.csPin = 0.16;
sdCard.external.cardDetectPin = 1.31;
s
by
gloomyandy
-
Firmware - experimental, borrowed, and future
As a follow on to the this it looks to me as if the sample board.txt files are out of date and need to be updated to match the new settings. I will get around to that when I can. Also at the moment we do not have a good way of detecting errors in the board.txt file. I'm not really sure what the best way to handle that is, this file gets read very early and so we have limited options in terms of h
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@DrDitton, I think that looks OK. A couple of things to try...
1. Post a link to the actual display you are using (or a picture), someone may know if there is a problem with it.
2. Try a slower SPI speed in the M918 command (F parameter) to see if that makes any difference.
3. Try M117 "Hello World" from the USB connection to see if that gets displayed on the screen.
4. Might be worth checking th
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@BT99 That's an interesting project! Have you tried the servo code on an LPC based board? It is not something I've ever used so no idea how well it works.
I've been looking at the TMC2209 support, merging the code from the add on driver repo is going to be fairly complex as there are a lot of differences (most of them are pretty minor, but it makes it harder to identify what actually needs to ch
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@pcr could you provide a little more information about the board you are designing? I've built a couple of adaptor boards (one for WiFi one for SBC) that just use prototype boards (and are not pretty!). Both of these simply plug into the connectors on the SKR boards for the display. In the case of the SBC adaptor I just have a set of header pins that I plug a normal female to female IDC cable int
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@BT99 Stall detection is not currently supported in the LPC port. Unfortunately it is not just a simple case of enabling the capability. I've taken a quick look at what will be needed...
There are a number of problems that would need to be solved to get it working fully. The code from DC42 is useful, but there are a number of issues that are unique to the LPC port, mainly to do with timing. For
by
gloomyandy
-
Firmware - experimental, borrowed, and future
I've never used the TFT35 stuff, but the obvious things to check are do you have the TX/RX connections the right way around and is the baud rate set correctly (the default baud rate for the serial port when using RRF is 57600).
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@PCR see previous comments in this thread, the PanelDue already works with the SKR. Yes you connect it to the TFT pins.
I hadn't realised that issues was disabled by default. I will enable it (on the main repo only for now), but I would prefer that things are discussed here first, it just makes it easier to have things in one place.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@PCR those boards are really designed for use as a serial line replacement so they only really bring out the RX/TX pins. For the full RRF solution you need access to the SPI pins (which also runs at a much higher speed then the serial interface). So although you could potentially use them as a sort of wireless serial, you wouldn't be able to run the RRF web interface etc.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@PCR If you allow the LPC to boot and talk to the 8266 (so it is no longer in a reset state), then you can flash the 8266 via USB. You can't use this to flash the device initially, but you can do it to update the firmware. When I was testing my updated version of the 8266 firmware, I flashed it many times this way.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
RC12 is now available:
In addition to the usual updates to track RRF this release also includes the capability to update the LPC firmware using DWC when uaing RRF in SBC mode.
Tagged repos here:
by
gloomyandy
-
Firmware - experimental, borrowed, and future
I use dual Z on my printer. I'm not sure that the "standard" RRF config tool has support for it (I seem to remember not finding it when I looked for it). So if anyone has plans to fix it, you might want to get it fixed in the main tool first.
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@cd_edwards I've just tested my PanelDue with an SKR V1.4 board (with the WiFi build) and it seemed to work fine with that, can't be sure about the SBase, but I would have thought it should be OK. Note however that you will probably need to add an extra line to your config.g file for RC11 see:
I'm also not sure if there is firmware update for the PanelDue or not (I've only tested the basics just
by
gloomyandy
-
Firmware - experimental, borrowed, and future
I'm sure it is possible, but the question is... is anyone willing to do the work and what is the gain in doing that work.
I doubt if using an ESP32 with an LPC based board will be any faster as the limiting factor is the SPI transfer speed between the LPC and ESP8266 and the lack of available memory (for buffer space) on the LPC. In terms of stability I've never seen any ESP8266 related issues,
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@rudenick I think jay has covered pretty much everything. As far as I can see all of those warnings/errors are either normal (heater overpowered) or related to config.g settings. As jay mentioned there is not sufficient RAM available on the LPC boards to allow networking (ethernet, WiFi or SBC) and the display support at the same time (at least that was the case the last time I checked and I doub
by
gloomyandy
-
Firmware - experimental, borrowed, and future
@rudenick So what problems do you have?
I don't think you should need anything other than the following in your board.txt file:
lpc.board = biquskr_1.4
8266wifi.lpcTfrReadyPin = 1.30
8266wifi.espResetPin = 1.31
sbc.lpcTfrReadyPin = 0.28
adc.prefilter.enable =true
Have you created a config.g file (and placed it in the sys directory on the rPi)? Please post the contents of that file.
EDIT: A
by
gloomyandy
-
Firmware - experimental, borrowed, and future