talkingtoken
2013-04-17 15:31:09 UTC
Hey Greg,
Being new to this forum, I'm not sure how much traffic you want to see regarding development and porting questions and/or suggestions, so if I'm posting inappropriately, just let me know. So I have made some more progress on the Mikroe-STM32F4 board port. I have the debug RS-232 port running (using the board's expansion header with jumper wires to an external USB-to-232 board). Plus I have the MMCSD interface working, and a driver for accessing the serial flash.
I have a few questions since I have and am making some fairly significant additions:
1. Are you interested in receiving this port for incorporation into a released build at some point? The questions below assume you might want the port, otherwise it wouldn't really matter how I implemented this stuff.
2. If you are interested in the port, in what format would you want it? Patch file? Or do you use a git repository or cvs or something?
3. I am adding a block flash driver that is optimized for the M25P80 (8Mbit serial flash) on this board (and other small serial flash), along with an optimized file system. I'm calling it the Sector Mapped Allocation for Really Tiny (SMART) flash driver and FS. But I need to add some FS ioctls. Should these be added to the "include/nuttx/fs/ioctl.h" or should I just put them in a local "driver/mtd/smart.h" file?
4. I plan to extend the file system's g_bdfsmap[] with a "smart" entry (properly conditioned with appropriate CONFIG_FS_SMART) so the serial flash can be mounted. Is this okay?
5. I noticed there are CONFIG_DEV_NULL and CONFIG_DEV_ZERO options, but the code doesn't actually use them. In my local "arch/arm/src/common/up_initialize.c" file, I conditioned the "devnull_register" with this define, and added a qualified devzero_register also, but I don't know if this would break anything in a release build.
6. I will need to add an enumeration to spi_dev_e in "include/nuttx/spi.h" for SPIDEV_AUDIO. I'm guessing that won't be an issue?
Again, sorry for all the pesky little questions. If there is a better forum for development type questions, just let me know.
Thanks. Oh, and did I mention this OS is FANTASTIC!!! I see there have been contributions from others, but it looks like more than 95% of the work is yours. Hard to believe one person could type so much! What keeps you so motivated?
Ken
Being new to this forum, I'm not sure how much traffic you want to see regarding development and porting questions and/or suggestions, so if I'm posting inappropriately, just let me know. So I have made some more progress on the Mikroe-STM32F4 board port. I have the debug RS-232 port running (using the board's expansion header with jumper wires to an external USB-to-232 board). Plus I have the MMCSD interface working, and a driver for accessing the serial flash.
I have a few questions since I have and am making some fairly significant additions:
1. Are you interested in receiving this port for incorporation into a released build at some point? The questions below assume you might want the port, otherwise it wouldn't really matter how I implemented this stuff.
2. If you are interested in the port, in what format would you want it? Patch file? Or do you use a git repository or cvs or something?
3. I am adding a block flash driver that is optimized for the M25P80 (8Mbit serial flash) on this board (and other small serial flash), along with an optimized file system. I'm calling it the Sector Mapped Allocation for Really Tiny (SMART) flash driver and FS. But I need to add some FS ioctls. Should these be added to the "include/nuttx/fs/ioctl.h" or should I just put them in a local "driver/mtd/smart.h" file?
4. I plan to extend the file system's g_bdfsmap[] with a "smart" entry (properly conditioned with appropriate CONFIG_FS_SMART) so the serial flash can be mounted. Is this okay?
5. I noticed there are CONFIG_DEV_NULL and CONFIG_DEV_ZERO options, but the code doesn't actually use them. In my local "arch/arm/src/common/up_initialize.c" file, I conditioned the "devnull_register" with this define, and added a qualified devzero_register also, but I don't know if this would break anything in a release build.
6. I will need to add an enumeration to spi_dev_e in "include/nuttx/spi.h" for SPIDEV_AUDIO. I'm guessing that won't be an issue?
Again, sorry for all the pesky little questions. If there is a better forum for development type questions, just let me know.
Thanks. Oh, and did I mention this OS is FANTASTIC!!! I see there have been contributions from others, but it looks like more than 95% of the work is yours. Hard to believe one person could type so much! What keeps you so motivated?
Ken