19:56 | vagrantc | are the ram schematics used on the cubox-i4x4 posted somewhere? |
20:16 | vpeter | vagrantc: I think there is schematic for microsom on wiki? |
20:17 | vagrantc | https://www.solid-run.com/download/pub/solidrun/SR-uSOM-mx6/ |
20:17 | vagrantc | ?? |
20:17 | vpeter | I hit this RTC bug with cubox-i if anyone interested: https://github.com/systemd/systemd/issues/1143 |
20:18 | vpeter | [ 3.078206] rtc-pcf8523 2-0068: setting system clock to 2066-01-02 00:25:03 UTC (3029617503) |
20:18 | vagrantc | http://wiki.solid-run.com/doku.php?id=products:imx6:microsom:quad doesn't give much information |
20:20 | vpeter | maybe http://wiki.solid-run.com/lib/exe/fetch.php?media=imx6:microsom:docs:sr-usom-mx6-rev-1_3-simplified-schematics.pdf |
20:22 | vagrant | 20:22 * vagrantc doesn't see any references to ddr, ram, memory, etc. |
20:22 | vpeter | Sorry, I didn't open :( |
20:23 | vagrantc | in particular, looking for if there are any differences between the 4gb and 2gb imx6q variants |
20:23 | vpeter | You can see this from u-boot which chips are used. |
20:24 | vagrantc | the u-boot sources, or u-boot shell? |
20:25 | vagrantc | i'm working on updating support in u-boot mainline, and i've managed to get it to work with 3.8gb, but that builds hangs on a 2gb machine |
20:39 | vpeter | u-boot sources |
20:41 | vpeter | You need to init dram correctly. Check board/solidrun/mx6_cubox-i/mx6_cubox-i_spl.c file |
20:45 | vpeter | I think mainline u-boot lack support for all the soms as you already figure out. |
20:50 | vagrantc | yeah, a bit over my head at the moment, but trying to swim anyways |
20:51 | vagrantc | as far as i can tell, it solidrun's u-boot-imx6 branch basically configures it for 4gb weather it has 2gb or 4gb, and then does a test to see how much memory is actually available |
20:56 | rabeeh | vagrantc: true; it's set to 4GByte and then there is a code that tries memory segments until it finds segments |
20:57 | rabeeh | https://github.com/SolidRun/u-boot-imx6/commit/e817fa3165a607b581433a6abfe37e095a5d1dc9 |
20:58 | vagrantc | right |
21:00 | vagrantc | which i conceptually understand, though forward-porting it to mainline u-boot is another adventure entirely :) |