IRC log of #cubox of Fri 20 Oct 2017. All times are in CEST < Back to index

09:50 jnettlet[m]> topi`: sorry for the breaks in communication. I have been in Israel so I get pulled into many more meetings than usual. I am heading back to the EU today.
11:50 topi`> remember to grab a i.MX8 board with you :D
11:50 topi`> so that the rest of us can be envious
11:51 vpeter> Don't forget to post a picture :)
11:55 topi`> jnettlet[m]: are you familiar with the factory setup at all? I forgot to ask for ethernet MACs, we'd prefer them to be done at factory time. I guess it's possible?
11:56 jnettlet[m]> topi`: yes it is possible. Have Ilya add it to your order
11:57 topi`> the ethernet MACs are our only way of telling the boards separate :)
11:57 jnettlet[m]> Just getting ready to go through security but will be online after that. Have a couple hours before the flight.
11:57 topi`> probably there are other avenues for identifying the boards, though
11:57 topi`> like some ID inside the i.mx6
11:57 topi`> good luck with the security, don't look too suspicious :)
11:57 topi`> remember to shave, etc :)
16:47 Ke> my macchiatobin boot freezes at mv_ddr: mv_ddr-armada-17.06.1-g47f4c8b-dirty (Oct 20 2017 - 14:31:00)
16:47 Ke> mv_ddr: completed successfully
16:48 Ke> dirty part is just me adding {} to appease the compiler
16:48 Ke> built on the crosscompiler of debian stretch on amd64 compile host
16:53 Ke> jnettlet[m]: are you in general able to build this marvell firmware with the latest gccs
16:53 Ke> obviously the fact that it does not compile out of the box implies it's not the primary target
17:10 Ke> http://wiki.macchiatobin.net/tiki-index.php?page=Setup+alternative+boot+sources actually it's where the example output ends here, what should happen at that point?
17:11 Ke> obviously I was expecting either u-boot console or error when trying to load the next stage
17:14 Ke> better get drunk and call these guys topi` mentioned
20:04 jnettlet[m]> Ke: I have built and run it against GCC 6.3. there are a few patches to clean up the bad coding style.
20:08 Ke> jnettlet[m]: any idea, what is supposed to happen, if I build according to the build instructions and boot from SD
20:08 Ke> definitely it get through the raminit, but doesn't seem to want to do anything after that
20:09 Ke> jnettlet[m]: anyway, if you want to have a weekend, please do
20:21 jnettlet[m]> Ke: I will have access to my mcbin Sunday, will double check then. I have a few patches in my tree but nothing major
20:22 Ke> I guess the main thing is, that I don't even know, what is the expected behaviour
20:23 Ke> perhaps I am supposed to provide the next stage somewhere to not to make it silently fail
21:07 jnettlet[m]> Ke: note you can maximum run the DDR at 2133, 2400 won't boot
21:07 jnettlet[m]> I think it says 2100 on the silk screen
21:08 Ke> I believe the defaults I am using are the low settings
21:08 Ke> also "mv_ddr: completed successfully" is what I get
21:09 Ke> obviously mv_ddr can just lie and pipe all my dram to /dev/null
21:09 jnettlet[m]> Odd. The default settings should have no problems.
21:10 Ke> I may have done some command incorrectly, I would perhaps mostly want to know, what is the expected behaviour there
21:12 Ke> I could also try EFI, might actually even be, what I want
22:23 flips> hm, I guess I might have to update something on my i4Pro, to patch the recent wifi issue (it's on a really old kernel I think, been so stable I forgot about patching etc)
22:26 flips> hm, can I update openelec (6.x) by placing LibreELEC-imx6-8.0.2.img.gz in /storage/.update/ ? (Cross grade and skip a major version?) :-D
22:34 flips> ... or rather LibreELEC-imx6.arm-8.0.2.tar ...