curuvar commented on PR #6850: URL: https://github.com/apache/incubator-nuttx/pull/6850#issuecomment-1215512998
I’m not sure how this would work. The Pico does have a flash chip where the program is loaded but no file system is configured by default. If we had a filesystem we could easily copy the chip firmware as it is supplied by pico-sdk as a binary file which we could read from anywhere. Putting this on a filesystem would not actually help though. It is easy enough to add the binary data to the NuttX image, and it would wind up stored on the same flash chip anyway. Why add file system overhead. Loading the nvram image is more of a problem. It is only available from pico-sdk as an include file. That is useless at run time, and if I were to pull the data out of that include to make a file that could be loaded at run-time, I’d still need to store it somewhere in the repo, which it the issue we’re trying to avoid. > On Aug 15, 2022, at 11:38 AM, Xiang Xiao ***@***.***> wrote: > > > @xiaoxiang781216 commented on this pull request. > > In drivers/wireless/ieee80211/bcm43xxx/cyw_chip_43439.c <https://github.com/apache/incubator-nuttx/pull/6850#discussion_r945883843>: > > > @@ -27,25 +27,34 @@ > > #include "bcmf_interface.h" > > +#include "../../../cyw43439.nvram.image" > can we load image from storage? > > — > Reply to this email directly, view it on GitHub <https://github.com/apache/incubator-nuttx/pull/6850#pullrequestreview-1072853730>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOAJTIXEHMWBRDHXXIDBBU3VZJQBDANCNFSM56O2RK7A>. > You are receiving this because you were mentioned. > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
