| *** tpb has joined #litex | 00:00 | |
| *** lf_ has joined #litex | 00:47 | |
| *** lf has quit IRC | 00:47 | |
| *** FFY00 has quit IRC | 01:48 | |
| *** Degi_ has joined #litex | 01:54 | |
| *** Degi has quit IRC | 01:54 | |
| *** Degi_ is now known as Degi | 01:54 | |
| *** FFY00 has joined #litex | 01:59 | |
| *** Dolu_ has quit IRC | 02:18 | |
| *** lkcl has quit IRC | 02:48 | |
| *** lkcl has joined #litex | 03:02 | |
| *** CarlFK has joined #litex | 04:00 | |
| *** CarlFK has quit IRC | 04:59 | |
| *** lkcl has quit IRC | 06:01 | |
| *** Bertl_oO is now known as Bertl_zZ | 06:02 | |
| *** lkcl has joined #litex | 06:14 | |
| _franck_ | st-gourichon-fid what is annoying you with this change in the linker script ? | 07:59 |
|---|---|---|
| *** Bertl_zZ is now known as Bertl | 10:31 | |
| *** Dolu_ has joined #litex | 11:14 | |
| *** FFY00 has quit IRC | 11:29 | |
| *** FFY00 has joined #litex | 11:30 | |
| 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. | 11:51 |
| 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. ¯\_(ツ)_/¯ | 11:56 |
| st-gourichon-fid | "all symbols" -> providing the same C-runtime-level array without linker script trick. | 11:57 |
| _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) | 13:44 |
| _franck_ | and by the way there is _franck_ and _florent_ :) | 13:45 |
| zyp | _franck_, listing them in an array would reference them and keep them from being garbage collected, no tricks needed | 14:43 |
| 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 | 14:44 |
| *** lkcl has quit IRC | 14:53 | |
| *** CarlFK has joined #litex | 14:55 | |
| *** lkcl has joined #litex | 15:05 | |
| st-gourichon-fid | _franck_, thanks for your answer. And yes, I was bitten by the IRC client autocompletion. :-p | 15:14 |
| 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. | 15:15 |
| zyp | makes sense | 15:33 |
| zyp | at least if you're using peripherals that the bios runs initialization for | 15:33 |
| st-gourichon-fid | Running our own interactive commands (with readline) is an appreciated luxury. | 15:48 |
| _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. | 16:19 |
| *** Bertl is now known as Bertl_oO | 16:51 | |
| *** lkcl has quit IRC | 20:21 | |
| *** lkcl has joined #litex | 20:33 | |
| *** indy has quit IRC | 22:19 | |
| *** indy has joined #litex | 22:42 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!