[LEDE-DEV] QCA Dakota support
K.Mani
sailormani at gmail.com
Thu Mar 9 08:15:36 PST 2017
Hi Matthew,
(IPQ40xx) # smeminfo
flash_type: 0x6
flash_index: 0x0
flash_chip_select: 0x0
flash_block_size: 0x10000
flash_density: 0x1000000
partition table offset 0x0
No.: Name Attributes Start Size
0: 0:SBL1 0x0000ffff 0x0 0x40000
1: 0:MIBIB 0x001040ff 0x40000 0x20000
2: 0:QSEE 0x0000ffff 0x60000 0x60000
3: 0:CDT 0x0000ffff 0xc0000 0x10000
4: 0:DDRPARAMS 0x0000ffff 0xd0000 0x10000
5: 0:APPSBLENV 0x0000ffff 0xe0000 0x10000
6: 0:APPSBL 0x0000ffff 0xf0000 0x80000
7: 0:ART 0x0000ffff 0x170000 0x10000
8: 0:HLOS 0x0000ffff 0x180000 0x400000
9: rootfs 0x0000ffff 0x580000 0xa80000
Is this a nand or nor booting board?
Don't know.
SF: MX25L25635E, it's spi-nor i guess.
If i have to flash 'initramfs', should it be on HLOS partition start address?
Also attached a old boot log.
Thanks a ton
Mani
On Thu, Mar 9, 2017 at 8:52 PM, Matthew McClintock
<msm-oss at mcclintock.net> wrote:
> Can you share a full log? What is the flash_type from smem? Is this a
> nand or nor booting board? I suggest using initramfs first until you
> get things going.
>
> -M
>
> On Thu, Mar 9, 2017 at 7:11 AM, K.Mani <sailormani at gmail.com> wrote:
>> Hi Matthew,
>>
>> I built the qsdk, but the device flash failed & bricked.
>> and i get the u-boot prompt only.
>> Can you suggest me the flashing procedure for ipq40xx?
>>
>> https://source.codeaurora.org/quic/qsdk/releases/manifest/qstak/tree/?h=release
>> -- caf_AU_LINUX_QSDK_RELEASE_DAKOTA_CS_TARGET_ALL.3.0.1011.220.xml
>>
>> flashing ipq40xx:
>> flashed NOR Boot --- hlos & rootfs partition
>>
>> smeminfo:
>> partition table offset 0x0
>> No.: Name Attributes Start Size
>> 0: 0:SBL1 0x0000ffff 0x0 0x40000
>> 1: 0:MIBIB 0x001040ff 0x40000 0x20000
>> 2: 0:QSEE 0x0000ffff 0x60000 0x60000
>> 3: 0:CDT 0x0000ffff 0xc0000 0x10000
>> 4: 0:DDRPARAMS 0x0000ffff 0xd0000 0x10000
>> 5: 0:APPSBLENV 0x0000ffff 0xe0000 0x10000
>> 6: 0:APPSBL 0x0000ffff 0xf0000 0x80000
>> 7: 0:ART 0x0000ffff 0x170000 0x10000
>> 8: 0:HLOS 0x0000ffff 0x180000 0x400000
>> 9: rootfs 0x0000ffff 0x580000 0xa80000
>>
>>
>> Thanks again
>> Mani
>>
>> On Thu, Mar 9, 2017 at 12:32 PM, John Crispin <john at phrozen.org> wrote:
>>> Hi Matthew,
>>>
>>> can you point me at the tree to use on codeaurora ? i am also looking for
>>> the AP145 dts file. this is ipq8062 based
>>>
>>> John
>>>
>>>
>>>
>>> On 08/03/17 15:49, Matthew McClintock wrote:
>>>>
>>>> Most of the support for the SoC should be in place, the various Dakota
>>>> boards dk0{1,4,7}-c{1,2,3,4} are very similar. You could look at the
>>>> device tree's on codeaurora.org to compare the differences from a
>>>> supported platform and this variant.
>>>>
>>>> -M
>>>>
>>>> On Wed, Mar 8, 2017 at 2:47 AM, K.Mani <sailormani at gmail.com> wrote:
>>>>>
>>>>> I have a target board based on IPQ40xx, I want to port LEDE on it.
>>>>> Does LEDE has support for the following type:
>>>>>
>>>>> Model: Qualcomm Technologies, Inc. IPQ40xx/AP-DK04.1-C2
>>>>> Compatible: qcom,ipq40xx-apdk04.1qcom,ipq40xx
>>>>> SF: MX25L25635E
>>>>>
>>>>> Thanks
>>>>> Mani
>>>>>
>>>>> _______________________________________________
>>>>> Lede-dev mailing list
>>>>> Lede-dev at lists.infradead.org
>>>>> http://lists.infradead.org/mailman/listinfo/lede-dev
>>>>
>>>> _______________________________________________
>>>> Lede-dev mailing list
>>>> Lede-dev at lists.infradead.org
>>>> http://lists.infradead.org/mailman/listinfo/lede-dev
>>>
>>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: boot.log
Type: text/x-log
Size: 120131 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/lede-dev/attachments/20170309/d2cb1275/attachment-0001.bin>
More information about the Lede-dev
mailing list