snair,

The first question that comes to mind is, are you powering on the kit with the JTAG debugger connected to the J36 JTAG header? That might cause the symptoms that you're seeing.

Hi Aaron,

I am connecting the JTAG through a 20 pin ARM JTAG interface. I am not sure what a J36 JTAG header means...

snair,

"J36 JTAG header" refers to the Printed Circuit Board (PCB) designator of the connector. If you look at the SDK board, right above the header you are connecting to you should see the letters "J36."

Since you are booting the board with something connected to the JTAG header, have you adjusted the jumpers on the board? To the left of the JTAG header you should see another 6-pin header with the label "J6" above it. Most revisions of the board also have a note that says something like "JTAG ENABLE" near that header. You need to ensure that those jumpers are in the proper configuration if you want to connect via JTAG. Check the SDK User's Guide or the QuickStart Guide for the proper settings for your board.

Let us know if this helps.

Regards,
--mikee

Hi Michael,

I checked on JTAG connection, it is J36 that I am connecting the JTAG to. Also I cheched the J6 pins and its jumper settings, it is in JTAG enable mode, with pin 2 & 5 not connected, as is shown in the document. Also I removed the JTAG connection and put the jumpers to normal mode configuration, but it still seems to go to an unknown state, but again when I do a debug session in IAR for an simple program, the LoLo would come up in the terminal window.

I am kind of stuck with this problem as I am not sure what I have do to resolve it either.

Any suggestion and help would be greatly appreciated.

Thanks,
Sajiv

snair,

Can you post the procedure that you're going through, basically provide a step by step process for how LoLo is booted through the debug session?

Do you have bootstrap or bootloader code of your own loaded at block 0?

Thanks,

Okay,

I've got one more quick thing to check and then I think I need to let Aaron and the other guys in the support crew field this.

Is the Card Engine properly seated on the SDK? Double check this as sometimes, if the Engine isn't properly snapped into the two 40-pin connectors, you can get odd results such as this.

--mikee

Hi Mikee and Aaron,

The card engine is seated properly on the SDK. I double checked it too. Aaron, I will put a step by step procedure as to how I get the LoLo running in the debug session. I did try to debug a bootstrap program that I got off from Sharp site for this board. And it did say cannot write to 0x0, which is obvious as it was trying to load the debug version of the program to flash.

The only way to over write the BoLo would be flashing my bootstrap program, which would be a whole different procedure by itself.

Will send you the information in a while.

Thanks,
Sajiv

Hello Aaron,

This is procedure that I follow for the debug procedure in IAR:

1. Open a program that is to be debugged in IAR

2. General Oprions:
A. Target tab: - ARM922T
- Generate interwork code checked.
- Processor mode - ARM
- Little endian, Stack Align: 4 bytes

3. In the linker options:
A. Output tab: Format - debug information for C-SPY, with runtime
control modules and I/O emulation modules checked.
B. Config tab: - Override default program entry checked
- Entry label checked and enter as _main
All the other tabs are left as it is in default condition.

4. In Debugger options:
A. Setup tab: Driver - RDI
Run to checked and entered as main
B. Download tab: Nothing checked
C. RDI tab: Location to RDI driver on the manufacture (SIGNUM)
D. Allow hardware reset checked.
F. Catch expressions - Nothing checked

5. Start the debug session and the LEDs GPIO1 and status LED1 toggle as how it should. Open the terminal window and the LOSH> promot comes up.

I can use all the commands available in LoLo, as I would in a normal process. Now I stop the debug process and go back to terminal window, I cannot type anything and start the debug process and it would come up again.
Now, when I stop the debug session itself, the LEDs GPIO1, Status LEDs 1 & 2 start flashing much faster and it goes to an unknown state of some sought.
If I try to reset the board using the reset button, it would again go to the unknow state.

Hope I was able to get you some insight about the system configuration that I am working in and the procedure to get up LoLo running.

Thanks very much.

Regards,
Sajiv

Sajiv,

These questions might be obivious but I want to ask them none the less.

Can you verify that bolo still exists in flash at Block zero and that you are booting lolo from flash when you are using the IAR tools?

Are you running LoLo out of flash or is it a RAM version?

Thanks,

Hi Aaron,

The LoLo gets loaded from RAM, by using IAR. It gets loaded from C0004000 location.
Just as a check, I cleared the content of LoLo from the RAM, basically initialized the memory with 0 from C0000000 till C0006000, and reset the board. After which, I brought up LoLo, just to make sure that a copy of LoLo is getting copied to RAM, which means BoLo gets intialized in flash and a copy is writtent to RAM. And that is the case, meaning LoLo does get copied on to RAM.

Which means that the boot process is working as it should, just that after LoLo getting copied to the RAM, for some reason that I am just not able to figure out it doesnt get invoked...This is my perseption of the problem...But I am not sure how to rectify it...

Thanks in advance...

Sajiv

Sajiv,

Can you examine 0x0 on the card engine and post the value shown?

Thanks,

Aaron,

Here are the values at 0x0

0x00000000 EA00000C

Thanks,
Sajiv

Hi,

I was abe to flash a new copy of the BoLo and LoLo in the memory. This took care of the problem.

Thanks very much for all the help...

Regards,
Sajiv

snair,

No trouble at all. I'm glad that we could help. Please continue to use these groups to post any similar questions/problems/solutions.

Best regards,
--mikee