Apparently the problem was my version of U-Boot. Updated to U-Boot 2020.04-rc3-00108-gdb41d985f6 (Mar 11 2020 - 13:15:53 -0400) and things seem to be working now.
On Mar 11, 2020, at 10:09 AM, Mike Clark <undefinedsp...@gmail.com<mailto:undefinedsp...@gmail.com>> wrote: Did you try 0x84000000? http://sel4.systems/pipermail/devel/2020-February/002670.html On Mon, Mar 9, 2020, 10:13 AM Travis Wheatley <travis.wheat...@emergentspace.com<mailto:travis.wheat...@emergentspace.com>> wrote: Thanks for the reply Mike. I tried using the cmakes-arm-vm project discussed in the thread you provided. However I am seeing the same behavior. Regardless of which project I build or what load address I use (0x10000000 or 0x82000000) I still get the same behavior. When I type “go <address>” I get a message that says: ## Starting application at <address> … After that I see nothing at all on the serial port (aka, stdout). At this point I completely stumped. Is there some tweak I need to make to the serial port code before building? Other suggestions? On Mar 5, 2020, at 4:11 PM, Mike Clark <undefinedsp...@gmail.com<mailto:undefinedsp...@gmail.com>> wrote: Did you try anything from my thread from January? http://sel4.systems/pipermail/devel/2020-January/002595.html On Thu, Mar 5, 2020, 5:03 PM Travis Wheatley <travis.wheat...@emergentspace.com<mailto:travis.wheat...@emergentspace.com>> wrote: Hello all, I am spinning up on sel4 and having difficulty booting a kernel on a Jetson TK1 board. I have successfully downloaded the cmakes repo and can build the x86 version of the code and run it as a simulation. I can also successfully build the TK1 version by changing the -DARCHETECTURE argument passed to init-build.sh to “tk1”. This results in a single image file named “capdl-loader-image-arm-tk1” to show up in my images folder (as opposed to both a kernel image and “userland” image that get created in the x86 version). So… I put that image on an SD card, plug it into the TK1, boot to a uboot prompt, and load the image using the command “fatload mmc 1 0x82000000 <filename>”. I can use “md” to see that the image is actually loaded properly. However, when I type “go 0x82000000” I see no output what so ever going out of the serial port. What I expect to see is similar output to what was displayed in the x86 simulation. I posted the question to the IRC channel yesterday and someone suggested using bootm or bootelf. No luck with either of these. So… hoping someone here might be able to give me a clue. — Travis _______________________________________________ Devel mailing list Devel@sel4.systems<mailto:Devel@sel4.systems> https://sel4.systems/lists/listinfo/devel _______________________________________________ Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel
