Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working about ckws2812

[LariSan]

No help here except to commiserate- I also ran into that problem for the
neopixel ring (9 LEDs) but instead of trying to figure it out I switched to
use the PICxel library.
http://marshallstechblog.wordpress.com/2014/07/03/the-picxel-library/

On Sunday, November 23, 2014, Brian Schmalz [email protected]
wrote:

It turns out that if you have CDEVICES set less than 14 then updateLEDs()
will never return true.

To test this out, take LBling example and set CDEVICES to 13 (and comment
out an appropriate number of initializes in rgGRB[]) and run. No LED data
will be output and the state will be stuck in LOADPAT forever.

Interestingly this is not as simple as it seams. You CAN use CDEVICES <
14, but the cDevices parameter to the begin() call must be less than the
cbPatternBuffer parameter (not equal, as they normally are). Why 14 is the
magic number where these things can be equal, I have no idea.

For example, if CDEVICES = 4,
ws2812.begin(3, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will work but
ws2812.begin(4, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will not work.

I have tried parsing the code to figure out why this happens, but I
haven't figure out exactly how the DMA an pattern buffers work yet, so I
can't see the forest for the trees at this point.

*Brian

—
Reply to this email directly or view it on GitHub
#1.

-Larissa
952.250.3891

[KeithV]

Dang… this is why I sometime hate contributed code that is done on a weekend; then you have to support it L

When I get a chance I will take a look and try to see what the deal is. Off of the top of my head… I don’t know why 14 would have any significates.

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Sunday, November 23, 2014 2:42 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

It turns out that if you have CDEVICES set less than 14 then updateLEDs() will never return true.

To test this out, take LBling example and set CDEVICES to 13 (and comment out an appropriate number of initializes in rgGRB[]) and run. No LED data will be output and the state will be stuck in LOADPAT forever.

Interestingly this is not as simple as it seams. You CAN use CDEVICES < 14, but the cDevices parameter to the begin() call must be less than the cbPatternBuffer parameter (not equal, as they normally are). Why 14 is the magic number where these things can be equal, I have no idea.

For example, if CDEVICES = 4,
ws2812.begin(3, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will work but
ws2812.begin(4, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will not work.

I have tried parsing the code to figure out why this happens, but I haven't figure out exactly how the DMA an pattern buffers work yet, so I can't see the forest for the trees at this point.

*Brian

—
Reply to this email directly or view it on GitHub #1 . https://github.com/notifications/beacon/AA8RTpsgexxCDyIkMJxIUIvxdER0t9D1ks5nQlpHgaJpZM4C_poj.gif

[LariSan]

KeithV--

chipKIT needed WS2812 libraries-- ESP for christmas!
However... it could be Karma for naming it after me ;-) , or purveyors of
"Bling" are generally high maintenance in nature. Luckily, Digilent's LED
strips come in strips of 30.

It's a weird glitch I would be interested to find out what is causing it,
but I was able to use the PICxel library for small and uncomplicated
patterns, so it wasn't a show stopper.

On Sun, Nov 23, 2014 at 7:49 PM, KeithV [email protected] wrote:

Dang… this is why I sometime hate contributed code that is done on a
weekend; then you have to support it L

When I get a chance I will take a look and try to see what the deal is.
Off of the top of my head… I don’t know why 14 would have any significates.

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Sunday, November 23, 2014 2:42 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small
numbers of LEDs from working (#1)

It turns out that if you have CDEVICES set less than 14 then updateLEDs()
will never return true.

To test this out, take LBling example and set CDEVICES to 13 (and comment
out an appropriate number of initializes in rgGRB[]) and run. No LED data
will be output and the state will be stuck in LOADPAT forever.

Interestingly this is not as simple as it seams. You CAN use CDEVICES <
14, but the cDevices parameter to the begin() call must be less than the
cbPatternBuffer parameter (not equal, as they normally are). Why 14 is the
magic number where these things can be equal, I have no idea.

For example, if CDEVICES = 4,
ws2812.begin(3, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will work but
ws2812.begin(4, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will not work.

I have tried parsing the code to figure out why this happens, but I
haven't figure out exactly how the DMA an pattern buffers work yet, so I
can't see the forest for the trees at this point.

*Brian

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1> . <
https://github.com/notifications/beacon/AA8RTpsgexxCDyIkMJxIUIvxdER0t9D1ks5nQlpHgaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

-Larissa
952.250.3891

[KeithV]

It should just work…. I will look at it.

KeithV

From: Larissa Swanland [mailto:[email protected]]
Sent: Sunday, November 23, 2014 9:37 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

KeithV--

chipKIT needed WS2812 libraries-- ESP for christmas!
However... it could be Karma for naming it after me ;-) , or purveyors of
"Bling" are generally high maintenance in nature. Luckily, Digilent's LED
strips come in strips of 30.

It's a weird glitch I would be interested to find out what is causing it,
but I was able to use the PICxel library for small and uncomplicated
patterns, so it wasn't a show stopper.

On Sun, Nov 23, 2014 at 7:49 PM, KeithV [email protected] wrote:

Dang… this is why I sometime hate contributed code that is done on a
weekend; then you have to support it L

When I get a chance I will take a look and try to see what the deal is.
Off of the top of my head… I don’t know why 14 would have any significates.

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Sunday, November 23, 2014 2:42 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small
numbers of LEDs from working (#1)

It turns out that if you have CDEVICES set less than 14 then updateLEDs()
will never return true.

To test this out, take LBling example and set CDEVICES to 13 (and comment
out an appropriate number of initializes in rgGRB[]) and run. No LED data
will be output and the state will be stuck in LOADPAT forever.

Interestingly this is not as simple as it seams. You CAN use CDEVICES <
14, but the cDevices parameter to the begin() call must be less than the
cbPatternBuffer parameter (not equal, as they normally are). Why 14 is the
magic number where these things can be equal, I have no idea.

For example, if CDEVICES = 4,
ws2812.begin(3, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will work but
ws2812.begin(4, rgbPatternBuffer, sizeof(rgbPatternBuffer), false)
will not work.

I have tried parsing the code to figure out why this happens, but I
haven't figure out exactly how the DMA an pattern buffers work yet, so I
can't see the forest for the trees at this point.

*Brian

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1> . <
https://github.com/notifications/beacon/AA8RTpsgexxCDyIkMJxIUIvxdER0t9D1ks5nQlpHgaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

-Larissa
952.250.3891

—
Reply to this email directly or view it on GitHub #1 (comment) .Image removed by sender.

[KeithV]

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down to CDEVICES == 3 and it just works for me. I do not have an SD, so I couldn't check that.

[EmbeddedMan]

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

[KeithV]

Hi Brian,

I actually downloaded the .zip file from github, it works fine for the WF32 and MAX32

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif

[EmbeddedMan]

Keith, good thinking! OK, I'll try it on some of my other boards and see if
I can't figure out the problem.

*Brian

On Wed, Nov 26, 2014 at 9:44 PM, KeithV [email protected] wrote:

Hi Brian,

I actually downloaded the .zip file from github, it works fine for the
WF32 and MAX32

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <
https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

[KeithV]

Well I found one problem with the GitHub version…..

The blinking LED in the loop is on LED1, that is a bad LED to use as that is PIN 13 which is also the SCK for the SPI… do not use LED1 on any UNO form factor board as that will hose up SCK.

This will not affect the MAX32, but will the WF32 and may affect the SD, don’t know. But… I think Rick changed this to LED1.

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 8:45 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith, good thinking! OK, I'll try it on some of my other boards and see if
I can't figure out the problem.

*Brian

On Wed, Nov 26, 2014 at 9:44 PM, KeithV [email protected] wrote:

Hi Brian,

I actually downloaded the .zip file from github, it works fine for the
WF32 and MAX32

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <
https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTnyLFEsUHghWe9Di-bxptOYt4tFkks5nRqPdgaJpZM4C_poj.gif

[KeithV]

Sorry Brian,

The only SDs I have here are you MX4 variations. So I can’t try and debug what is wrong with the 1.5 SD; as the spi controller is not fully supported on the MX4.

Ah, I noticed really high PIN numbers for the SPI in the variant file….???

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 8:45 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith, good thinking! OK, I'll try it on some of my other boards and see if
I can't figure out the problem.

*Brian

On Wed, Nov 26, 2014 at 9:44 PM, KeithV [email protected] wrote:

Hi Brian,

I actually downloaded the .zip file from github, it works fine for the
WF32 and MAX32

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <
https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTnyLFEsUHghWe9Di-bxptOYt4tFkks5nRqPdgaJpZM4C_poj.gif

[KeithV]

Brian,

Oddly enough though… I do have one of your SDMZ, not sure how I got that… you must have sent me one.

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 8:45 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith, good thinking! OK, I'll try it on some of my other boards and see if
I can't figure out the problem.

*Brian

On Wed, Nov 26, 2014 at 9:44 PM, KeithV [email protected] wrote:

Hi Brian,

I actually downloaded the .zip file from github, it works fine for the
WF32 and MAX32

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <
https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTnyLFEsUHghWe9Di-bxptOYt4tFkks5nRqPdgaJpZM4C_poj.gif

[KeithV]

Like I said, it looks like Rick put everything to LED1 and that will create a conflict with SCK on Uno style type form factor boards like the WF32.

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif

[KeithV]

Hi Brian,

I fixed up the project to work with the Mini (dev) and got it to work with CDEVICES == 13. However I did NOT do any mapping of the SPI pins, so I am just running the controller without mapping anything out to the pins. But I do get past LOADPAT. I had to fix up the DMA controller priority… I bet you just commented out the priority level for the MX250 and thus the DMA had zero priority and never ran. Not sure how it would work for more than 14 devices though. Anyway look at the attached project… but remember you must add pps mappings to the SPI, and make sure the LED does not conflict (I just removed the LED).

I used the latest build of MPIDE.

Good Luck

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif

[EmbeddedMan]

Keith,

Thanks, I'll take a look at the changes you made.

Important note: all of my work was done on a Fubarino Mini, not a Fubarino
SD. You mentioned that you didn't have a MX795 version of the Fubarino SD -
but that doesn't really matter for these tests, as the Mini is what I was
having trouble with.

I'll let you know what I find-

*Brian

On Thu, Nov 27, 2014 at 12:28 AM, KeithV [email protected] wrote:

Hi Brian,

I fixed up the project to work with the Mini (dev) and got it to work with
CDEVICES == 13. However I did NOT do any mapping of the SPI pins, so I am
just running the controller without mapping anything out to the pins. But I
do get past LOADPAT. I had to fix up the DMA controller priority… I bet you
just commented out the priority level for the MX250 and thus the DMA had
zero priority and never ran. Not sure how it would work for more than 14
devices though. Anyway look at the attached project… but remember you must
add pps mappings to the SPI, and make sure the LED does not conflict (I
just removed the LED).

I used the latest build of MPIDE.

Good Luck

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <
https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

[KeithV]

Thanks Brian,

I saw in the GitHub version that Rick put the Furburino SD in there and it did not compile for me because the MX4 does not support the SPI features, so I assumed Rick put it in there for the MX7 version. Then I read your mail and realized it was the MX250 you had the problems with; so I got an old dev Mini, but I didn’t want to fool with the 50MHz bootloader, so I just checked it out at 40MHz. I don’t think that will make a difference…. But who knows?

Hope you had a great Thanksgiving!

Keith

From: Brian Schmalz [mailto:[email protected]]
Sent: Thursday, November 27, 2014 6:56 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents small numbers of LEDs from working (#1)

Keith,

Thanks, I'll take a look at the changes you made.

Important note: all of my work was done on a Fubarino Mini, not a Fubarino
SD. You mentioned that you didn't have a MX795 version of the Fubarino SD -
but that doesn't really matter for these tests, as the Mini is what I was
having trouble with.

I'll let you know what I find-

*Brian

On Thu, Nov 27, 2014 at 12:28 AM, KeithV [email protected] wrote:

Hi Brian,

I fixed up the project to work with the Mini (dev) and got it to work with
CDEVICES == 13. However I did NOT do any mapping of the SPI pins, so I am
just running the controller without mapping anything out to the pins. But I
do get past LOADPAT. I had to fix up the DMA controller priority… I bet you
just commented out the priority level for the MX250 and thus the DMA had
zero priority and never ran. Not sure how it would work for more than 14
devices though. Anyway look at the attached project… but remember you must
add pps mappings to the SPI, and make sure the LED does not conflict (I
just removed the LED).

I used the latest build of MPIDE.

Good Luck

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected] wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <
https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub #1 (comment) . https://github.com/notifications/beacon/AA8RTmE0O6bO6gv5aniWaWlsiTpzob-Gks5nR9urgaJpZM4C_poj.gif

[ricklon]

Happy Thanks Giving.

Just trying to catch up to this. I think I just added stuff so it would
compile for FubarinoSD. I did have it working, but I'm not sure for numbers
less than 16. I can try Saturday and see what happens.

-_Rick

On Fri, Nov 28, 2014 at 1:21 AM, KeithV [email protected] wrote:

Thanks Brian,

I saw in the GitHub version that Rick put the Furburino SD in there and it
did not compile for me because the MX4 does not support the SPI features,
so I assumed Rick put it in there for the MX7 version. Then I read your
mail and realized it was the MX250 you had the problems with; so I got an
old dev Mini, but I didn’t want to fool with the 50MHz bootloader, so I
just checked it out at 40MHz. I don’t think that will make a difference….
But who knows?

Hope you had a great Thanksgiving!

Keith

From: Brian Schmalz [mailto:[email protected]]
Sent: Thursday, November 27, 2014 6:56 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Thanks, I'll take a look at the changes you made.

Important note: all of my work was done on a Fubarino Mini, not a Fubarino

SD. You mentioned that you didn't have a MX795 version of the Fubarino SD

but that doesn't really matter for these tests, as the Mini is what I was
having trouble with.

I'll let you know what I find-

*Brian

On Thu, Nov 27, 2014 at 12:28 AM, KeithV [email protected]
wrote:

Hi Brian,

I fixed up the project to work with the Mini (dev) and got it to work
with
CDEVICES == 13. However I did NOT do any mapping of the SPI pins, so I
am
just running the controller without mapping anything out to the pins.
But I
do get past LOADPAT. I had to fix up the DMA controller priority… I bet
you
just commented out the priority level for the MX250 and thus the DMA had
zero priority and never ran. Not sure how it would work for more than 14
devices though. Anyway look at the attached project… but remember you
must
add pps mappings to the SPI, and make sure the LED does not conflict (I
just removed the LED).

I used the latest build of MPIDE.

Good Luck

KeithV

From: Brian Schmalz [mailto:[email protected]]
Sent: Wednesday, November 26, 2014 2:40 PM
To: ricklon/ckWS2812
Cc: KeithV
Subject: Re: [ckWS2812] Crash with < 14 LEDs (CDEVICES value) prevents
small numbers of LEDs from working (#1)

Keith,

Drat. That may mean that it's something about the MX250's DMA that's
different. Hmm.

Can you confirm that the latest files in Gihub are the versions that you
sent Rick? It looks like the only changes to the files have been from
Rick.

*Brian

On Wed, Nov 26, 2014 at 4:25 PM, KeithV [email protected]
wrote:

I tried this on both a WF32 and MAX32 exactly as Brian suggests and
down
to CDEVICES == 3 and it just works for me. I do not have an SD, so I
couldn't check that.

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64721094> . <

https://github.com/notifications/beacon/AA8RTnLzcD1CDlS7ZcXOQbw04jn-PfGFks5nRk41gaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

—
Reply to this email directly or view it on GitHub <
https://github.com/ricklon/ckWS2812/issues/1#issuecomment-64847861> . <
https://github.com/notifications/beacon/AA8RTmE0O6bO6gv5aniWaWlsiTpzob-Gks5nR9urgaJpZM4C_poj.gif>

—
Reply to this email directly or view it on GitHub
#1 (comment).

Co-founder
Fair Use Building and Research (FUBAR) Labs
http://fubarlabs.org