-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use of uninitialized value in TM4C NetworkInterface.c #1026
Comments
Hi @jonathangjertsen , Github doesn't let me see mentioned pages, it shows a big number 500. And even TM4C/NetworkInterface.c doesn't load, where
Later on, the word is loaded again:
It looks like the TM4C driver still needs some work. |
I guess |
These are the (local) definitions that you mention:
where
So I would propose to reserve DMA buffer of
And define :
And use it like this in the two locations:
A network buffer is preceded by 10 hidden bytes, called
|
@htibosch Thank you for taking a look at this. I completely agree with your justification. I'll see about getting this updated so that this default uninitialized variable doesn't bite anyone else using this port in the future. |
@kstribrnAmzn wrote:
No problem. Here is a picture that may help to get a good understanding: I like a |
Thank you for raising change @archigup @jonathangjertsen If you have some time can you please help in validating the change once, before we merge it. Thank you |
@jonathangjertsen Thank you for the quick update. Will we review it and merge it. Thanks again for reporting the issue. |
The fix got merged. Closing the issue. Thank you |
I got a warning when trying to port a project from TI CCS to the GNU ARM toolchain. Specifically on this line:
FreeRTOS-Plus-TCP/source/portable/NetworkInterface/TM4C/NetworkInterface.c
Line 485 in 5e55153
GCC warns that
'buffer_size_requested' may be used uninitialized
. Indeed, it is declared here and never initialized:FreeRTOS-Plus-TCP/source/portable/NetworkInterface/TM4C/NetworkInterface.c
Line 450 in 5e55153
Note that the port works great despite this apparent bug. But it seems like this should cause issues with the DMA. Tagging @jscott-hotstart in case you remember what
buffer_size_requested
should be.The text was updated successfully, but these errors were encountered: