Activity
From 08/01/2018 to 08/30/2018
08/29/2018
- TR 11:06 PM Software Development: RE: Yocto MDK Status
- Hi, well it was easier then trying to fix the two repo failures, (which I will do)... just running bitbake again without the -k saw it succeed and now have the jffs image. Tom
- JC 10:04 PM Software Development: RE: Yocto MDK Status
- Tom Riddle wrote:
> Hi Jonathan,
> ... - TR 07:36 PM Software Development: RE: Yocto MDK Status
- Hi Jonathan,
We open a shell, go to yocto-archives dir, set the env
> source oe-init-build-env
then execute
> ...
to bypass the two repos that are not available. Please see the attached gzip file of the log. Let me know what...
08/28/2018
- JC 06:21 PM Software Development: RE: Yocto MDK Status
- Could you provide a log of your bitbake command plus output in an attached file?
- TR 06:10 PM Software Development: RE: Yocto MDK Status
- Hi Folks... any feedback on where the image might be? Thanks, Tom
- AB 03:18 PM PCB Development: RE: OMAP L138 HPI
- Unfortunately during my initial review of the modules with and without FPGA I confused the RESETOUT (T17) pin connection for the FPGA module.
As you have found T17 from the L138 is not connected to an FPGA IO but is connected to a ded... - HS 09:05 AM PCB Development: RE: OMAP L138 HPI
- Thank you.
I was able to check the connection information between FPGA and L138.
Could you tell me the pin wiring of ball T17(UHPI_HAS) of L138?
It seems necessary to connect to power supply(1.8V or 3.3V).
08/24/2018
- AB 11:12 PM PCB Development: RE: OMAP L138 HPI
- You can find the pin-out between the FPGA and the OMAP-L138 processor of the module in the Carrier Board Design Guide (Table 4):
https://www.criticallink.com/wp-content/uploads/2014/01/MityDSP-L138F-Carrier-Board-Design-Guide.pdf
P... - HS 01:53 AM PCB Development: RE: OMAP L138 HPI
- Thank you for your reply.
Sorry, I missed BALL R16, R17.
I found that a board with FPGA(MityDSP-L138F) is necessary.
Is there a way to know the connection information of L138 and the FPGA in the board(board schematic etc)? - TR 04:37 PM Software Development: RE: Yocto MDK Status
- Hi Bob, thanks for the quick response, I'll start playing with the recipe.
On the rootfs question, can't seem to find the file, see the dir listing below. Perhaps I need to build or execute something else? All I have done to date is
... - BD 04:19 PM Software Development: RE: Yocto MDK Status
- Tom Riddle wrote:
> Thanks Jonathan I will give that a try, in the meantime there are a few other questions.
> ...
Tom, if you have the Yocto build working, you can modify the kernel recipe in meta-mitydsp-l138 to point to your desired... - TR 03:59 PM Software Development: RE: Yocto MDK Status
- Thanks Jonathan I will give that a try, in the meantime there are a few other questions.
So we have a 3.2 kernel here with a moderate number of modifications that is based on the 2011 MDK kernel source. We can continue to build it sep...
08/23/2018
- AB 08:15 PM PCB Development: RE: OMAP L138 HPI
- I'm not sure that we've used the UHPI interface in any designs nor am I aware of any customers that have utilized the UHPI.
Are you interested in the MityDSP-L138 with or without the FPGA?
* For the module without the FPGA the UHPI... - I am looking for a board that can use HPI function of DSP of OMAP L138.
Is it possible to operate HPI using MityDSP-L138 and another HPI host MPU?
08/22/2018
- JC 08:22 PM Software Development: RE: Yocto MDK Status
- It looks like the vim repo has been moved. googlecode.com is no longer a valid url. Looking at more recent "vim recipes":https://git.congatec.com/yocto/meta-openembedded/blob/morty/meta-oe/recipes-support/vim/vim_8.0.0022.bb point to g...
- TR 06:44 PM Software Development: RE: Yocto MDK Status
- Hi, One last question... I built with "-k" to get past these two fetch errors,
Summary: 2 tasks failed:
/export/software/L138/yocto-archive/meta-openembedded/meta-oe/recipes-support/vim/vim_7.4.258.bb, do_fetch
/export/software... - TR 04:02 PM Software Development: RE: Yocto MDK Status
- Hi, thanks... suspected that was the case but didn't know where the setting was at. It successfully fetched and is moving on now.
- JC 03:33 PM Software Development: RE: Yocto MDK Status
- Thanks for the extra info. wanda.syr.criticallink.com is an internal server, CL_SOURCE_GIT_HOST should point to support.criticallink.com instead. Sorry about that.
08/21/2018
- TR 09:24 PM Software Development: RE: Yocto MDK Status
- Ok, Will try again... hope I can get an answer to the network question... it appears to fail at trying to fetch the following
Summary: 2 tasks failed:
/export/software/L138/yocto-archive/meta-mitydsp-l138/recipes-bsp/fpga-drivers/f...
08/18/2018
- TR 05:38 PM Software Development: RE: Yocto MDK Status
- Hi, So in the building of the yocto-archive it seems to get pretty far until these errors appear
ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: unable to connect to wanda.syr.critical...
08/15/2018
- YY 01:55 PM Software Development: RE: Change data between ARM & DSP cores, undefined behaviour
- Gregory Gluszek wrote:
> My guess is that the system is running out of DSPLink buffers. I would recommend checking return codes for functions such as GetBuffer(). GetBuffer() will return a NULL pointer if it cannot obtain a new buffer. ...
08/14/2018
- GG 02:59 PM Software Development: RE: Change data between ARM & DSP cores, undefined behaviour
- My guess is that the system is running out of DSPLink buffers. I would recommend checking return codes for functions such as GetBuffer(). GetBuffer() will return a NULL pointer if it cannot obtain a new buffer.
Thanks,
\Greg - YY 04:35 AM Software Development: RE: Change data between ARM & DSP cores, undefined behaviour
- After N-iterations I get an errors:
08/13/2018
- JC 07:07 PM Software Development: RE: Change data between ARM & DSP cores, undefined behaviour
- > They often fail. How to fix it?
Could you clarify what you mean about it failing often? Error messages? What does failure mean? - Hello!
I have MityDSP OMAPL-138F, version linux kernel - 3.2, version dsplink 1.65 (from MDK-2012-03-2012), pc Ubuntu-14.04.05 LTS. ARM & DSP clock freq - 300MHz.
I want to establish a continuous exchange of data between two cores ...
08/10/2018
- AK 08:00 PM Software Development: RE: Yocto MDK Status
- The yocto-archive contains all of the necessary files to build the MDK (with the exception of the missing file).
I'm working on adding the @.templateconf@ to the archive for future releases. In the mean time, the contents of the file ... - TR 02:52 AM Software Development: RE: Yocto MDK Status
- Thanks, Aidan. that's helpful. I still had a number of errors, but they may be related to other items here that are not setup properly.
So I'd like to ask a few general setup questions, following the general yocto install instruction... - TR 05:21 PM Software Development: RE: Building DspHelloWorld MDK 2018
- Greg, thanks... So the other option (assuming untested) would be to rebuild DSPlink libs with the XDC Tools version on the CCS v7.3? regs, Tom
- GG 03:17 PM Software Development: RE: Building DspHelloWorld MDK 2018
- Hi Tom,
I believe the DSP MDK core library you are linking against was built with Code Composer 6.1. I would recommend using CCS v6.1 to build the DSP Hello World application.
Thanks,
\Greg - Hi,
I'm setting up a native Ubuntu 16.04 hosted machine for the MDK 2018. CCS v7.3 is installed with the recommended tools and have followed these instructions.
https://support.criticallink.com/redmine/projects/arm9-platforms/wiki/...
08/09/2018
- AK 01:07 PM Software Development: RE: Yocto MDK Status
- Hi Tom,
From your error message it looks like @CL_SOURCE_GIT_HOST@ and @CL_SOURCE_GIT_PATH@ aren't defined. These variables are defined in Critical Link's Yocto distro, @cl-systemd@.
Since you're building for the MityDSP-L138 you s... - TR 02:18 AM Software Development: RE: Yocto MDK Status
- I have successfully built Yocto core, however when I try to build meta-criticallink I get the following error. Any help would be appreciated.
======
rurisond@skyskip-minidell:/export/software/mitydsp/sources/poky/yocto-archive$ bitba...
08/08/2018
- TR 01:20 AM Software Development: RE: Yocto MDK Status
- Following up here... I basically had to update the CC assignment in the Makefile so it could find --sysroot, now it builds correctly. Are these Makefile mods expected or have I missed an MDK setup step somewhere? Please advise, thanks
08/07/2018
- TR 05:34 PM Software Development: RE: Yocto MDK Status
- Hi,
I pulled over my kernel sources and it builds. Next I am attempting to build some of the 2018 MDK examples. Running into things like ${MDK} was not set, path issues, etc. So beyond installing the MDK and sourcing this file (below)... - GG 02:54 PM Software Development: RE: Yocto MDK Status
- Hi Tom,
The 3.2 branch you are following is the one to track for our latest updates for the L138 platform.
Thanks,
\Greg - TR 05:15 AM Software Development: RE: Yocto MDK Status
- Hi,
So I've been using the following kernel and have a number of changes.
On branch mitydsp-linux-v3.2
According to the git log this was the last commit
commit ce5d9bb2f9a2405a6321e3603e0c5dcaf9f47d6b
Author: Gregory Glusz...
08/02/2018
- JC 01:38 PM Software Development: RE: Yocto MDK Status
- It was built on Ubuntu 16.04
- TR 12:05 AM Software Development: RE: Yocto MDK Status
- Hi Bob, Thanks, BTW, what version of Ubuntu are you hosting the 2018.04 Yocto-based MDK on? Regs, Tom
08/01/2018
- BD 01:54 PM Software Development: RE: Yocto MDK Status
- Hi Tom,
We've released some Yocto-based MDKs under the "Files":https://support.criticallink.com/redmine/projects/arm9-platforms/files tab. The latest is 2018.04. We don't have full documentation for creating your own Yocto-based MDK ... - Ok, looks like it may be the appropriate time for us here to cut over to the Yocto MDK. We've been on the MDK_2014-01-13 but the filesystem limitations are starting to hold us back. We've done a significant amount of kernel work integrat...