• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by berin

  1. Been a while. I have not touched this project but I'll be getting back into it soon. I just got my small home cnc machine up and running. Now I'll be able to start diverting time back to this project and the big cnc machine that the company that is supposed to be making the parts for for me has still been delaying me on.
  2. Hi... all you have to do is install the DEB packages.. that I built if you want the RT.... they are already built. OR you can build them your self. if you want to build them your self just follow the guides and use my RT patches. unless there is a newer version out and you'll need to find newer patches. unless your going to run 4.19. unless you need something special there is not much point to compile it your self when the DEB packages are already built and posted. install. reboot. enjoy. This will give you everything you need to know for building for tinkerboard and other boards. download there image. update it update it and its hard coded to compile for armbian.
  3. no no.... not easy anything but easy I agree it should be released with the drivers and codecs installed. no point to have to ADD it when, and I'm going to go out on a lim here MOST PEOPLE will need some if not all of those packages.
  4. Is that your build? if so looks very interesting. I would suggest a dust skirt under the router motor and a vacuum. Though I do see that video is from 5 years ago. What aspect are you interested in this ongoing project? What are you looking forward to when a working release is made public? and do you have any plans?
  5. Getting closer to a working linuxcnc on armbian using the tinkerboard. I'll release the alpha when the bugs are worked out. I am interested in how many people are interested in this project??
  6. Helping files for building the GPIO HAL otions and gpio SPI hal_gpio.c
  7. So at this point its confirmed that the tinkerboard is as I expected a good candidate for running linux cnc. looking for anyone that can help get the GPIO HAL working AND the hal drivers for ethernet and spi mesa like boards for linuxcnc.
  8. linuxcnc_test shows an acceptable level of jitter for software stepping.
  9. I'm only just getting started with this project. So far I have gotten a lot of help from some great people and looking to get further along with this project as time goes on. My main goal is to turn the tinkerboard into a linuxcnc control system with a drop in SDcard/EMMC image(s). The images will be preloaded with everything needed to setup a cnc machine for different control systems such as GPIO, ETHERNET, SPI depending on one's choice or needs for control. The gpio will provide direct step/dir, end stops, router power control signals, etc.... the normal cnc machine control logic one would expect when using a parallel port. Ethernet and SPI will be options for anyone using drivers like the MESA controllers for example. At this point I have the working and current FULL preempt RT images and kernel DEB packages for any one looking to build or install. I have posted the files HERE. I have a working image setup with linuxcnc already compiled, and 3d/opengl video drivers fully working. If anyone is interested or willing to host the multi gig file let me know. CURRENTLY HAL for SPI, GPIO and ETHERNET are not built. These are areas I'm looking for help. Also at this point I could really use a hand with TUNING the build or tuning options for compiling the kernel if any. I'm weak in regards to software, strong in the hardware as well the electronics side. The last few issues I'm having are with the driver support for my LCD. it is not currently working at all. I have a raspberry pi 7" LCD with a native res. of 1024x600. I have to run it at 1024x768 which stretches the image a bit as well makes smaller print harder to read. The other issue though more of a personal one, I have an I2C RTC setup but i2c is not fetching the TIME/DATE but rather seeking network time. I do not know how to fix this and the few febal attempts I've made, I discovered that armbian has been rather locked down to use network time rather then seek multi sources for current time. I'm currently on the kernel 4.19 full preempt RT kernel. If anyone is interested in seeing photos of the project and the VERY custom mold and shell I built for this project check this LINK I've gotten a lot of positive feed back on it so far.
  10. OMG I cant believe I didnt post this.
  11. Linuxcnc is working fine, the only tasks left, are getting the I/O setup in linuxcnc. I do not have a mesa board and I'm prefer to use the GPIO mainly. would love any help from anyone that can. The only other issue that needs to be worked out is the Native resolution of the lcd I'm using is not working in armbian, 1024x600. My finish goal is to PUBLISH a working SD/EMMC image to the world. so people with a tinkerboard have a DROP IN cnc controller just add the boot/distro image and setup your connections for your machine as needed.
  12. I power my tinkerboard using a castle power supply and a 12v power brick. This post of mine describes My setup and design. VERY stable I have yet to brown out my tinkerboard. This link shows photos of my build
  13. So I now have working RTOS builds for 4.4 and 4.19, I'm now working on getting linuxcnc setup and working SPI, ETHERNET, and GPIO control functions.
  14. ? not full preempt RT. only preempt is setup in the current offered download images for tinkerboard .
  15. I finally got the RTOS built and working. Armbian 4.19.34 NEXT FULL PREEMPT RT kernel patch rockhip build 5.78 armhf Finally got them to compile current RT for 4.19 let me now if it works or knot? linux-dtb-next-rockchip_5.78_armhf.deb linux-headers-next-rockchip_5.78_armhf.deb linux-image-next-rockchip_5.78_armhf.deb Let me know if anything has issues, I had to re-upload linuxsource-next because it was corrupted. patch-4.19.34-rt18.patch.gz Patch for compiling armbian Next real time, drop into userpatches kernal rockchip-next linux-source-next-rockchip_5.78_all.deb
  16. and that is what ever the latest version is that was released what a day ago?
  17. I guess I'm comparing bionic 4.19 download image to the 4.4 bionic, aside from 1024x600 not being part of the system at all, it does not try to set everything to 75hz by default is what I'm getting at. "crappy HDMI controller" I'm not going to argue that and reporting the lenovo 19" at least I'm not alone . scripting errors: i'm refering to changing to display modes automaticlly with out user input and no i have not altered anything. Thats dump image to SD card and boot. "native first" ok makes sense "Uboot boot resolution" boots fine with my normal full sized external monitors (they are all HD capable). but with the 7" PI LCD it uboots at 1920x1080 unkown HZ and does the flickering thing more like a blink on for a split second then off for 2-6 seconds then on for a second off half a second back again. very random. Same with my other HDMI tiny lcd's it boots at 1920x1080. And does the flicker thing.
  18. "no I have not... will do and test." I have now tested the latest 4.4 bionic First opinion, very annoying scripting errors in the display settings. Its trying to default to 75hz regardless of what monitor is plugged in, I tried 3 monitors and 2 TVs. 60hz should always be the default refresh rate period, let the user define there refresh rate there after. Most lcd's and tvs do not support 75hz. RPI lcd, 1024x600 is not listed as an option unless I plug the RPI lcd in, then its automatically listed and tries to use that res, but does not work. It just flickers widly and was very hard to see anything to get the res changed. I would strongly suggest NOT having the scripts change resolutions automatically with out the users input. I used an external monitor and set it to a low resolution. But when I plugged my RPI lcd in it tried to default to 1024x600 that does not work, the screen flickers wildy and is hard to change to something else. 1024x768 works for the time being. I dont understand why 1024x600 is listed at the top of the list above 1920x1080. An other thing that is interesting is that DISPLAY list's my RPI 7" 1024x600 as a Lenovo 19" display? The way the display flickers I'm going to assume its a timing issue. The picture shows for anything from .1 seconds to .5 seconds, typically you can see the display just fine for that time frame. then its blank. Some times the display is streached in odd ways. But the display spends more time BLACK then showing anything at all. An other thing I would strongly suggest is dropping the uboot resolution or at least have the easy option to change from the default 1920x1080 to 1024x768 60hz or other in general. That resolution is so high the display flickers on/off during boot and CLI actions are often impossible to see. Its usless to try and see anything using smaller displays like mine or smaller still like the 5" and the 2.5" etc. lcd's.
  19. I need to get 1024x600 on HDMI working to use my RPI lcd at the correct resolution. It is not supported on ether 4.4 or the latest 4.19 The booklet that comes with it list's the following hdmi_group=2 hdmi_mode=1 hdmi_mode=87 hdmi_cvt 1024 600 60 6 0 0 0 max_usb_current=1 chip rtd2660h The website keeps going up and down. <-- may not work try link below if needed.
  20. aqua everything that is 5v is directly connected to each other. its the 5v rail on the tinkerboard motherboard. Infact you could power the thinkerboard using the usb ports alone.. (not talking about the micro offical usb power supply port). USB is designed to be tolerant of up to a max of 5.6v DC. anything over that may cause damage. FYI most usb devices are 3.3v and have a 5v to 3v step down power supply, ether a liner or DC-DC system. supplying the tinkerboard with 5.3v means you get more power with less current, This means less heat and less strain on the tinker board power supply system (low voltage for the cpu supply). The main reason the tinkerboard has a reboot cycle issue is 100% due to not having a good power bus system setup on the board. and bumping the voltage a little will solve it period.
  21. I have done a number of test's on the tinker board. I have found that they are the most stable when powered via 2 inputs, using the MICRO usb and the GPIO. AND using 5.3v DC... 5.2v works but 5.3v has shown to be much more stable. and the voltage drop out is eliminated. Also the tinkerboard should not be run with out a heat sink period. I talk about my power system setup here photos of my setup here
  22. I could be worng, but this is going by memory. As I recall you can manually set I2C clock rates, BUT I believe i2c clock rate is also automatic when the i2c bus handshakes devices on its bus. And finds the speed everything works with. i.e. every device but one is capable of the Mbit data on the same bus and the slow one is 400kbit. Then the hand shake defines 400kbit. Again I could be worng.
  23. I have the same issue with 1024x600.... very common RPI lcd but there is no built in support for my HDMI disploay
  24. (FREE OFFER) In fact for a little motivation I'd be willing to build and give for free to one (1) person the first person who full fills what I'm seeking, anyone who can solve my software issues. (ship in usa only) one of my handmade hand designed fiberglass shells for SBC's, designed around the RPI hardware model. My Asus Tinkerboard worktation shell I think it could support up-to a 10" LCD depending on lcd bezel/frame design. Hind sight I kind of wishing I had gone with a little larger LCD. I'm looking for an SDcard image to be published for all to use and access of armbian with RTOS "Preemption Model (Fully Preemptible Kernel (RT))" based on the most current release of Armbian for Tinker Board, with support for the RPI 1024x600 touch lcd VGA/HDMI. The display res is not supported (TOUCH screen however works just fine in the current tinker board armbian release bionic that I'm running now), i2c real time clock ds1307/ds1338c detection and support. There are a few other items as well. See My Asus Tinkerboard workstation shell link for photos.