public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3: EVM: Linker errors across tool chain versions
Date: Thu, 16 Dec 2010 15:31:21 +0100	[thread overview]
Message-ID: <4D0A22B9.9090708@ahsoftware.de> (raw)
In-Reply-To: <4D0A186B.1040006@ahsoftware.de>

Am 16.12.2010 14:47, schrieb Alexander Holler:

> To put some salt into the wounds ;) , Using gcc 4.5.1 board_init_f isn't
> reached here. When I'm using gcc 4.3.5 it is reached. In both cases I've
> used the same version of binutils, 2.20.1.
>
> For a test without using jtag, I've modified board_init_f to be
>
> -----------
> board_init_f()
> {
> turn_on_leds
> while(1) ;
> ...
> }
>
> I'm working with the master (f8689b9eb3a7f6925cd50404a12479889188c510)
> on a beagleboard, using
> --------
> make mrproper
> make omap3_beagle_config
> make
> --------

To be precise, turn_on_leds is:

-------
// GPIO5
#define GPIO5_OE        (*((volatile unsigned long *)0x49056034))   // 
Output Data Enable Register (Table 24-27)
#define GPIO5_DATAOUT      (*((volatile unsigned long *)0x4905603C)) 
// Data Out register (Table 24-31)
#define LED1 0x00200000   // Bit 21
#define LED0 0x00400000   // Bit 22
// PRCM
#define CM_FCLKEN_PER      (*((volatile unsigned long *)0x48005000)) 
// Controls the modules functional clock activity. (Table 4-237)
#define CM_ICLKEN_PER      (*((volatile unsigned long *)0x48005010)) 
// Controls the modules interface clock activity (Table 4-239)
// SCM
#define CONTROL_PADCONF_UART1_TX  (*((volatile unsigned long 
*)0x4800217C))   // Pad configuration for GPIO_149 [31:16] (Tables 7-4 & 
7-74)
#define CONTROL_PADCONF_UART1_CTS (*((volatile unsigned long 
*)0x48002180))   // Pad configuration for GPIO_150 [15:0]  (Tables 7-4 & 
7-74)
// Set the pinmux to select the GPIO signal
CONTROL_PADCONF_UART1_TX &= 0x0000FFFF; //  [31:16]=GPIO_149  - Clear 
register bits [31:16]
CONTROL_PADCONF_UART1_TX |= 0x00040000; //  [31:16]=GPIO_149  - select 
mux mode 4 for gpio
CONTROL_PADCONF_UART1_TX &= 0xFFFF0000; //  [15:0] =GPIO_150  - Clear 
register [15:0]
CONTROL_PADCONF_UART1_TX |= 0x00000004; //  [15:0] =GPIO_150  - select 
mux mode 4 for gpio
// Switch on the Interface and functional clocks to the GPIO5 module
CM_FCLKEN_PER |=  0x20; // Enable GPIO5 F clock
CM_FCLKEN_PER |=  0x20; // Enable GPIO5 I clock
// Configure the GPIO signals
GPIO5_OE      &= ~(LED1+LED0);  // Set GPIO_149 & GPIO_150 (GPIO 4 bit 
2) to output
GPIO5_DATAOUT |=  LED0;  // Set GPIO_150 high
GPIO5_DATAOUT |= LED1;  // Set GPIO_149 high
//GPIO5_DATAOUT &= ~LED1;  // Set GPIO_149 low
-------

(code stolen from somewhere on the web, just to show bss isn't used here)

Regards,

Alexander

  reply	other threads:[~2010-12-16 14:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  8:25 [U-Boot] OMAP3: EVM: Linker errors across tool chain versions Dirk Behme
2010-12-12 10:08 ` Albert ARIBAUD
2010-12-12 10:32   ` Dirk Behme
2010-12-12 11:40     ` Albert ARIBAUD
2010-12-14 15:42       ` Dirk Behme
2010-12-14 16:01         ` Albert ARIBAUD
2010-12-14 16:14           ` Wolfgang Denk
2010-12-16 13:47           ` Alexander Holler
2010-12-16 14:31             ` Alexander Holler [this message]
2010-12-16 15:20             ` Dirk Behme
2010-12-16 16:55               ` Alexander Holler
2010-12-14 16:21         ` Wolfgang Denk
2010-12-16 10:10           ` Dirk Behme
2010-12-17 10:39             ` Dirk Behme
2010-12-30 12:04               ` Premi, Sanjeev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D0A22B9.9090708@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox