Parallella Community

sebraa,

You bring up some good points. The srec loader was a huge hack that we are trying to get away from, but I suppose just removing support was too draconic and we will have to live with this mistake a while longer...

Regarding the other two, I will let Ola respond so that we can see if this is a misunderstanding or what we can do about this. Did you read the release notes?

Anreas

I did not fully read the release notes until noticing that my code stopped working, so this is my own fault. I did read it before posting, though.

On the other hand, I did upgrade to ELF in my own infrastructure, so removing SREC support only affects programs based on older infrastructures. However, some of our projects date back to eSDK 4.x when ELF was not an option yet. I did like using SREC files though, since they are an extremely simple solution to the problem, and are useful as fallback solutions in special cases (e.g. the ELF loader rejecting my post-processed files). In fact, in my first tests I did post-processing on the SREC files manually (later using sed) before turning to binutils.

In any case, my main complaint about this is that the documentation was not updated accordingly and now simply states wrong facts. I tend to read documentation once completely through (taking notes) and then start coding based on what I read. I also prefer referring to documentation instead of code, so I rely on the documentation to be both truthful and the most important source of authority. If I can't trust the documentation, I can't trust the project.