| 01:11 | heap_ | whats going on with that cubox? |
| 01:12 | heap_ | http://pastie.org/10579189 |
| 06:32 | sanjeevs | which defconfig need to use for humming board |
| 07:12 | sanjeevs | ping Jnettlet |
| 07:12 | jnettlet | sanjeevs, what's up? |
| 07:14 | sanjeevs | hi |
| 07:14 | sanjeevs | how are you doing ? |
| 07:15 | jnettlet | hanging in there. Yourself? |
| 07:15 | sanjeevs | not Bad |
| 07:15 | sanjeevs | I am using i4pro and while booting kernel with dtb seeing kernel panic |
| 07:15 | sanjeevs | Hence I need your support |
| 07:16 | sanjeevs | Kernel panic - not syncing: ERROR: Failed to allocate 0x2000 bytes below 0x0. |
| 07:17 | jnettlet | I would need to see more of the panic than that. Can you copy the output from the console into pastebin.com? |
| 07:17 | sanjeevs | I could see that dtb has been read sucessfuly and I am attaching comlete logs for your reference |
| 07:18 | jnettlet | thanks |
| 07:18 | sanjeevs | http://pastebin.com/6G6L7had |
| 07:22 | sanjeevs | I think we need to look around cma: CMA: failed to reserve 256 MiB |
| 07:25 | jnettlet | sanjeevs, well it looks like your memory isn't being setup properly. |
| 07:25 | jnettlet | what does u-boot report/ |
| 07:25 | jnettlet | ? |
| 07:28 | jnettlet | you should see a line that says something like DRAM: |
| 07:34 | sanjeevs | in defconfig we should set option CONFIG_VMSPLIT=2G instead of VMSPLIT_3G |
| 07:35 | sanjeevs | it shows DRAM 2 GIB |
| 07:35 | jnettlet | either should work fine, but in general we recommend using VMSPLIT_3G |
| 07:38 | sanjeevs | DRAM controller initialiaztion look's OK |
| 07:38 | sanjeevs | So i4pro by default comes with 2GB RAM correct |
| 07:41 | jnettlet | correct |
| 07:41 | jnettlet | sanjeevs, can you download one of our new debian images and test that it boots? |
| 07:45 | sanjeevs | I assume that if DRAM had an issue it wouldn't parse stb file |
| 07:45 | sanjeevs | sorry dtb file |
| 08:57 | sanjeevs | Can anyone let me know the part number of DDR3 2GB on uSOm |
| 09:10 | sanjeevs | Do we have schematic of DDR3 RAM also |
| 09:11 | sanjeevs | hello jnettlet |
| 09:12 | sanjeevs | is it possible that this Kernel panic is due to DRAM wrong initiliazation |
| 09:12 | jnettlet | sanjeevs, no. There is no need since it is integrated onto the microsom |
| 09:12 | jnettlet | if you are using our u-boot then that is not possible |
| 09:12 | jnettlet | if you are using upstream u-boot then it is very possible, but we can't support that. |
| 09:13 | sanjeevs | I am using my own uboot and my uboot code initialize 1 GB not 2GB |
| 09:14 | sanjeevs | can I see the pin schematic of DRAM on uSOM and do you know which part number has been used for DDR3 RAM |
| 09:15 | jnettlet | sanjeevs, all the information that is publicly available is on the website already. |
| 09:16 | sanjeevs | is your 2 GB DDR3 initilization is different from Nitrogen6x ddr 3 initialization |
| 09:16 | jnettlet | yes, all our initializations are specific to the various microsom revisions. |
| 09:16 | sanjeevs | I am using SR-uSOM-MX6-rev-1_3 schematic but don't see interface with DDR RAM |
| 09:17 | jnettlet | yes because that is not part of the open documentation |
| 09:17 | sanjeevs | hmm and DDR3 RAM part number is also not opensource |
| 09:18 | jnettlet | I do not have the information readily available right now I am sorry. You can read the part number directly from your microsom. |
| 09:18 | sanjeevs | Now I am modifying DDR initialization as per uboot and if any clarification required I will ping you |
| 09:19 | jnettlet | If you are not using our u-boot then I can't spend much more time on this. |
| 09:19 | sanjeevs | Ok |