Dear Fabio Estevam,
In message CAOMZO5AiJtDt_CZrO6gzU=JiPp_2-etPiGFcK7ZhFhNNzxp3_A@mail.gmail.com you wrote:
- How come setenv is not working in the board file? I tried setenv in
different locations of board_early_init_f(), board_init(), board_late_init() and checkboard(), but it's not working. Did something change?
Haven't tried it, but if this does not work, then it is a bug that needs to be fixed. Do you have access to a mx53 qsb board? Does it work there?
Suffix _f trditionally means "running from flash", i. e. this is before relocation to RAM. Here we have usually only a read-ony data segment, no BSS at all, and only limted stack. All complicated stuff like setenv is only supposed to be available after relocation.
On mx6 we have several boards calling setenv from the board files.
Actual behaviour is hardware-dependent, but it's better not to make any such guesses.
Actually it is usually a very bad idea to mandatorily modify the envrionment in code. This is almost always a design error.
Best regards,
Wolfgang Denk