Following current instructions for U-Boot result in build failing with "bad value (armv5) for.."

Following current instructions for U-Boot result in build failing with “bad value (armv5) for -march= switch”

First, thank-you to the community - especially Robert C Nelson for all of his hard work and dedication.

After having (speculatively) succeeded in the Kernel build process, I’ve moved-on to trying to create an SD card.
I am carefully stepping through the various steps documented here: https://eewiki.net/display/linuxonarm/BeagleBone+Black with the understanding that the best way to do this is to build each of the individual items that constitute a complete image and then “assemble” them accordingly. I’m not looking for any shortcuts - such avoiding the issue by plunking my Kernel onto an existing SD - I just wan tto follow directions.

While building U-Boot ( https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot), I’m encountering an error which has stopped me dead in my tracks.

lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
/*
^
kbuild:43:recipe for target ‘lib/asm-offsets.s’ failed

For the sake of completeness, I have followed the instuctions as listed, including the application of what appears to be two patch files from an RCN repository.

Any guidance would be appreciated. The purpose of my kernel build is to subsitute-in the older serial driver - as we’re working on a RS-485 project in which the attached hardware requires the use of the GPIO-driven TXEN mechanism which is not implemented (and is not likely to be imlemented in that manner) in the newer driver. Unfortunately, the hardware design does not use the RTS/CTS signals at all - so I am very limited as to what I can do now - at least until we redesign the attached circuit.

In essence - I am attempting to do the opposite of this procedure:
http://processors.wiki.ti.com/index.php/Sitara_Linux_UART_-_Switching_to_8250_Driver

I anticipate using a modified (for uart1) version of the BB-UART4-RS485 for configuring my port, in which the BB acts as a MODBUS Master.

If anyone has performed this procedure before on a current image and can make it available to me, that would also be useful as time is a consideration and my expertise at Linux kernel building is minimal. That being said, I’m hopeful that after some repetition I will become eventuall proficient at building the Kernel as required as the BB is slated to play a significant role in our product development plans.

This just means you skipped the previous instruction to set the CC variable… or opened a new terminal window.

Regards,

Hi Robert,

I’ve also faced the same issue and got resolved with your suggestion. Thank you .

Regards,
Venkatesh