Hi Kranthi, can you send me your resulting uImage (var/run/log/uImage) after a fresh built without NR_OF_CPUS changes to me personally so that I can test it on our board using my boot procedure?
Regards Stefan On 05/02/2017 11:54 AM, Kranthi Tej wrote: > Hello Stefan, > > I've cloned the genode repository freshly as you have suggested. I've > followed the following steps for building the uImage: > > * Created a build directory by using /tool/create_builddir wand_quad > * Included "RUN_OPT += --include image/uboot in [1] > * Changed RAM0_SIZE = 0x80000000 to RAM0_SIZE = 0x40000000 > * Run "make run/log" from the build directory [2] > > When I haven't changed NR_OF_CPUS, it is hanging at "Starting kernel > ..." itself. When I've changed NR_OF_CPUS to 1, I'm getting the > following output: > > MX6Q SABRESD U-Boot > bootm 0x30000000 > ## Booting kernel from Legacy Image at 30000000 ... > Image Name: > Image Type: ARM Linux Kernel Image (gzip compressed) > Data Size: 608176 Bytes = 593.9 kB > Load Address: 10001000 > Entry Point: 10001000 > Verifying Checksum ... OK > Uncompressing Kernel Image ... OK > > Starting kernel ... > > :virt_alloc: Allocator 0x200c40b8 dump: > Block: [00001000,10001000) size=256M avail=256M max_avail=256M > Block: [10585000,20001000) size=256496K avail=256496K max_avail=3144208K > Block: [2017b000,2017c000) size=4K avail=0 max_avail=0 > Block: [2017c000,e0000000) size=3144208K avail=3144208K max_avail=3144208K > Block: [f0004000,f0005000) size=4K avail=0 max_avail=3144208K > Block: [f0007000,f0008000) size=4K avail=0 max_avail=0 > Block: [f0009000,f000a000) size=4K avail=0 max_avail=262036K > Block: [f000a000,fffef000) size=262036K avail=262036K max_avail=262036K > => mem_size=4019097600 (3832 MB) / mem_avail=4019081216 (3832 MB) > > :phys_alloc: Allocator 0x200c304c dump: > Block: [10585000,10586000) size=4K avail=0 max_avail=0 > Block: [10586000,10587000) size=4K avail=0 max_avail=1042644K > Block: [10587000,10588000) size=4K avail=0 max_avail=0 > Block: [105ca000,105cb000) size=4K avail=0 max_avail=1042644K > Block: [105cb000,50000000) size=1042644K avail=1042644K max_avail=1042644K > => mem_size=1067683840 (1018 MB) / mem_avail=1067667456 (1018 MB) > > :io_mem_alloc: Allocator 0x200c5130 dump: > Block: [00000000,10585000) size=267796K avail=267796K max_avail=267796K > Block: [10588000,105ca000) size=264K avail=264K max_avail=2952790015 > Block: [50000000,ffffffff) size=2952790015 avail=2952790015 > max_avail=2952790015 > => mem_size=3227283455 (3077 MB) / mem_avail=3227283455 (3077 MB) > > :io_port_alloc: Allocator 0x200c619c dump: > => mem_size=0 (0 MB) / mem_avail=0 (0 MB) > > :irq_alloc: Allocator 0x200c7208 dump: > Block: [00000000,00000001) size=1 avail=1 max_avail=1 > Block: [00000002,0000001d) size=27 avail=27 max_avail=994 > Block: [0000001e,00000400) size=994 avail=994 max_avail=994 > => mem_size=1022 (0 MB) / mem_avail=1022 (0 MB) > > :rom_fs: ROM modules: > ROM: [1017e000,1017e158) config > ROM: [10154000,1017a900) init > ROM: [100d6000,10153b64) ld.lib.so <http://ld.lib.so> > ROM: [1017b000,1017d598) test-log > > > kernel initialized > Error: page fault in core thread (core): ip=0x20037b34 fault=0x68c88038 > > We are unable to detect what the problem is. Am I missing something in > the build process itself? > > Thanks, > Kranthi > > [1] build/wand_quad/etc/build.conf > [2] /build/wand_quad > > On Tue, May 2, 2017 at 1:57 PM, Stefan Kalkowski > <stefan.kalkow...@genode-labs.com > <mailto:stefan.kalkow...@genode-labs.com>> wrote: > > Hi Kranthi, > > On 05/02/2017 09:43 AM, Kranthi Tej wrote: > > We've already made this change. We are currently using this setting > > itself. Besides, making this change, we've changed the NR_OF_CPUS to 1 > > in [1]. If we let the default value of 4 be set, the device hangs at > > "Starting kernel ..." stage itself. We also tried setting the RAM0_SIZE > > to 0x20000000. Our board has a physical RAM of 1 GB. > > > > We have been facing the same pagefault for both the images (demo and > > log). The core isn't being started. Please provide any pointers to > > resolve this problem. > > Please, do not test the release version 17.02, but the _current_ master > branch, e.g., by cloning the git repository: > > g...@github.com:genodelabs/genode.git > > just to ensure whether this works for you. I've used this version > successfully with all 4 cores enabled on the same board. > > Regards Stefan > > -- > Stefan Kalkowski > Genode Labs > > https://github.com/skalk · http://genode.org/ > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > genode-main mailing list > genode-main@lists.sourceforge.net > <mailto:genode-main@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/genode-main > <https://lists.sourceforge.net/lists/listinfo/genode-main> > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > genode-main mailing list > genode-main@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/genode-main > -- Stefan Kalkowski Genode Labs https://github.com/skalk · http://genode.org/ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ genode-main mailing list genode-main@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/genode-main
