Thanks Giovanni!
This was the hint you gave: "Writes are just a way to "assemble" frame composed of multiple parts."
I did not realise that by macWriteTransmitDescriptor() the driver should have only written to device's internal buffer and put that buffer on the ethernet only after ...
Search found 8 matches
- Mon Oct 30, 2023 1:06 pm
- Forum: Small Change Requests
- Topic: Extend MAC HAL API by macClearInterrupts()
- Replies: 4
- Views: 46847
- Sun Oct 29, 2023 12:00 am
- Forum: Small Change Requests
- Topic: Extend MAC HAL API by macClearInterrupts()
- Replies: 4
- Views: 46847
Re: Extend MAC HAL API by macClearInterrupts()
Hello Giovanni, thanks for response!
Ok, I understand about HAL API; driver's interrupt handling has been rewritten now.
One issue is still present what I'm struggling with. That one is around the lines with for(q = p; ...) macWriteTransmitDescriptor() in low_level_output(). I have said before ...
Ok, I understand about HAL API; driver's interrupt handling has been rewritten now.
One issue is still present what I'm struggling with. That one is around the lines with for(q = p; ...) macWriteTransmitDescriptor() in low_level_output(). I have said before ...
- Sat Oct 28, 2023 6:01 pm
- Forum: Small Change Requests
- Topic: Extend MAC HAL API by macClearInterrupts()
- Replies: 4
- Views: 46847
Extend MAC HAL API by macClearInterrupts()
Hello Giovanny.
I wrote two drivers for W5500 Wiznet SPI Ethernet Controller with integrated TCP/IP stack. The first driver is implementing "plain" ethernet using hal_mac_lld and therefore needs LWIP to work; the second one is based on IoLibrary from Wiznet. I'm going to contact folks from Chibios ...
I wrote two drivers for W5500 Wiznet SPI Ethernet Controller with integrated TCP/IP stack. The first driver is implementing "plain" ethernet using hal_mac_lld and therefore needs LWIP to work; the second one is based on IoLibrary from Wiznet. I'm going to contact folks from Chibios ...
- Mon Sep 06, 2021 8:40 am
- Forum: Bug Reports
- Topic: Linker errors on #define CH_CFG_NO_IDLE_THREAD TRUE
- Replies: 4
- Views: 4327
Re: Linker errors on #define CH_CFG_NO_IDLE_THREAD TRUE
Thanks for clarification about the main thread!
- Fri Sep 03, 2021 4:32 pm
- Forum: Bug Reports
- Topic: Linker errors on #define CH_CFG_NO_IDLE_THREAD TRUE
- Replies: 4
- Views: 4327
Linker errors on #define CH_CFG_NO_IDLE_THREAD TRUE
Hello Giovanni.
I have been playing with a demo RT-STM32F303RE-NUCLEO64. Having defined CH_CFG_NO_IDLE_THREAD as TRUE I get compiler warning "chDbgAssert(otp != chSysGetIdleThreadX(), "sleeping in idle thread");" and later linker errors with undefined references to "ch_core0_cfg" and ...
I have been playing with a demo RT-STM32F303RE-NUCLEO64. Having defined CH_CFG_NO_IDLE_THREAD as TRUE I get compiler warning "chDbgAssert(otp != chSysGetIdleThreadX(), "sleeping in idle thread");" and later linker errors with undefined references to "ch_core0_cfg" and ...
- Sat Nov 10, 2012 5:27 pm
- Forum: User Projects
- Topic: msp430x port
- Replies: 34
- Views: 30964
Re: msp430x port
Hi Giovanni,
common/msp430x is not supposed to replace the old GCC/msp430. msp430x port is relying on extended cpu instruction set: calla, mova and so on. The code would possibly become very rich in #ifdef constructions on trying to merge both ports together.
I've totally overseen TI libs in the ...
common/msp430x is not supposed to replace the old GCC/msp430. msp430x port is relying on extended cpu instruction set: calla, mova and so on. The code would possibly become very rich in #ifdef constructions on trying to merge both ports together.
I've totally overseen TI libs in the ...
- Tue Nov 06, 2012 4:10 pm
- Forum: User Projects
- Topic: msp430x port
- Replies: 34
- Views: 30964
Re: msp430x port
Hi Giovanni,
thank you for answer, it did help - see report below. mspgcc and IAR ABI are different. The main modification was changing from asm("mova r11, r15") to asm("mova r11, r12") to get IAR happy, added some other compiler specifics and it ran. I was able to compile the port with the mspgcc ...
thank you for answer, it did help - see report below. mspgcc and IAR ABI are different. The main modification was changing from asm("mova r11, r15") to asm("mova r11, r12") to get IAR happy, added some other compiler specifics and it ran. I was able to compile the port with the mspgcc ...
- Fri Nov 02, 2012 4:20 pm
- Forum: User Projects
- Topic: msp430x port
- Replies: 34
- Views: 30964
Re: msp430x port
I have been porting ChibiOS to msp430x (msp430f5437). The port seems to be complete so far, but running TestThread doesn't confirm this:
*** Kernel: 2.4.2
*** Compiled: Nov 2 2012 - 15:30:01
*** Compiler: IAR IAR C/C++ Compiler V5.10.1.50144/W32 for MSP430
*** Architecture: MSP430
*** Core Variant ...
*** Kernel: 2.4.2
*** Compiled: Nov 2 2012 - 15:30:01
*** Compiler: IAR IAR C/C++ Compiler V5.10.1.50144/W32 for MSP430
*** Architecture: MSP430
*** Core Variant ...