Activity
From 06/11/2016 to 07/10/2016
07/09/2016
- JC 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_CSC0 and would that show the chip select operation from reading the flash? It seems a good inference but it is speculative ... - IS 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. Apparently, none of our documents state that the SPI1_SCS[1] is "open drain".
We have
"am1808 tech ref (spruh82a)".pdf... - IS 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. Sorry, I said eeprom when I meant the 8MB flash. The JEDEC result is from FLASH, so ok. I modified the code to do the ... - MW 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 from DSPlink).
I am curious about the "sudden" appearance of the error following a power cycle on your fielded unit. ... - FW 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 that accesses dsp-link; the one below was just found in the field. The field device was in operation for 2 months with ...
- FW 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-link is related to dsp-link (newer, older, ?)...
[[https://e2e.ti.com/support/embedded/tirtos/f/355/t/385081]]
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. "remove_wait_queue" seems to be in atomic code, and anything that can cause a call to the scheduler is not allowed after a s...
- JC 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 from SPI1,CS0 (8MB NOR Flash).
> ...
The eeprom is on the i2c0 bus. I'm assuming you are talking about the SPI Nor flash...
07/05/2016
- I am building and programming a custom board without Linux. Basic embedded drivers running from SPI1,CS0 (8MB NOR Flash).
CCS version 6.1.3, compiler TI 15.15.1 LTS, custom carrier board with 1808-FX-225-RC (MityARM 1808) SOM.
I can ...
06/22/2016
- PB 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, there is no issue on the thread itself.
We use VLAN tag to route the traffic specifically from the devices to our c...
06/21/2016
- GG 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, correct?
Does your design have any sort of network traffic shaping or advanced traffic control in place? I do not think an... - Hello,
We've built an application receiving messages from two devices at a rate of 1 message of 1440 bytes every 10 ms in a thread schedule in SCHED_RR priority 70. This is the higher priority user thread in the system.
A network tra...
06/17/2016
- FW 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
- JC 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. Would like to see the output of the commands mentioned above first.
- JC 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 is that you will need to have the mtdblocks enabled inorder to boot from nand.
If you do have the mtdblock devices it ... - We use opkg to push updates to our products that are installed in the field. We now need a way to update the kernel, which is saved in NOR on the MityDSP-l138 som. A search of the CL wiki shows:
@flashcp -v uImage /dev/mtd7@
We hav...
06/15/2016
- JC 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 different. For example:
Instead of @arch/arm/mach-omap2/@ you should look in @arch/arm/mach-davinci@ for the board (boar... - BD 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 development board:
https://support.criticallink.com/redmine/projects/armc8-platforms/wiki/Creating_a_custom_baseboard
... - Hi, it's me again,
I'm knowing the Profibus Development Kit (and embedded systems) and for that I'm trying to do simple codes in C++ in Eclipse,
I was checking the datasheet about the connector pin assignments and the signals names... - HB 11:00 AM Software Development: RE: Problems with the first time configuration
- Now it's working, thanks a lot Jonathan!
- JC 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.
> ...
These settings only affect u-boot. You need to configure the ip settings after booting into linux.
> U-Boot > print bootargs
> ...
https://suppor... - HB 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?*
> ...
I tried with this [[Setting_a_Static_IP_Address#NFS-Mounted-File-System]]
@U-Boot > print bootargs
bootargs=mem=96M console=tt... - JC 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"
> ...
This is a error is normal and doesn't hurt anything.
>
> ...
If you don't have a dhcp server then you will need to set your ip...
06/14/2016
- HB 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"
> ...
sorry about that, I was watching from the other PC and typing in the one with Network connection for making the post, but in the bootlog is OK,
>There sh... - JC 03:35 PM Software Development: RE: Problems with the first time configuration
- Hector Bojorquez wrote:
> Hi Jonathan,
> ...
There shouldn't be a space in the console arg. "console=ttyS1,115200n8"
Also root should have an '=' not a '-'.
From attachment:UpdatingDevKitMDK.txt
> U-Boot > setenv bootcmd "runflas... - HB 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 result:
@U-Boot > print bootargs
bootargs=mem=96M console=ttyS1, 115200n8 root-/dev/mtdblock0 rw rootwait@
>If t... - JC 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 below.
- HB 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, so I tried again with the [[Updating_devkit_to_latest_MDK]] tutorial
I left attached the bootlog, after that I tried ... - BD 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 it up depends on the amount of memory in your module and I expect you could access it from base SDRAM address @0x8000_0...
- BD 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://github.com/beagleboard/am335x_pru_package>
This documentation is compatible with the PRU Module for the 3.2 kernel...
06/13/2016
- BD 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 apply the commit via Jon's instruction.
If that fixes your problem, we can push it to our main branch.
- JC 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:
- JC 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 your issue.
- JC 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/Angstrom-distribution/meta-ti/blob/master/recipes-kernel/linux/linux-ti33x-psp-3.2/3.2.18/0027-jffs2-Fix-lock-acquisition-or... - FW 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 follow spin_lock. Spin_lock places the kernel into atomic mode; during this mode, the processor must not call scheduler, ...
- BD 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 ultrasonic kernel: BUG: scheduling while atomic: flash-writer/2221/0x00000002
Jun 12 12:08:37 ultrasonic kernel: Module...