From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Schweigstill Date: Tue, 18 Jul 2006 12:54:17 +0200 Subject: [U-Boot-Users] clarifications u-boot for arm In-Reply-To: <8bf247760607140651l4e0bc8fdh55e1e0b731209597@mail.gmail.com> References: <8bf247760607140029l62f6c124idee300237361518f@mail.gmail.com> <20060714081656.373AA352681@atlas.denx.de> <8bf247760607140651l4e0bc8fdh55e1e0b731209597@mail.gmail.com> Message-ID: <44BCBDD9.8040900@schweigstill.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Ram! Ram schrieb: > Does this really invoke start_armboot?. This is because > _start_armboot is what is > stored in pc and not start_armboot and there is also a branch > point _start_armboot (underscore start_armboot) Please see above. And why don't you learn the syntax and semantics of ARM assembler before you send messages to this list? > I didnt understand the things relating interrupt and thier processing though. In order to understand the interrupt related things I recommend reading some documents about ARM architecture, your processor datasheet(s) AND U-BOOT DOCUMENTATION. Then you will find out by yourself why it is so difficult to understand interrupt handling on most platforms... :-) And why don't you just hook your JTAG debugger on the interrupt entry point and try to follow the execution flow? Then you will also notice something very important in U-Boot... Andreas Schweigstill -- Dipl.-Phys. Andreas Schweigstill Schweigstill IT | Embedded Systems Schauenburgerstra?e 116, D-24118 Kiel, Germany Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436 Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/