path: root/firmware/target/arm/imx233/
AgeCommit message (Collapse)AuthorFilesLines
2020-07-05imx233: Fix bootloader link regression caused by cd9906Solomon Peachy1-2/+2
Change-Id: I6341069aa3855a8a3ea9ed021c27aaa742cab698
2020-07-05arm: Fix PortalPlayer linker scripts with binutils 2.21+Solomon Peachy1-1/+1
For reasons that are still unclear, the 'ncbss' region was overlapping the "audiobuffer" when linked with 2.21, but okay with 2.20. Fixed it by making the audiobuffer explcitly use the current position instead of relying on it being implicit. With this change, portalplayer-based targets generate working binaries when built with binutils 2.21 or newer. This bug also theoretically affects imx233/imx31 targets as they also have NOCACHE_BASE games in their linker scripts, but I lack access to one to test with. Change-Id: Idb38ab20f03599b9ed3d4bc0eafe519f38677438
2017-01-24imx233: remove redundant lines in linker scriptAmaury Pouly1-1/+0
Change-Id: Ief8ab0c33abdd3b36cd94b0578e2c5cad22bf2a6
2014-02-17imx233: fix to properly support INIT_ATTRAmaury Pouly1-1/+1
Original fix by Marcin: it had a problem because crt0 on imx233 is more complicated than many targets: since we use virtual memory, we first disable the MMU, then move the entire image (including init and itext stuff), then setup a temporary stack to setup the MMU. Only when the MMU is enabled, can we move the init and itext stuff to its right location and finally boot. This requires some trickery because: - the initial move copies everything, including init and itext - the stack overlaps with init and itext to reclaim space - the temporary stack cannot be the same as the main stack to avoid trashing the init and itext code, also it needs to be a physical address Change-Id: Ibaf331c7d90b61f99225d93c9e621eb0f3f8f2dc
2012-05-20imx233: remove useless alignments in linker scriptsAmaury Pouly1-2/+0
Change-Id: I7fc5445f405e1a3e8830ddec2f7652e66a03a633
2011-12-17Do some things to make -ffunction-sections work better.Michael Sevakis1-4/+4
* Add wildcards to various sections placements a la *(".text") => "*(.text*)" * Remove hacky bits from those linker scripts (no problem encountered testing) * Change section for asm functions from .<section> to .<section>.<function> so that -ffunction-sections works for those asm file too. git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-09-23imx233/fuze+: rework crt0 and linker script to be able to load at any ↵Amaury Pouly1-0/+10
address and self-copy at the right one git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-09-13imx233/fuze+: rework linker script to load the bootloader at ram start + 1Mb ↵Amaury Pouly1-10/+20
to leave a load for the firmware git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-09-05imx233:fuze+: major memory and usb reworkAmaury Pouly1-1/+15
- now identity map dram uncached and have a cached and buffered virtual alias - rework dma to handle virtual to physical pointers conversion - fix lcd frame pointer - implement usb detection properly - implement bootloader usb properly - allow the bootloader to disable MMC windowing (useful for recovery) git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-07-23imx233/fuze+: move page table to dramAmaury Pouly1-2/+2
git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-07-23imx233/fuze+: prepare target to enable MMUAmaury Pouly1-3/+3
git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-07-02imx233/fuze+: make config.h more correct, remove logo from bootloader, ↵Amaury Pouly1-28/+23
update linker file and crt0 to produce a single blob into dram git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657
2011-05-01Sansa Fuze+: initial commit (bootloader only, LCD basically working)Amaury Pouly1-0/+71
git-svn-id: svn:// a1c6a512-1295-4272-9138-f99709370657