Seems like I missed that declaration of limitation when deciding to buy.
Seems like I missed that declaration of limitation when deciding to buy.
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
I, you or some, could copy paste HSERIN macros (and some other compiler directives), modify it, include them in the .LIB so you have a "fully workable" 2nd USART... but it belongs to Melabs to fix
Nothing stop you to implement a home-made one though...
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Modifying .LIB files works well, but it is a mixed blessing when MELabs releases a new version. You want the new features, but you have to be really careful to move your changes into the new library. When that time comes, I highly recommend the program ARAXIS MERGE.
Charles Linquist
Thanks for the help guys. I looked at the LIB files and I don't want to mess with them. I will try my luck with support, until then I guess I will just do it "long hand". It seems to me the advantage of HSERIN/HSEROUT is easy array TX/RX and data formating.
Can anyone confirm this?
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
true. do you need all features, high baudrate and interupts? In meantime can DEBUG/SERIN be enough?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I am not sure what "all features" are. No I don't need high Baud or interupts. I DO need to use the 2nd UART and not the 1st. I am trying to play with SERxxx2 now just to establish board function and communcation with PC. When I have that working, I will move on to the hardware UART. I am hoping by then maybe Melabs will have an answer as to fixing the omission or not. From there I will decide how I want to code the hardware UART based on their answer. Right now I am feeling like a "PBP talking to the registers" is going to be the answer. Thats still a tiny bit simpler then writing it in ASM.
Or I will come up with an "include" file so I can use it like HSERxxx. maybe I'll call it BSHIN and BSHOUT!
-Bert
The glass is not half full or half empty, Its twice as big as needed for the job!
http://foamcasualty.com/ - Warbird R/C scratch building with foam!
Bookmarks