_florent_ changed the topic of #litex to: LiteX FPGA SoC builder and Cores / Github : https://github.com/enjoy-digital, https://github.com/litex-hub / Logs: https://freenode.irclog.whitequark.org/litex
tpb has quit [Remote host closed the connection]
tpb has joined #litex
lf_ has joined #litex
lf has quit [Ping timeout: 260 seconds]
FFY00 has quit [Ping timeout: 260 seconds]
Degi_ has joined #litex
Degi has quit [Ping timeout: 272 seconds]
Degi_ is now known as Degi
FFY00 has joined #litex
Dolu_ has quit [Ping timeout: 260 seconds]
lkcl has quit [Ping timeout: 240 seconds]
lkcl has joined #litex
CarlFK has joined #litex
CarlFK has quit [Quit: Leaving.]
lkcl has quit [Ping timeout: 240 seconds]
Bertl_oO is now known as Bertl_zZ
lkcl has joined #litex
<_franck_> st-gourichon-fid what is annoying you with this change in the linker script ?
Bertl_zZ is now known as Bertl
Dolu_ has joined #litex
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #litex
<st-gourichon-fid> _florent_, thanks for asking! In our design, another microcontroller runs code compiled with another SDK and linker script, and little flexibility without modifying the SDK itself, which contains the linker script used. So far we could progress without modifying the SDK.
<st-gourichon-fid> I considered alternatives, like: before compilation, generating a C-source-level array listing all symbols. Fully scripted "build in one step" of course. We can also run a modified SDK from now on. ¯\_(ツ)_/¯
<st-gourichon-fid> "all symbols" -> providing the same C-runtime-level array without linker script trick.
<_franck_> st-gourichon-fid without the linker section and the KEEP attribute, you may have to find a trick to keep cmd functions in the object file (not beeing stripped away)
<_franck_> and by the way there is _franck_ and _florent_ :)
<zyp> _franck_, listing them in an array would reference them and keep them from being garbage collected, no tricks needed
<zyp> st-gourichon-fid, are you saying that you are building the litex bios against the SDK for another microcontroller? I'm not sure I understand exactly what you're trying to do
lkcl has quit [Ping timeout: 256 seconds]
CarlFK has joined #litex
lkcl has joined #litex
<st-gourichon-fid> _franck_, thanks for your answer. And yes, I was bitten by the IRC client autocompletion. :-p
<st-gourichon-fid> zyp, the other microcontroller is an external chip that can access the wishbone bus, so it can be very handy to run the bios prompt on that chip.
<zyp> makes sense
<zyp> at least if you're using peripherals that the bios runs initialization for
<st-gourichon-fid> Running our own interactive commands (with readline) is an appreciated luxury.
<_franck_> zyp you're right, I've misread "generating a C-source-level array listing all symbols". I was thinking at something that would have emulated the linker section.
Bertl is now known as Bertl_oO
lkcl has quit [Ping timeout: 264 seconds]
lkcl has joined #litex
indy has quit [Ping timeout: 272 seconds]
indy has joined #litex