TonyMac32

Moderators
  • Content Count

    2308
  • Joined

  • Last visited

5 Followers

About TonyMac32

  • Rank
    Embedded member

Profile Information

  • Gender
    Male
  • Location
    Michigan

Contact Methods

  • Website URL
    http://www.electricgraveyard.com

Recent Profile Visitors

10876 profile views
  1. For some info: http://opensource.rock-chips.com/wiki_Main_Page The boot process explained: http://opensource.rock-chips.com/wiki_Boot_option Sent from my Pixel using Tapatalk
  2. Which image are you using? Sent from my Pixel using Tapatalk
  3. Good luck with the deployment! Sent from my Pixel using Tapatalk
  4. Rockchip recommends it for Linux as well. It isn't relevant to the processor thank goodness, and we certainly don't use it. Sent from my Pixel using Tapatalk
  5. You could try the tinkerboard image and swap the EVB device tree. Model: Evb-RK3288 DRAM: 2 GiB Relocation Offset is: 7de4d000 Using default environment Sent from my Pixel using Tapatalk
  6. Can confirm display port working in USB-C, don't try hotplugging too many times it will give up eventually until reboot. really cool though
  7. I've been (trying) to move the Tinker and MiQi u-boots to 2020.07, however if I use any of the following: A MiQi, A Tinker S an image for a Tinker S an image for a Tinker on a Tinker S I get stuck in the initramfs busybox with it telling me the filesystem is toast. The only 2020.07 combo I've gotten to boot is the Tinker with the non-eMMC supporting u-boot. As for clues, I haven't found any, the u-boot source code is of course very well organized for debugging purposes :lol:. If anyone has an idea about what could be going on with this let
  8. I have no problem with SPI flash when it doesnt require me to take extra steps to get basic functionality. I'm just not sure why you can't just load the u-boot preloader directly into flash and forget about tapdancing around all the chromebook knock off u-boot stuff. If yanking it works though (it should, really), that's probably what I'll do, I have the tools to do it and keep the SPI in case I need it.
  9. As was stated only a couple posts above this one, the display was never working with mainline kernels. As the driver has been upstream for a while and gotten some attention I may try it again, however the RPi designed hardware is of course not fully compliant with any standard display module, and could cause some difficulties. Sent from my Pixel using Tapatalk
  10. Mine is an "EPIK" branded model, Veyron Jerry. I got it for almost nothing. I'd be willing to take a look at if there's a way to wipe the entire coreboot mess off the SPI and start over.
  11. I can. Sent from my Pixel using Tapatalk
  12. I have one actually (veyron), but it seemed like a pain in the ... to flash it so it got forgotten.
  13. The GPIO pins are very low current, 3-5 mA if I remember correctly. I don't think you'll damage the SoC, but it certainly won't drive a fan if my memory is correct. Sent from my Pixel using Tapatalk
  14. @ning Yeah, I was keeping up with the mailing list, reverted it here: https://github.com/armbian/build/commit/9372fcdedfb6af9709ba1a046e983523997aeada Now it all works, we had a Vim1 issue because it wasn't using the modified card name so PA wasn't immediately enabling it (I chose to use "gx-sound-card") I have not touched vim2 and up, I don't have test boards.