NOR Direct boot custom board OMAP L 137

Have you connected the NOR flash properly in HW level?
I have seen some E2E posts that you are not able to access the flash >32KiB, also our TI employee Shankari also able to reproduce the same with disabling the CS3, so could you send/attach the schematics here for checking the schematics by HW person.

If you are not able to access, or want to access the NOR with GPIOs then you may need UBL code which should be less than or equal to 32KiB(as you said) to configure the NOR more than 32KiB.

Hi Titus,

Yes the hardware is connected properly and I have used NORWRITER before to flash a small program < 32kb that blinks LED and it worked ok.

here is the schematic if you want to take a look 

My question is :

I want to use the method NOR direct (NOT NORWRITER) described by bootloader document but I don't know how.

Can you please walk me through the necessary steps to build a specific UBL that I can use for this specific case.

What I should write in this UBL and how that can make the code able to execute directly from NOR. 

Thank you for your support

I have a question.
for AIS NOR Boot, if the AIS image.bin exceeds 32 KB , what should be included in the image to fully transfer to L2 RAM of the DSP knowing that OMAP bootloader can access only 32KB.
if a secondary boot loader is required, how this would be combined with DSP + ARM codes.
that means I need DSP UBL that Enables the ARM and copy (DSP code + ARM code) ? and if it is the case should I use a function inside DSP ubl to copy DSP code ,which has been already stored in the NOR somewhere, from NOR to L2 RAM
Thanks for the support

Dear Ahmed,
From your schematic, I understood that you have used A0-A14 (15 address lines) for NOR flash interfacing and some of the address lines of NOR has been connected to GPIOs.

So, you are getting expected behavior only, you can access only upto 32KiB since you have 15 address lines.

If you want to access more than 32KiB then you have to drive the GPIOs (upper address lines) manually.

Hi Titus,

Thank you for your support.

if you check my previous post 

http://e2e.ti.com/support/dsp/omap_applications_processors/f/42/p/472800/1702653#1702653   I managed the upper address lines using a function to toggle gpio while addressing upper memory space.

my concern is during boot sequence of omap 137  and assume I have AIS image > 32KB how it is going to work.

should I keep the image less than 32KB and only include DSP ubl that enable the ARM what about the DSP code that if it is added will generate an AIS image bigger than 32KB.

Thank you 

Ahmed 

Hi Ahmed,

Definitely it won't work since RBL can't use gpio pins right?

Since you are using OMAPL137, you may have to use DSP UBL code upto 32KiB, then you can access the flash more than 32KiB by using ARM UBL and u-boot which has gpio drive code as address lines.

Thank you Shankari,
Would you please explain more this process, if you can refer me to a document.
I am not planning to use linux,
for the DSP ubl should I include a function that will copy DSP code from NOR

Thanks
Ahmed