Hi Dan,
You are probably right about the code being "optimised" away, it would certainly explain things.
The overlap with CS0 was definitely the root cause of the problem.
The processor's reference manual, logically, does not mention CS0 being used on the netburner board and I did not find it ...
Search found 40 matches
- Sun Dec 15, 2013 11:23 pm
- Forum: NetBurner Software
- Topic: software triggered eDMA does not start
- Replies: 8
- Views: 8332
- Fri Dec 13, 2013 5:16 am
- Forum: NetBurner Software
- Topic: software triggered eDMA does not start
- Replies: 8
- Views: 8332
Re: software triggered eDMA does not start
Update: changed the start addresses as follows to avoid overlap with FB_CS0 address range
#define FB_CS1_BASE 0x02000000; // CS_1 base address
#define AD1reading *(DWORD*) FB_CS1_BASE
#define FB_CS4_BASE 0x02010000; // CS_4 base address
#define AD2reading *(DWORD*) FB_CS4_BASE
Result: dead as a ...
#define FB_CS1_BASE 0x02000000; // CS_1 base address
#define AD1reading *(DWORD*) FB_CS1_BASE
#define FB_CS4_BASE 0x02010000; // CS_4 base address
#define AD2reading *(DWORD*) FB_CS4_BASE
Result: dead as a ...
- Fri Dec 13, 2013 2:11 am
- Forum: NetBurner Software
- Topic: software triggered eDMA does not start
- Replies: 8
- Views: 8332
Re: software triggered eDMA does not start
OK, here are the various sections dealing with edma setup and use.
I have checked thoroughly that all sections get called in the right order.
First: some defines used in the code below
#define FB_CS1_BASE 0x01000000; // CS_1 base address
#define AD1reading *(DWORD*) FB_CS1_BASE
#define FB_CS4_BASE ...
I have checked thoroughly that all sections get called in the right order.
First: some defines used in the code below
#define FB_CS1_BASE 0x01000000; // CS_1 base address
#define AD1reading *(DWORD*) FB_CS1_BASE
#define FB_CS4_BASE ...
- Thu Dec 12, 2013 11:14 pm
- Forum: NetBurner Software
- Topic: Variable declaration
- Replies: 2
- Views: 3312
Re: Variable declaration
OK, thanks for the info.
There is always something you can learn.
There is always something you can learn.
- Thu Dec 12, 2013 7:54 am
- Forum: NetBurner Software
- Topic: software triggered eDMA does not start
- Replies: 8
- Views: 8332
software triggered eDMA does not start
Hi,
I used to work with a dev-70 board + a hand wired prototype board that required single value data transfers to get my AD converter data into SRAM.
I used the DREQ1 pin to trigger those transfers and it worked quite well except for the fact that potentially the eDMA transfer would be delayed ...
I used to work with a dev-70 board + a hand wired prototype board that required single value data transfers to get my AD converter data into SRAM.
I used the DREQ1 pin to trigger those transfers and it worked quite well except for the fact that potentially the eDMA transfer would be delayed ...
- Thu Dec 12, 2013 7:27 am
- Forum: NetBurner Hardware
- Topic: MOD54415 Boot problems
- Replies: 4
- Views: 5886
Re: MOD54415 Boot problems
yes, it definitely has something to do with power up behavior.
The solution I found is relatively simple: put a 1 microfarad capacitor between the reset pin and ground and it always works.
On the scope you can see the reset pin comes up +/- 1mS later and everything is fine in that case.
I have ...
The solution I found is relatively simple: put a 1 microfarad capacitor between the reset pin and ground and it always works.
On the scope you can see the reset pin comes up +/- 1mS later and everything is fine in that case.
I have ...
- Thu Dec 12, 2013 4:16 am
- Forum: NetBurner Software
- Topic: Variable declaration
- Replies: 2
- Views: 3312
Variable declaration
Hi,
On the assumption there is no such thing as a silly question, only silly answers here is a question the answer to which is probably very obvious but I am missing it.
in Example file "PeriodicAd.cpp" if find this:
volatile edma_tcdstruct &tmrTcd = sim2.edma.tcd[DMA_CH_DTER_0 + timerNum ...
On the assumption there is no such thing as a silly question, only silly answers here is a question the answer to which is probably very obvious but I am missing it.
in Example file "PeriodicAd.cpp" if find this:
volatile edma_tcdstruct &tmrTcd = sim2.edma.tcd[DMA_CH_DTER_0 + timerNum ...
- Fri Dec 06, 2013 6:05 am
- Forum: NetBurner Hardware
- Topic: MOD54415 Boot problems
- Replies: 4
- Views: 5886
Re: MOD54415 Boot problems
First Result: it definitely has something to do with power up behaviour:
If I apply the power by switching on the lab supply most often it does not boot.
If I leave the lab supply switched on and apply the power with a switch it never misses and always boots.
If I use the power supply ON/OFF ...
If I apply the power by switching on the lab supply most often it does not boot.
If I leave the lab supply switched on and apply the power with a switch it never misses and always boots.
If I use the power supply ON/OFF ...
- Fri Dec 06, 2013 4:17 am
- Forum: NetBurner Hardware
- Topic: MOD54415 Boot problems
- Replies: 4
- Views: 5886
MOD54415 Boot problems
Hi Everyone,
After 5 months of doing something completely different I have returned to my MOD54415 project.
In the mean time my new hardware is ready.
The hardware is specific to the application which uses the PWM outputs of the MCPWM a lot but in general it very much resembles the DEV-70 ...
After 5 months of doing something completely different I have returned to my MOD54415 project.
In the mean time my new hardware is ready.
The hardware is specific to the application which uses the PWM outputs of the MCPWM a lot but in general it very much resembles the DEV-70 ...
- Thu Jun 27, 2013 12:55 am
- Forum: NetBurner Software
- Topic: ucos task priority question
- Replies: 7
- Views: 7141
Re: ucos task priority question
Hi All,
Thanks for the help, because of it it did not take till noon.
I used the method suggested by roland.ames and it works a treat.
Just a few extra bits of info though: I am using version 2.6.2 so are there a few subtle differences to what roland suggested.
1) The function to use to wait for ...
Thanks for the help, because of it it did not take till noon.
I used the method suggested by roland.ames and it works a treat.
Just a few extra bits of info though: I am using version 2.6.2 so are there a few subtle differences to what roland suggested.
1) The function to use to wait for ...