10:58 <josuah> This happened to me in another context the same day (yesterday)

14:32 <marker5a> Hello everyone... relatively n00b here... newish to FPGAs and newer to Litex. I've got an Alchitry Cu board and I'm trying to load firmware onto my setup. I created an SoC using my base.py (https://pastebin.com/xfmU6E3g). When I run base.py --build --flash, it flashes fine and I can modify memory to toggle LEDs and send data out over UART, so that all seems good. I wrote a simple c program that literally sets the led register to a value of 1... quikc and

14:32 <marker5a> dirty (https://pastebin.com/YN5H9cv3).

14:32 <marker5a> I run litex_term --kernel=firmware/firmware.bin /dev/ttyUSB1 --safe (have to do safe otherwise I get CRC error) and I get liftoff but it doesn't do anything. I tried some other examples to run a console in firmware but it's not working. My guess is that the firmware is being loaded maybe into the wrong address and I'm not really sure where to start poking around, so I'm sort of looking for pointers to help get this thing rolling

14:43 <marker5a> also, just to clarify, I did also try running the examples from the litex-boards repo/folder. I did a ./alchitry_cu.py --build --cpu-type=picorv32 --flash in the targets folder of litex-boards, then ran make in the demo folder of litex but modified the build direcotry to point to the alchitry_cu build directory in the litex-boards repo and I get similar behavior... it shows iftoff but nothing after

14:48 <marker5a> and if this is suited for a github issue, I can go that route too, just don't like unneccesarily flooding github... would rather flood irc :)

16:57 <josuah> Hello marker5a

17:01 <josuah> do you have access to the bootloader?

17:01 <josuah> mem_list and mem_dump can help to check the addresses and make sure the content is the expected one

17:03 <josuah> How did you build the firmware? You might have a firmware.map file that contains the description of the memories configured in the linker script.

17:06 <josuah> https://pastebin.com/xfmU6E3g line 180: prog.flash(bios_flash_offset, f"{build_dir}/../../firmware/firmware.bin")

17:06 <tpb> Title: #!/usr/bin/env python3## This file is part of LiteX-Boards.## Copyrigh - Pastebin.com (at pastebin.com)

17:07 <josuah> here you could keep that on, and configure another address instead of `bios_flash_offset`, then simply check, with the bios/bootloader, that the memory is there and has the right data

17:08 <josuah> then, once you are there, you would know the full memory map, and would be able to check that this memory map matches your firmware.map

17:09 <josuah> You can also compare the bios.elf and firmware.elf's memory map with objdump

17:09 <josuah> s/objdump/readelf -a/

17:10 <josuah> wishing you luck, let us know how it goes!

19:09 <mithro> BTW People here might find the blog at https://chipsandcheese.com/ interesting

19:09 <tpb> Title: Chips and Cheese – The Devil is in the Details (at chipsandcheese.com)

19:46 <josuah> mithro: thank you for this heirloom! feel free to keep them coming :)

22:06 <marker5a> Thanks @josuah, I'll go through those items and see if I can figure out what's going on... appreciate the info. Unfortunately, I'll have to dig in tomorrow but if I find something that seems useful, I'll report back here and on github... thanks for your time!

22:48 <josuah> marker5a: feel free to ask here some more as you go :)