Hi Anish,
Thanks for pointing that out. I ran menuconfig and that fixed the compilation issue however, now I'm getting this error when I try to run it:
spl_load_image_fat_os: error reading image args, err - -1
I guess I'll fool around with menuconfig see if there is something that should be enabled and isn't. (maybe you have a suggestion on this?)
Anyway, I'll post updated defconfigs when I figure it out. Hopefully this is just a config issue.
Thanks, Gilles .
On Mar 14, 2015, at 10:55 , Anish Khurana anish.khurana130181@gmail.com wrote:
Hi Gilles,
This u-boot version is having lot of changes , they have enabled Kconfig similar to Kernel and having GUI support ( make menuconfig) . so if you are gettting error as you mentioned , try to add Device model configurations and SYS malloc() as :
Steps 1 make <birdland_bav335x config> Step 2 make menuconfig Step 3 Device driver -> Enable driver model, enable Driver model for serial) Step 4 malloc() pool , General setup --> Enable malloc() pool.
Please try this , I think it will work.
Thanks, Anish
On Sat, Mar 14, 2015 at 10:36 AM, Gilles gilles@gigadevices.com wrote:
Folks,
I posted a patch to add support for bav335x boards (a322aad99de4). The patch was tested against v2015.04-rc1 and worked perfectly but somehow, something was introduced since then which breaks the board support.
There are two main errors I need to fix before posting another patch but need help with the second error.
The first error is easy. Compilation throws: #error "Please define NS16550 registers size." which I can simply fix by defining CONFIG_SYS_NS16550_REG_SIZE in include/configs/bav335x.h ((( Altough I am stil puzzled as to why this was defined as -4 (where?) on v2015.04-rc1 )))
After adding the define, everything compiles up to failing on the final link with:
drivers/serial/built-in.o: In function `get_current': /home/gilles/bbdev/u-boot/drivers/serial/serial.c:389: undefined reference to `default_serial_console' drivers/serial/built-in.o: In function `serial_initialize':
Can anyone please explain what changed between 2015.04-rc1 and 2015.04-rc2 which could cause such a behavior? I have spent the last couple hours re-basing a branch to see where it breaks as to maybe get a clue on what changed but no luck so far. Any tips would be appreciated.
Thanks, Gilles .
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot