@gloomyandy Did you by any chance happen to give this a go for the software UART: I think that is a nice solution utilising the GPDMA on the LPC17xx.by sdavi - Firmware - experimental, borrowed, and future
Quotesinned sure, that works! but the thing is you need some sort of device to parse it and direct it to a display. Since I longer use the raspi with RRF, what is missing is the computer to process the M408 data and a means to display it. I am curious how you are parsing the M408 data and how far back a data stream you archive There are heaps of JSON parsers out there for most languages thby sdavi - Firmware - experimental, borrowed, and future
Quotesinned dc42: are you saying that the LPC subsystem is already spitting out the datastream ? what I was refering to was an LCD connected to the raspi. the data stream parsed by Octoprint and processed through the raspi/GPIO pins to a 4 line 20x4 HD44780 display. there was another one that did it with I2C - see in my pic that the 12864 is connected to the RAMPs? the 20x4 is connecby sdavi - Firmware - experimental, borrowed, and future
Yeah oops, I forgot to commit that fix yesterday, it needed the noexcepts in the cpp file otherwise it doesn't compile I just pushed it to GitHub just now.by sdavi - Firmware - experimental, borrowed, and future
Quotegloomyandy @sdavi Thanks for the update. So I guess it makes sense to switch testing etc. over to the 3.01 branch? If so I'll try and rebase my branch to that as soon as I can. I'm about to start testing heaters etc. so I don't think it makes sense to continue with the older branch. In terms of memory I'm curious about the free memory figures. Do dynamic allocations use both LPC main memoryby sdavi - Firmware - experimental, borrowed, and future
Quotegloomyandy Ah yes but I was thinking that for some boards (like some of the SKR boards) that do not use the hardware SPI to drive the LCD it might be possible to still operate the display (but no external SD card reader) at the same time as using the WiFi, but memory may be the bigger problem. I'd actually rather like to be able to have a minimal LCD menu system (just the main status screenby sdavi - Firmware - experimental, borrowed, and future
@gloomyandy great work getting the TMC22xx UART implemented.by sdavi - Firmware - experimental, borrowed, and future
Yep, the 3.01 branch is where the dev work is going on at the moment. David has kindly merged in some of LPC RRF code into RRF, this makes keeping the LPC port easier manage as it hopefully means less conflicts when merging in the changes from the official RRF repository. As such, the LPC 3.01 branch is now based on a fresh checkout of RRF 3.01 and the LPC directory and other LPC specific fileby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s Sdavi Is it possible to increase the scope of whats written to the config-override file? I'm thinking more for users who don't have network access and are instead using pronterface to control their machine. It would allow a user to modify any settings and get them stored, rather than making adjustments and having to note them down to update the config.g file when removing the sd card.by sdavi - Firmware - experimental, borrowed, and future
Quotegloomyandy Given that it does not seem currently possible to operate both the display and WiFi (due to memory I think), this is probably not a big deal. The WIFI is also running as a SPI Master.by sdavi - Firmware - experimental, borrowed, and future
Quotesinned sdavi - thanks for explaining it so well. I have forgotten so much of this since college. 1. so by moving the tcp/ip stack off the LPC,does it gain us any more memory to the system as well? is this desirable to do anyhow? 2. what pins does the esp/wifi unit need to work? will it free up more pins on the LPC boards then? 3. can you compare performance overall between Eth0 and Wby sdavi - Firmware - experimental, borrowed, and future
Quotesinned question about the ESP-Wifi integration: Is the ESP unit working as a bridge to communicate to the network or is it working as an integrated piece of hardware with the LPC processor? What if any code runs on the ESP unit? Perhaps I misunderstand, do we need both Ethernet AND Wifi modules compiled in to the FW? The built-in ethernet uses the onboard EMAC which receives frames fby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s Do you have a full list of custom gcode commands which have been added? The only custom gcode in the LPC port is the extra diagnostic (P200) on M122.by sdavi - Firmware - experimental, borrowed, and future
Quotejay_s That's great thank you. I'll test my addition of the SKR 1.4 tonight. If it work and I push it to github, will you sort out updating the LPCConfigurator? or is that a separate repo I can commit to? I only did the LPC configurator so it would be easier to give the betas a try at the time - there was no interest there so I abandoned it. Some configuration options in RRF3 I think have cby sdavi - Firmware - experimental, borrowed, and future
I've just uploaded those changes to github, it now sets the lpc.board string to "generic" if it fails to find the board name in the array. I've also added that lpc board name string to M122 as you suggested as well.by sdavi - Firmware - experimental, borrowed, and future
Quotejay_s I've built the latest version of RRF3. I am working on adding an entry for the SKR 1.4 in the boards section. I have added the pins as appropriate. I am defining the board using lpc.board = biquskr_1.4 in the boards.txt file. How do I know that this has been recognised by the firmware? There doesn't seem to be an entry in M122 to reflect the selected board (as it would show which duby sdavi - Firmware - experimental, borrowed, and future
On the LPC, with WIFI compiled in there is 1 file write buffer of 1k and in the standard LPC build is only 1 file write buffer of 0.5k. You can test with this in storage/FileWriteBuffer.h (if you have enough memory). As comparison to the Duets which has 2 write buffers of 8k. The LPC manual says that when running SSP in slave mode, the master must not exceed 1/12 of the SSP peripheral clock. Whby sdavi - Firmware - experimental, borrowed, and future
Quotegloomyandy Hi, quick update. I've been able to build both the main firmware (using vscode and the command line) and he esp8266 firmware (using eclipse - which reminded how much I dislike eclipse!). As recommended above I used an older version of the esp development kit 2.4. After a little bit of a struggle I managed to flash the firmware to the esp8266 module I've got (I had to get a more upby sdavi - Firmware - experimental, borrowed, and future
Quotegloomyandy Thanks for the update. I've been looking at the schematics and it looks reasonably simple to hook things up (famous last words). A few more idiotic questions if you don't mind... 1. What IDE are you using? I managed to get RRF3 built on Linux (see below for a little feedback), using vscode and the command line. Looks like you are using the Arduino IDE for the ESP-12F is that correby sdavi - Firmware - experimental, borrowed, and future
Quotegloomyandy @sdavi, @jay_s I am also very interested in getting the WiFi/esp8266 boards working with SKR hardware (I have and SKR V1.1, SKR V1.3 and have an SKR V1.4 on order). I've worked on the LPC176x port of Marlin (added flash eeprom emulation, improved the USBMSD/USBCDC support and implemented software serial, for TMC devices). So far I've managed to build the V3 version of the firmwby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s @sdavi I have received the SKR v1.4 Turbo and I have 2.05 up and running. This board has a port for an ESP and also has hardware SPI pins available for use. Pinout attached I have created a config file for it and I have submitted it via github. Are you willing to share the information about the wifi board you have been working on for the ReArm so I can look at getting it working onby sdavi - Firmware - experimental, borrowed, and future
QuoteOhmarinus Okay, so I started looking into the RRF files and I cannot get my head around it. First of all: - introduction/commissioning-duet/ This site is dead, so I have no clue about starting to use this. Second of all I see all kinds of software coming around I've never heard of like bossac? Is there maybe some guide you would recommend for someone using a Macbook pro that wants to instaby sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA It is interesting to read the whole thread as one can see the problems that can pop up and how to solve them. On the other hand, it starts to contain too many weakly related issues/subtopics. May be time to start a new one with the above request as first post ? Yeah there is also a lot of outdated info at the start of the thread too so maybe it's time for a new thread. GitHub repos cby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s @sdavi Any chance you can update the first post with the latest builds and boards supported? It would make it easier for new users to get up to speed with the project etc. The forum doesn't allow me to edit old posts.by sdavi - Firmware - experimental, borrowed, and future
@sinned: The LPC binary only supports 5 steppers, so you will need to download the source code and make a few changes and compile a new binary. LPC/Pins_LPC.h - Update NumDirectDrivers to the number you need (this var is also used to set the array sizes for the step/dir/en pins so it can fit the number of pins defined in board.txt). If the new STEP pins are not on port2, then the firmware will nby sdavi - Firmware - experimental, borrowed, and future
Quotesinned Its either 0 or 1000 That's still a digital signal (only on or off), if it were analog you'd be getting values in-between as well . Its just the way its represented - probes have a value between 0 and 1000 for both analog or digital types.by sdavi - Firmware - experimental, borrowed, and future
1.29 is not ADC capable, if you need analog then you need to find a spare ADC pin and use that pin for zProbe.pin. Pins configured as ADC inputs are not 5V tolerant. Generally I'd expect most people on the LPC port to use digital type probes with either P5, P8 or P9 and set zProbe.pin to the endstop pin they want to use as the probe (and remove that pin from the endstop array and replace with Nby sdavi - Firmware - experimental, borrowed, and future
Quotejay_s I'd definitely be interested in ordering an SKR 1.4 Turbo (LPC1769 variant) if its supported. Maybe @sdavi could chip in on this? The LPC port currently works on both LPC1768 and LPC1769. As for the SKR1.4, I don't know much about it.by sdavi - Firmware - experimental, borrowed, and future
QuoteMKSA Just wondering how many are we, using this firmware ? It is so quiet here. I am a bit bored, no problem. I'm not sure how many are using the LPC port, but I can get the download stats from github since I've started using the github releases: v2.04 - 21 v2.05RC2 - 5 v2.05 - 7by sdavi - Firmware - experimental, borrowed, and future
Updated binary to RRF v2.05. Download here:by sdavi - Firmware - experimental, borrowed, and future