From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Gorsulowski Date: Fri, 21 Jan 2011 13:39:06 +0100 Subject: [U-Boot] U-Boot support for board(s) meesc, otc570 In-Reply-To: <4D3972ED.7040403@emk-elektronik.de> References: <20101127215828.7CD40220233A@lilith> <4D072AED.6080703@esd.eu> <4D355CFC.5050806@esd.eu> <4D356200.5000801@aribaud.net> <4D3577A9.8050505@esd.eu> <4D3586D7.7040009@emk-elektronik.de> <4D37E8CE.5010404@esd.eu> <4D392AFC.6080200@emk-elektronik.de> <4D394DDD.5020304@esd.eu> <4D3963A8.8070202@emk-elektronik.de> <4D396B65.8080905@esd.eu> <4D3972ED.7040403@emk-elektronik.de> Message-ID: <4D397E6A.1050100@esd.eu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hello Reinhard, ... >> >> Back to the problem... >> In my opinion, my USART configuration is correct. I still have no idea, >> why there is no output on DBGU. > > I am at a loss there, too. > > Which USART is the output coming from instead? Is it really console output > or maybe some other, independent pulses? I don't know, to which USART the output goes. I guess you assume, my "GPIO debugging" was to meassure the pulses on the USART pins. But no, my GPIO debugging was as follows: -set gpio pin with led attached -send characters by puts() (wherever it goes) ;-) -reset gpio pin -measure time between high- and low- rising edge on gpio pin -calculate baudrate (on DBGU pin, there is no pulse at all past starting U-Boot) > > Can you verify that the value for ATMEL_BASE_DBGU in at91sam9263.h is > correct? Yes, according to datasheet, Debug Unit Control Register (DBGU_CR) is located at 0xFFFFEE00. And in at91sam9263.h is defined: #define ATMEL_BASE_DBGU 0xffffee00 > > Are you using the actual driver source? It should have lines like > atmel_usart3_t *usart = (atmel_usart3_t*)CONFIG_USART_BASE; > at the begin of each function. Yes, I'm using the driver with your changes from 2010-11-03 16:32:56 > > Best Regards, > Reinhard > > Best Regards, Daniel