Activity
From 06/12/2016 to 07/11/2016
07/11/2016
- 05:06 PM Software Development: RE: L138 dsplink problem - schedule while atomic bug
- I looked deeper into the error we were provoking on our bench; it turned out to be a c++ vector de-referencing error ...
07/09/2016
- 06:24 PM Software Development: RE: SPI1 controller, access to FLASH and carrier board. NOT linux based.
- Ian St. John wrote:
> Can you confirm that the signal marked as 'reserved' just beside the SPI1_CSC1 is the SPI1_CSC... - 05:56 PM Software Development: RE: SPI1 controller, access to FLASH and carrier board. NOT linux based.
- Hmm. I asked the EE about the diagram and he was interested in the fact that there was a pull up on the CS line. Appa...
- 12:40 AM Software Development: RE: SPI1 controller, access to FLASH and carrier board. NOT linux based.
- The eeprom is on the i2c0 bus. I'm assuming you are talking about the SPI Nor flash which is on SPI1_CS0.+
Oops... - 01:23 PM Software Development: RE: L138 dsplink problem - schedule while atomic bug
- Hi Fred,
Syslink is newer than DSPlink, though in the context of the L138 it's very similar code (syslink evolved ... - 12:11 PM Software Development: RE: L138 dsplink problem - schedule while atomic bug
- The error collected above was on the bench after making some minor software changes seemingly unrelated with the code...
- 11:23 AM Software Development: RE: L138 dsplink problem - schedule while atomic bug
- I found the following on the TI site; looks like they struggled with this issue with sys-link... I'm not sure how sys...
07/08/2016
- I think there may be a bug in the dsplink kernel code that causes the scheduler to run after a call to spinlock. "rem...
- 09:33 AM Software Development: RE: SPI1 controller, access to FLASH and carrier board. NOT linux based.
- Ian St. John wrote:
> I am building and programming a custom board without Linux. Basic embedded drivers running fro...
07/05/2016
- I am building and programming a custom board without Linux. Basic embedded drivers running from SPI1,CS0 (8MB NOR Fla...
06/22/2016
- 04:13 AM Software Development: RE: kernel 3.2 - tcpip stack latency
- Hi Greg,
Than you for your feedback.
Indeed, flag CONFIG_PREEMPT is set in kernel config. As far as we can see...
06/21/2016
- 01:30 PM Software Development: RE: kernel 3.2 - tcpip stack latency
- Hi Patrice,
Since you are using SCHED_RR I am assuming you are using CONFIG_PREEMPT in your kernel config, correc... - Hello,
We've built an application receiving messages from two devices at a rate of 1 message of 1440 bytes every 1...
06/17/2016
- 08:25 AM Software Development: RE: Flashing a new kernel to NOR from Linux rather than u-boot
- Here are the results from my board/MDK:...
06/16/2016
- 05:43 PM Software Development: RE: Flashing a new kernel to NOR from Linux rather than u-boot
- Alternatively it may be possible for you to build the kernel features as modules and insert them in the live system. ...
- 05:39 PM Software Development: RE: Flashing a new kernel to NOR from Linux rather than u-boot
- Fred,
Do you have /dev/mtdblock* devices? My kernel boot args have this "root=/dev/mtdblock0", so my assumption i... - We use opkg to push updates to our products that are installed in the field. We now need a way to update the kernel, ...
06/15/2016
- 05:14 PM Software Development: RE: How to configure the GPIOs as outputs?
- Do note that the custom baseboard instructions were written for the 335x family. So some things will be slightly diff...
- 04:14 PM Software Development: RE: How to configure the GPIOs as outputs?
- Héctor,
Please check the last section of this page for information on how to review and set the pinmux for the dev... - Hi, it's me again,
I'm knowing the Profibus Development Kit (and embedded systems) and for that I'm trying to do s... - 11:00 AM Software Development: RE: Problems with the first time configuration
- Now it's working, thanks a lot Jonathan!
- 10:02 AM Software Development: RE: Problems with the first time configuration
- Hector Bojorquez wrote:
> > This is a error is normal and doesn't hurt anything.
> *
> So, the reflashing process ... - 09:55 AM Software Development: RE: Problems with the first time configuration
- > This is a error is normal and doesn't hurt anything.
*
So, the reflashing process went well?*
> If you don't h... - 08:38 AM Software Development: RE: Problems with the first time configuration
- Hector Bojorquez wrote:
> >There shouldn't be a space in the console arg. "console=ttyS1,115200n8"
> >Also root sh...
06/14/2016
- 05:45 PM Software Development: RE: Problems with the first time configuration
- >There shouldn't be a space in the console arg. "console=ttyS1,115200n8"
>Also root should have an '=' not a '-'.
... - 03:35 PM Software Development: RE: Problems with the first time configuration
- Hector Bojorquez wrote:
> Hi Jonathan,
>
> I made the changes, and yes the problem continues the same, I checked ... - 02:56 PM Software Development: RE: Problems with the first time configuration
- Hi Jonathan,
I made the changes, and yes the problem continues the same, I checked the bootargs and this was the r... - 01:20 PM Software Development: RE: Problems with the first time configuration
- Thanks for all the logs, definitely helpful. The kernel panic indicates that it failed to find the filesystem. See be...
- 12:50 PM Software Development: RE: Problems with the first time configuration
- Hi,
I followed the steps in the [[Reprogramming_a_Dead_Board]] guide and I got access to the u-boot prompt again, ... - 05:15 PM Software Development: RE: Specifics on reserving DDR for PRU/ARM shared use
- Regarding your specific questions, yes, you could use memmap to set aside a particular chunk of memory. Where you set...
- 05:07 PM Software Development: RE: Specifics on reserving DDR for PRU/ARM shared use
- Hi Andrew,
I recommend you review the TI-provided documentation and examples for the PRU available here:
<https...
06/13/2016
- 05:14 PM Software Development: RE: JFFS2 "scheduling while atomic" problem with L138 running linux kernel 3.2
- Sorry I missed that Fred.
You can just make the change (swapping two lines) yourself for testing, or you can appl... - 05:12 PM Software Development: RE: JFFS2 "scheduling while atomic" problem with L138 running linux kernel 3.2
- Note we can list any other jffs patches that is in the linux-3.2.y branch that isn't in ours by doing the following:
... - 05:07 PM Software Development: RE: JFFS2 "scheduling while atomic" problem with L138 running linux kernel 3.2
- The patch was included in the 3.2.18 kernel release. You can cherry-pick the patch from there to verify it fixes you...
- 04:56 PM Software Development: RE: JFFS2 "scheduling while atomic" problem with L138 running linux kernel 3.2
- Looks like someone already did the backport of the fix. The patch is very straight forward.
https://github.com/Angs... - 04:28 PM Software Development: RE: JFFS2 "scheduling while atomic" problem with L138 running linux kernel 3.2
- Ah, yes, so this is indeed the problem; the code you show above is _before_ the fix. The issue is mutex_lock cannot f...
- 02:48 PM Software Development: RE: JFFS2 "scheduling while atomic" problem with L138 running linux kernel 3.2
- Fred,
The current MityDSP-L138 kernel (Branch: mitydsp-linux-v3.2) has the following code in @fs/jffs2/gc.c@:
... - I have been getting a lot of "scheduling while atomic" messages seemingly centered around JFFS2:
@Jun 12 12:08:37 ...
Also available in: Atom
Go to top
