Hi Dalon,

That is exactly what I did. I created a cff_from_mmc_ext function at this
very same file you mentioned. But then I ran into the problem where the
ext4_fileread just returns with the following error:
ext4fs_devread read outside partition 4776

How is the support for ext4 on the arria10 branch? (

   - socfpga_v2014.10_arria10_bringup
   
<https://github.com/altera-opensource/u-boot-socfpga/compare/socfpga_v2014.10_arria10_bringup>
   )
   -


Thanks !

David


On Mon, Apr 4, 2016 at 8:21 PM, Dalon Westergreen <[email protected]>
wrote:

> its entirely plausible, but not supported.  Programming from fat is done
> during boot using file_fat_read_at which reads bits of the fpga image to
> ram and programs them to flash.  the function that implements fpga config
> from flash also does not use the fpga load command which requires the
> entire fpga image be present in memory.  the fpga load calls and init for
> the fpga for each call, essentially restarting configuration.
>
> to do what you ask you would need to implement something like
> the cff_from_mmc_fat function
> in u-boot-socfpga/arch/arm/cpu/armv7/socfpga_arria10/cff.c
>
> Thanks,
> Dalon
>
> On Mon, Apr 4, 2016 at 5:02 PM, David Cemin <[email protected]>
> wrote:
>
>> Hi,
>>
>> On an arria10 SoC development kit, i would like to be able to configure
>> the fpga from an EXT partition instead of doing it from the FAT partition.
>>
>> So, i removed the call on the sdram.c that configures the fpga during
>> boot (function dram_init calls cff_from_mmc_fat) and tried to do:
>>
>>    - ext4load mmc 0:X $rbftosdramaddr <path to my rbf on ext3 partition)
>>
>> This doesnt work because at this point the ddr_calibration_sequence didnt
>> run yet so I cant actually use the external memory to put my image on.
>>
>> I tried manually calling the fpga loadfs and configure the fpga from the
>> FAT partition, and then have the memory ready. So, I load the my fpga image
>> into memory:
>>
>> ext4load mmc 0:2 0x400 /firmware/fpga_img.rbf
>>
>> Then I tried using the fpga load command to program it again:
>> fpga load 0 0x400 $filesize
>>
>> It gets stalled.
>>
>>
>> Not happy with it, because I thought it could be something weird on the
>> load program, i repeated the same thing the cff_from_mmc_fat does, but
>> using ext4_read instead of file_fat_read_at .. and it barfs giving me this
>> message:
>> ext4fs_devread read outside partition 4776
>>
>>
>> So, I thought I should separate that in smaller chunks, because this was
>> a problem on the ext4 read, and I get that it reads up to 3840 bytes, and
>> then it returns an error:
>> otal_read = 3584 Total: 31619884 fname /firmware/fpga_img.rbf temp
>> 00003840 bufptr 0 cs 64
>> bytesread: 64
>> total_read = 3648 Total: 31619884 fname /firmware/fpga_img.rbf temp
>> 00003940 bufptr 0 cs 64
>> bytesread: 64
>> total_read = 3712 Total: 31619884 fname /firmware/fpga_img.rbf temp
>> 00003a40 bufptr 0 cs 64
>> bytesread: 64
>> total_read = 3776 Total: 31619884 fname /firmware/fpga_img.rbf temp
>> 00003b40 bufptr 0 cs 64
>> bytesread: 64
>> total_read = 3840 Total: 31619884 fname /firmware/fpga_img.rbf temp
>> 00003c40 bufptr 0 cs 64
>> ** File not found /firmware/fpga_img.rbf **
>> read_rbf_header_from_ext: failed to read /firmware/fpga_img.rbf -1 != 64
>> cff_from_mmc_ext: error reading rbf header
>>
>>
>> *So, my question finally is*:
>> Does anybody know if it is possible to configure the fpga on arria10 dev
>> kit from an ext3 partition instead of from a FAT partition  ?
>>
>> Thank you
>>
>> Best regards,
>>
>> David
>>
>> --
>>
>> *+1 (343) 777-1735 <%2B1%20%28343%29%20777-1735>* David Cemin
>> http://coveloz.com
>>
>>
>> <http://coveloz.com/>
>>
>> _______________________________________________
>> Rfi mailing list
>> [email protected]
>> http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi
>>
>>
>


-- 

*+1 (343) 777-1735* David Cemin http://coveloz.com


<http://coveloz.com/>
_______________________________________________
Rfi mailing list
[email protected]
http://lists.rocketboards.org/cgi-bin/mailman/listinfo/rfi

Reply via email to