Legacy microcontrollers Forum Discussions
Dear all,
For PTN194501, MB9BF566RPMC-G-JNE2 is migrated to CY9BF566RPMC-G-MNE2.
Is there any change in function, specification or form?
Also please let me know if there is any change in fab, assembly and test site?
Thank you,Shun Furusawa
Show LessAny information on this is appreciated.
The client's PCB has:
- P2.9 for DAP0
- P7.0 for DAP1
How can I configure the XE167F-96F to use these pins for DAP debugging with the miniWiggler 2? Show Less
MB90097PFV-G-132-BNDE1 と MB90097PFV-G-132-BND1 の違いを教えてください。
Hi,
I think I found a bug in the PDL v2.1.0 in adc.c. There are 2 macro names used that are not defined: FM_ADC0_SCTSL_AVAILABLE and FM_ADC0_PRTSL_AVAILABLE. The correct names, as defined in the s6exxxxx.h files, should be FM_ADC_SCTSL_AVAILABLE and FM_ADC_PRTSL_AVAILABLE respectively (without the "0" after "ADC"). There are 3 lines where one or both macros appear (see diff below).
--- a/PDL/2.1.0/drivers/adc/adc.c
+++ b/PDL/2.1.0/drivers/adc/adc.c
@@ -485,7 +485,7 @@ en_result_t Adc_Init( volatile stc_adcn_t* pstcAdc,
return ErrorInvalidParameter;
}
- #if defined(FM_ADC0_SCTSL_AVAILABLE)
+ #if defined(FM_ADC_SCTSL_AVAILABLE)
// Scan Conversion Timer Start Enable and Timer Source
if (TRUE == pstcConfig->pstcScanInit->bScanTimerStartEnable)
{
@@ -516,7 +516,7 @@ en_result_t Adc_Init( volatile stc_adcn_t* pstcAdc,
// Priority external Trigger Start Enable
stcPCCR.PEEN = (TRUE == pstcConfig->pstcPrioInit->bPrioExtTrigStartEnable) ? 1u : 0u;
- #if defined(FM_ADC0_PRTSL_AVAILABLE)
+ #if defined(FM_ADC_PRTSL_AVAILABLE)
// Priority Conversion Timer Start Enable and Timer Source
if (TRUE == pstcConfig->pstcPrioInit->bPrioTimerStartEnable)
{
@@ -729,7 +729,7 @@ en_result_t Adc_DeInit( volatile stc_adcn_t* pstcAdc, boolean_t bTouchNvic )
pstcAdc->WCMRCOT = 0u;
pstcAdc->WCMRCIF = 0u;
#endif
-#if defined(FM_ADC0_SCTSL_AVAILABLE) && defined(FM_ADC0_PRTSL_AVAILABLE)
+#if defined(FM_ADC_SCTSL_AVAILABLE) && defined(FM_ADC_PRTSL_AVAILABLE)
pstcAdc->SCTSL = 0u;
pstcAdc->PRTSL = 0u;
#endif
Best regards,
Thomas
Show LessHello I have the same problem as discussed in https://community.cypress.com/thread/47796?q=S6E2CC%20not .
I installed all the prerequisite drivers and software. When trying any keyboard input into the Serial Port viewer terminal, LED's on the board flash but nothing happens. Running board tests (as the quickstart guide suggests) by pressing ENTER does nothing. No keyboard input shows up in the terminal.
Apart from that, just like in the above mentioned post, I can compile and load code that should work (example code and S6E2CC projects found online) onto the board but the boards does not seem to be doing anything .
I tried removing the J2 jumper connector from the board but that did not help.
Its my first time using the board so all suggestions/ help is welcome.
Show LessI am trying to verify the check sum on a few XC886 ICs using the Memtool and Miniwiggler V3.
I have been able to connect via JTAG to the DAS network and it discovers the device. I have not been able to get the Memtool to work correctly.
Please help Show Less
Help me please with a target.cfg for XC2336A-72F80L. I can't find one in Memtool 4.7. I've tried with 4.3 but no luck either.
I'm using miniwiggler v2.0 and i simply can't connect to this type of controller.
Many thanks Show Less
My goal is to evaluate how fast I can toggle an I/O on the XMC1100.
For this, I bought the cute XMC 2Go kit and installed DAVE4.
Starting point was the XMC_2Go_Initial_Start_v1.3 example.
I can change the frequency of the blinking led. Toolchain works. Fine.
Then I added the line
P0_5_toggle();
In a while(1) loop.
Toggling works and time from rise to fall is about 3us.
Really slow.
According the comments in the example, the CPU clock is running on 8 Mhz.
Not sure how this works, but I need the 32 Mhz.
Changed the configuration to :
SCU_CLK->CLKCR = 0x0FFC0100UL;
This resulted in toggle time of about 1.2 us.
After this, I replace the function call to P0_5_toggle() with it's contents:
PORT0->OMR = 0x00200020UL;
This resulted in an improvement to about 530ns.
Oops! The tooling neglects the inline directive of the P0_5_toggle() function. No idea why.
Next step is to execute the toggle code from RAM.
Therefore, I move the toggling code to a separate function in a separate file.
In the function declaration, I added the famous __attribute__((section(".ram_code")))
However, the tooling also neglects this directive, and the code is still executed from flash.
Anybody knows a solution?
It seems that it is a tooling issue.
I tried to understand the linker script, but I did not see strange things.
Thanks,
Lodewijk
--
An investigation of the 530 ns:
The P0_5_toggle() generates 3 assembly instructions (2 loads and 1 store):
LDR: 2 cycles
LDR: 2 cycles
STR: 2 cycles
+ a B(ranch) for the while loop of 3 cycles
So, this is 9 cycles. If we assume 2 wait cycles for reading from flash, we have 8 additional cycles.
In total 17 cycles. 17 cycles * 31ns = 527ns. Show Less
Dear all,
Please provide the latest datasheet of MB96800.
Is it following? If not, please attach to this case.
MB96800_DS704-00016-3v0-J.pdf
MB96800_MN704-00013-2v0-J_20140630.pdf
Thank you,Shun Furusawa
Show Less