Oleg:
Stuff in build/tmp/deploy/images/elphel393 looks good.
Yocto looks promising for MicroZed work...

I noticed a "create_img_iso.py" script in elphel-tools-update.
How is this used with the build stuff to get a sdimage.iso?
How does the BOOT_FILE_LIST files link to the build output?

thanks,
Frank Bennett

On 03/31/2017 11:25 AM, Oleg wrote:
Hi,

I forgot:
$ bitbake linux-xlnx -c link -f
$ bitbake linux-xlnx

I don't think it is described anywhere at the moment:
./linux-elphel/src/drivers/elphel/x393.h
this file (and all the others from our tree) gets linked to the kernel source by an extra task added to the kernel recipe (in elphel393_fixold/meta/meta-elphel393/recipes-kernel/linux/linux-xlnx_4.0.bbappend) -
addtask do_link before do_kernel_configme after do_patch
which is before do_compile where bitbake stopped.

What happened:
* python-numpy was missing
* scripts failed to generate x393.h and it wasn't linked to the source
* bitbake was up to do_compile task, so 'bitbake linux-xlnx' would not get back to do_link.

Best regards,
Oleg Dzhimiev
Electronics Engineer
phone: +1 801 783 5555 x124
Elphel, Inc.

On 31 March 2017 at 09:24, Frank Bennett <bennet...@centurylink.net> wrote:
Oleg:
Got python-numpy
reviewed poky manual
rm projects.json
./setup.py
still no x393.h in poky/build path only in:
fwb@fw:/s/opt/elphel/elphel393$ find . -name x393.h
./fpga-elphel/x393/py393/generated/x393.h
./linux-elphel/src/drivers/elphel/x393.h
only mention in setup output:
...
X393SensCmprs: BUFFER_ADDRESS=0x25500000
X393SensCmprs: BUFFER_LEN=0x19000000
Running in simulated mode, using hard-coded addresses:
BUFFER_ADDRESS_LOGGER=0x2d000000
BUFFER_LEN_LOGGER=0x400000
Running task: ['export_all']
typedef definitions for the x393 hardware registers are written to  to /s/opt/elphel/elphel393/fpga-elphel/x393/py393/generated/x393_types.h
Constants definitions and functions declarations to access x393 hardware registers are written to  to /s/opt/elphel/elphel393/fpga-elphel/x393/py393/generated/x393.h
Functions definitions to access x393 hardware registers are written to  to /s/opt/elphel/elphel393/fpga-elphel/x393/py393/generated/x393.c
Constants and hardware addresses definitions to access x393 hardware registers are written to  to /s/opt/elphel/elphel393/fpga-elphel/x393/py393/generated/x393_defs.h
Sorted hardware addresses map is written to  to /s/opt/elphel/elphel393/fpga-elphel/x393/py393/generated/x393_map.h
    Result: OK




_______________________________________________
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com
 

_______________________________________________
Support-list mailing list
Support-list@support.elphel.com
http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com

Reply via email to