Daniel Hayes

So this line "-C", "link-arg=-Thifive1-link.x" would change to "-C", "link-arg=-newlink.x" if newlink.x was in my project tree ?

Will I need to modify the memory-hifive1-revb.x too, or just the linker?

Are the region alias' sensitive to renaming? For example, keeping U and M level code separate wouldn't I need to have a .textM and a .textU etc? Maybe I can...

I've never done this before, obviously. How completely nuts does this look? INCLUDE memory-fe310.x MEMORY { MFLASH ORIGIN = 0x20000000, LENGTH = 2M UFLASH ORIGIN = 0x20200000, LENGTH = 2M...

Wow, really? LOL, cool. Obviously, I can tweak the region sizes a bit to not waste space, just divided everything in half to start. I will get rid of the...

Right, that makes sense. If I did that, then I wouldn't need the change the region names just the memory boundaries. I would also have to $cargo run twice this...

I really appreciate your help!

One more thought. I plan on entering the user mode memory section by setting the stack pointer address and changing to u mode. When I write my user mode code,...

I see what you are saying. Do you have any suggestions for the memory definition file. When I try to build with the extra -C argument, it says that "RAM"...

Nope, the problem is the quickstart template is adding the -Thifive1-link.x argument which calls the hifive-memory.x file then link.x linker. I think I can just do this ` "-C", "link-arg=-Tnew-memory.x",...