mboehmer

Members
  • Content Count

    35
  • Joined

  • Last visited

About mboehmer

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. mboehmer

    Rock PI 4

    Sorry, no link, it was direct contact with the German distributor by phone (and some luck, talking about my specfifc requirements).
  2. mboehmer

    Rock PI 4

    RockPi4 sales start officially today. I got two preproduction run boards, one was clearly not yet optimized in soldering Accoridng to revision printing on silk screen it's the final version being sold. One issue only so far: the M.2 adaptor is from a different board, but works electrically.
  3. mboehmer

    Rock PI 4

    So, to get back to facts, build is running, may take a while. Just compared the RockPI4 with the NanoPC-T4. Seems a good choice for starting, bioth RK808D and RT8211E are the same. Audio circuit is different, the RockPI uses an ES8316 instead of ALC5651. Wifi/BT is at least similar, on the RockPI there is an AP6256, compared to the AP6356 on the T4. IR is missing. Update: NanoPC T4 image compilation succeeded, but fails booting. It starts the BL31, but hangs after two NOTICE lines. BL31 version of original image is different to the one used in NanoPC T4 image. I can post both boot logs, if anyone is interested (good ol' FT232AM works with 1.5MBaud, while Prolific fails )
  4. mboehmer

    Rock PI 4

    Zinq = Xilinx = NoGo. I started with Xilinx FPGAs, but use only Lattice ones nowadays. There are company policies which I don't support at all. Maybe a Mico32?
  5. mboehmer

    Rock PI 4

    Hi Igor, I'm a VHDL programmer mostly, with C on microcontrollers. Bash is out of my reach - too complicated... Honestly, if I can contribute by different means, I will do (and will read that page again, as suggested). Are you sure that there is really no FPGA to be programmed? So far, Michael
  6. mboehmer

    Rock PI 4

    Sir, yes Sir I have a working Armbian developer system, that's not a big deal (even for a noob like me )
  7. mboehmer

    Rock PI 4

    Hi Igor, yes... I know. I have patches prepared for Uboot 2018/Odroid C2, Tony takes already a look on. I'm not a kernel programmer, but willing to test - needing a starting point, i.e. someone to include the RockPi4 into the Armbian development tool. So, instead of pointing me to the general "contribute" page, what would be the best "first step" for me? Michael
  8. mboehmer

    Rock PI 4

    Hi all, a new RK3399 board appeared, it is called RockPi4 I have two of these beasts here already, and they works nicely - I like the small details about it (nice eMMC fixture, all heat plates on the bottom side for simple cooling, and an M.2 PICe slot for my second network card Do you see any chance to get Armbian working on that beast, and if so, what can *I* do (with my limited experience in kernel programming)? Debian is working on it already, in case you need more specific information please let me know. Any help is appreciated. So far, Michael
  9. mboehmer

    Thanks for the fish!

    Hi guys, finally, paper is finished, and for anyone interested it can be found here on the arXiv site Be warned, it concentrates on the physics, not the electronics Michael
  10. mboehmer

    Odroid C2 Uboot saveenv

    Just removed the lines in config, and just left my UART baudrate changes in, which didn't change anything regarding this error message. Seems that Uboot tries to load/save from uSD card. Guess I wait a day or so - I tried to understand the defines, but they seem quite complicated.
  11. mboehmer

    Odroid C2 Uboot saveenv

    Hi guys, I just recompiled my patches from old 2015 Uboot to the 2018 version, allowing setting the baud rate in Uboot (for accessing it by 9600 8N1), and saving envs in eMMC. First one works, I can switch easily baudrates now, but "saveenv" fails, spitting out a lot of error messages: => saveenv Saving Environment to EXT4... Card did not respond to voltage select! ** Bad device mmc 0 ** Failed (1) I also see that apparently the settings are being loaded from a wrong partition: U-Boot 2018.07-armbian (Oct 28 2018 - 10:43:58 +0100) odroid-c2 DRAM: 2 GiB MMC: mmc@72000: 0, mmc@74000: 1 Loading Environment from EXT4... Card did not respond to voltage select! ** Bad device mmc 0 ** Failed (-5) In: serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: eth0: ethernet@c9410000 Hit any key to stop autoboot: 0 Any ideas on that? Maybe eMMC disk layout changed? Any help is appreciated (if you need patches, I can post them here). Michael
  12. mboehmer

    Thanks for the fish!

    It is a research program, one of our professors from TU Muenchen cooperates with the Canadians (who operate the sub sea infrastructure). The goal of this setup was to measure water quality in North Pacific (more specific, this special site) by deploying some light emitters and light detectors on two strings. We want to learn about bioluminescence and radioactivity induced light, which both are kind of noise for the measurements intended later. Let's say it like this: it's dark there, really, you have a perfect stable temperature, and it's easier to get things there (and back again) than going for deep holes in ice. Moreover, we had to learn all necessary things about sub sea technics in a short period of time, including deployment technis (thanks to one guy supporting us, we made the job). The setup is still operational (which I call success), and with some luck we will extend it with a third string next year, including some Odroid C2 based setups and (as we go for real fibre that time instead of good ol' copper lines) some more sophisticated electronics. As soon as our paper is published, I can give more details (while I "just" did the electronics, there will be some more physics included )
  13. mboehmer

    Thanks for the fish!

    Issue solved, btw. A wrong capacitor was mounted on our power supply assembly (SMD, unmarked). We got a small dip on +5V rail, disconnecting the USB ethernet adaptor. It was reenumerated, but in brown out, so the USB interface showed up again, but the network part was dead. Changing the capacitor, and adding some smart power regulation for another switched load fixed the issue.
  14. mboehmer

    Thanks for the fish!

    Hi guys, after some rest we will soon start a new development (yet another deep sea installation). Just wanted to warn you, I will come up with some silly questions again for sure Especially about the changes made last time on kernel, like device tree, eMMC issues, and UART speed for kernel console. So far, Michael
  15. mboehmer

    PWM & SAR

    It's working perfectly. You need the correct files for dts/dtb, otherwise it will not work. As my systems are deployed already (no access, 2650m deep), I have other issues now to solve. I recommend to kindly address Neil Armstrong (no, not the one who was on Moon ) and ask for the correct files, and... to check them into to official branch In case you need help, please let me know, I can try to help, but my time is at the moment severily limited. Michael